This post will probably help exactly none of you, but if any of you are experimenting with incorporating older MIDI gear into your setups, the process might at least be interesting.
As you might remember, a week ago I posted samples from my "new" Yamaha Digital Drums DD-5, explaining that while its built-in sounds may have a fun, cheesy vibe to them, what truly makes the DD-5 intriguing is setting it up to be used as a MIDI controller in Reason/Record. What I didn't get into was that its default MIDI output data is, in a word, strange. Its four pads output to A1, E2, A2, and D#3, making it the very opposite of "plug and play."
There are a couple of things you can do to change this. The first, and most obvious, is to use Reason's "Remote Override Edit Mode" which is what I experimented with to get it working in Redrum. It doesn't take much time and the results are what you would expect, giving you the "hit-here-get-sound-there" effect that you're probably looking for. The problem is that once you have these maps set up, tying each drum pad on the DD-5 to its appropriate Redrum channel, you'll quickly learn that those remote overrides aren't saved as global settings in Reason, instead being settings just for that one song or project. You can work around that, of course, by setting up a Reason or Record song with these settings and saving it as a template file, which you would then load every time you want to use the DD-5 as an instrument controller in a song.
That is, unfortunately, not very practical. I rarely know what devices I'll be using when I start up a new song. Part of the fun in making music is working through that process, picking up gear and blowing the dust off, as you encounter the different needs and inspirations of your latest song. Needing to know which devices you will use, before you start, might not be practical.
The other issue is that your MIDI interface, which accepts the MIDI data from the DD-5 and makes it into something Reason can understand, might not be dedicated solely to your DD-5. As is the case with my own setup, the MIDI interface you use might be more "universal" and sees use with a variety of gear, so mapping the DD-5's drum pads to specific Note Numbers might make it useless for other MIDI gear that require default note assignments, if you unplug devices and plug in new ones, working through your song.
The second option to you is using the DD-5's controls to set its output Note Numbers to match what you need Reason to "hear." The process for this involves several button presses on the DD-5, sometimes done while turning the unit on, but how this is actually done is a mystery to me. The DD-5 Owner's Guide is surprisingly vague on the steps and since the unit doesn't have a screen to provide any kind of useful feedback, its literally a case of fumbling in the dark. Plus, any tweaks or changes you make are erased when the unit is powered off, requiring you to do this every time you use it. Again, not very practical.
So, what can you do? Well, the solution I finally decided upon, which might be useful to you in your own MIDI experiments, is using Reason's NN-XT to map samples to the specific notes being sent from the Yamaha DD-5 (or whatever piece of outdated gear you might be using).
- Yamaha DD-5: Preset Pad Assignments ( NN-XT Patch )
If you open up the NN-XT's Remote Editor you'll see that the instrument contains four samples, each one mapped to either A1, E2, A2, or D#3, the MIDI Note Outputs of the DD-5. The specific samples and assignments match the four preset pad assignments that load into the DD-5 when you first power it on, but they can easily be replaced with whatever sounds you might want to trigger using the device's drum pads by selecting the appropriate sample and clicking "Load Sample" to assign a new sample. The mapping stays the same, but keep in mind that the Root resets to C3 whenever a new sample is loaded. You'll need to manually change this whenever you load a new sample if you want to keep its tone intact.
While this isn't quite "plug and play" its a bit faster than using the Remote Override Edit Mode, and if you take the time to set up a series of NN-XT patches with samples mapped to the appropriate pad assignments, you can achieve the kind of quick, flexible access you might need.
So, as I said at the beginning of this tutorial, this long-winded explanation of how I setup my DD-5 probably isn't useful for anyone out there. The odds that any one of you have a setup (or needs) identical to mine are fairly slim, but using Reason's NN-XT to accept specific MIDI notes, especially from old gear, might be a useful tool or technique for you.
A few random tidbits if you are one of the strange few using a DD-5 with Reason:
- The Yamaha DD-5 continues to make sound through its built-in speaker even while sending MIDI data. This can be hugely annoying, especially if you're using it to trigger sounds the DD-5 isn't making while you're playing it. Turning the volume on the DD-5 down doesn't work, because even at its lowest setting, the Yamaha machine continues to make noise. Just plug a 1/4 inch to 1/8 inch adapter into the DD-5's Audio Out and it'll stop making noise.
- As stated above, remember to adjust the Root note for each sample, if you load new sounds into the NN-XT patch provided. If you create a particular kit that you like, save it for quick access later.
- Also remember that you'll need to adjust the Amp Envelope's Release setting to account for samples that are longer in length than the NN-XT's default setting of only 60 ms. Forgetting to do this will create abbreviated sounds when you play them.