Yes, "Drum map" is kind of a limiting description. Really it's an all-purpose port, channel and note number mapping tool that can also add velocity offset and scaling. You can use it to create keyboard splits to different synths or channels of a multi-timbral synth, or to alter the effective velocity curve or note range of a controller to work with a particular synth/patch, or to remap keyswitches to another part of the keyboard, etc.

I already tried downloading and installing a track template with AD drum maps, but when I load it I got no sound and couldn't figure out how to get it to output sound, and I just went ahead and redid my session drummer drum tracks into AD manually with note names in the AD clips instead of drums.

I don't know if this helps, but you can think of a Drum Map as a "routing" of sorts.   The note you click on in the PRV is routed to a specific synth, using a specific channel and MIDI note number.   So, you need to make sure that channel and MIDI note number are valid for that instrument... and of course that the instrument exists in the project.  
 

stevec
I don't know if this helps, but you can think of a Drum Map as a "routing" of sorts.   The note you click on in the PRV is routed to a specific synth, using a specific channel and MIDI note number.   So, you need to make sure that channel and MIDI note number are valid for that instrument... and of course that the instrument exists in the project.  
 

Hmm... that brings a lot more depth to all this. No wonder the darned thing is so complex. Now my brain is going in all sorts of different directions on its uses. And I thought I had it all figured out. D'oh. ;-)

Beepster

stevec
I don't know if this helps, but you can think of a Drum Map as a "routing" of sorts.   The note you click on in the PRV is routed to a specific synth, using a specific channel and MIDI note number.   So, you need to make sure that channel and MIDI note number are valid for that instrument... and of course that the instrument exists in the project.  
 

Hmm... that brings a lot more depth to all this. No wonder the darned thing is so complex. Now my brain is going in all sorts of different directions on its uses. And I thought I had it all figured out. D'oh. ;-)

Hey, as long as you don't implode you should be OK.  
 
As Dave mentioned there are things you can do beyond pure "routing", but I find it best to get that foundation down first so that the other stuff makes sense in context.   It is a powerful tool.  If anything, the UI/workflow just needs a little TLC! 
 

Well one of the first things that jumped out at me is the need to type in a MIDI note number with no option of using actually note/oct#... unless I'm missing something. Not a big deal but it will make it a little more tedious for me what with havin' to do all the mathz and countin' and such.
 
This is obviously easier for dudes who've been using MIDI for a long time... and who aren't as slow with basic number type things like ole Beeps here. :-/

Oh but on the hardware end of things, if this applies, I notice that the velocity range stuff might make it a lot easier for me to use my first gen DX-7 which has that pre standard velocity output. I'm assuming I could create a map with appropriate settings and turn that 110 range (or whatever it is) to be more evenly spread over the 127 range. Then I'd (in theory) apply the map to whatever track I want to record into with the old Yammie.
 
 I could also see it being useful with my padKontrol when doing drum beats. Like limiting the velocities to more upper range stuff so I don't get the occasionally "way too low" velocity hits which then need to be corrected later while retaining the variations of a live performance.
 
I was going to do this type of thing in the Track Inspector on a case by case basis or create a preset but a map sounds like a much better way to deal with it all.
 
That is... of course... if that IS indeed possible with the Drum Map thingie. If not I'd appreciate someone stating otherwise so I don't get myself all excited for nothing.
 
;-)
 

Beepster
Oh but on the hardware end of things, if this applies, I notice that the velocity range stuff might make it a lot easier for me to use my first gen DX-7 which has that pre standard velocity output. I'm assuming I could create a map with appropriate settings and turn that 110 range (or whatever it is) to be more evenly spread over the 127 range. Then I'd (in theory) apply the map to whatever track I want to record into with the old Yammie.

 

midiCurve may be a solution for the DX-7 issue

Thanks. I've gotten a few suggestions for third party stuff (from yourself as well and I thank you) but even if the Drum Map feature won't handle I think I've got a pretty decent plan with some of the built in controls in Sonar.
 
The one I was originally going to use for the DX-7 was to simply increase the velocity input by 17 (or whatever the discrepancy works out to) so the bottom velocities just aren't available because for 99% of what I'd be doing I don't think I'll be needing those and if I DO want to play something really delicate and quiet I can redo the settings or edit it later.
 
But does this mean that the Drum Maps won't spread the 110 range over the full 127 or, if not, duplicate the input scenario I described above (cutting off the lower 17)?
 
I do also have a modern 25 key controller if it is absolutely necessary for full velocity needs which I generally use anyway but I would like to become a proficient keyboard player because... well it's nerdy and cool. I even have a thin black tie and a fedora to wear while I play which makes things sound even cooler. ;-)

Yeah, I remember the old post. This plug-in looked interesting because it has the ability to create a velocity curve.