Post by kyrrinstoch on Feb 10, 2011 11:17:52 GMT -5
This is something I know we ALL dread having to do - restoring our own personalized configurations and custom programming anytime we make any major changes to our setups. Most of us just set up the module the way we like it and leave it alone after that because of the hassle it takes to make all the changes.
The only "restore" we've been able to do is to the original factory configuration of the ddrum4 SE (1.5 version), because the configuration file was included on the Sound Library cd.
What if I told you that you could have multiple configurations you could load up without the hours of having to reprogram trigger/pad types, output routing or having to rebuild your kits every time you needed to change your setup?
That there was a way to save all of your programming and configuration information and restore it at your leisure?
A while ago (about 3-4 years ago) I was working with the MIDI Dump function of my ddrum4 (Section 6 - Panel Reference, System Functions, MIDI, D.xx functions in the 1.5x manual), and was able to capture different settings dumps using a tool called MIDIOX. I was then able to restore these same settings after reprogramming my module, simply by sending them back to the module using the same program.
This made my life so much easier when it came to managing my ddrum setup. I had certain sounds I used for certain things. Some were only ever used when triggering my acoustic kit, while others only got used with my pads.
I ended up creating a couple different setups and put each into their own folder. Each folder contained a copy of all of the sounds I used for that particular configuration and the associated settings dump file. Any time I needed to change from a triggered acoustic configuration to an all electronic setup, it was literally as simple as deleting all the sounds in the module, loading up the new sounds and then dumping in the configuration file. It only took a minute or two longer than just the sound transfer, as I also needed to fire up the MIDIOX program.
Pretty cool, huh?
MIDIOX is a 32-bit program for Windows.
Sysex Librarian software for Mac OS X may work as well (I'm not a Mac user, so I can't verify this...)
The only "restore" we've been able to do is to the original factory configuration of the ddrum4 SE (1.5 version), because the configuration file was included on the Sound Library cd.
What if I told you that you could have multiple configurations you could load up without the hours of having to reprogram trigger/pad types, output routing or having to rebuild your kits every time you needed to change your setup?
That there was a way to save all of your programming and configuration information and restore it at your leisure?
A while ago (about 3-4 years ago) I was working with the MIDI Dump function of my ddrum4 (Section 6 - Panel Reference, System Functions, MIDI, D.xx functions in the 1.5x manual), and was able to capture different settings dumps using a tool called MIDIOX. I was then able to restore these same settings after reprogramming my module, simply by sending them back to the module using the same program.
This made my life so much easier when it came to managing my ddrum setup. I had certain sounds I used for certain things. Some were only ever used when triggering my acoustic kit, while others only got used with my pads.
I ended up creating a couple different setups and put each into their own folder. Each folder contained a copy of all of the sounds I used for that particular configuration and the associated settings dump file. Any time I needed to change from a triggered acoustic configuration to an all electronic setup, it was literally as simple as deleting all the sounds in the module, loading up the new sounds and then dumping in the configuration file. It only took a minute or two longer than just the sound transfer, as I also needed to fire up the MIDIOX program.
Pretty cool, huh?
MIDIOX is a 32-bit program for Windows.
Sysex Librarian software for Mac OS X may work as well (I'm not a Mac user, so I can't verify this...)