MIDI Map the FIRST LAYER on the DN-HC1000S
All the buttons can already be remapped on the FIRST LAYER. You know how users are complaining that the buttons don't work correctly until they delete the old MIDI maps. BINGO.
Well, you have to write your new maps. However, it is not that easy.
With a program like OSX MIDI or Bome's Midi Translator, I was able to change Denon's DN-HC4500 Native MIDI Map to my custom MAP. Serato didn't recognize the input anymore and I could use the controller as any standard MIDI controller. Instead of the TAP button being used for BPM, I changed it to the censor button etc. I had a detailed tutorial how to do this on the denondjforums.com before it was lost (last backup was November of 2008). Eventually, I will post a easier way on how to do this.
1. Load on old version of SSL (before Native DN-HC1000S support)
2. Do a manual custom MAP. Assign only the buttons on the HC1000s that you want to be different. For instance: Assign Tap to Internal
3. Go to Setup/ MIDI and name and save your MIDI Map. Do a backup in Windows Explorer (for PC: MyDocumentsMyMusicScratchLiveMIDI
for MAC: Music/ScratchLive/MIDI/)
4. Load the newest SSL with Native DN-HC1000S Support
5. Assign that same MAP.... Let me know if it worked.
Running more than one version of Scratch LIVE:
PC Users - before installing, find the ScratchLIVE executable (by default it is in C:Program filesSeratoScratchLIVE, and rename it - for example call it ScratchLIVE 1.9.1.exe. When you install the new version, the old executable will not be deleted, and you can choose which you want to run by going into that folder and double clicking on the executable. You can still do this if you have already installed the 1.9.2 Public Beta - just rename the executable to ScratchLIVE 1.9.2 Public Beta.exe, and then reinstall the version you were previously running.
Mac users - before installing, rename the existing application file as above (like "Scratch LIVE 1.9.1") - you have to be admin to rename it. (If you aren't admin, you can copy it to another location, and then rename it.) Even though the Public Beta version is already named to indicate which version it is, you need to change the name to stop it being overwritten by the next version you install, for example by changing "Public_Beta_1" to "PB1".