I've got a bunch of annoying meatworld stuff to deal with today but thought I'd toss this out to see what kind of ideas it produces. I am probably not going to do this immediately because I've got other things to do to my song first but I'd like to try it... or at least some variation of it.
 
Recently I've kind of learned how drum maps work. Very rudimentary knowledge and I haven't tested it but if I understand it correctly I can do multiple things that would benefit me greatly.
 
For this plan what I would like to do is create a drum map that triggers two drum synths. AD2 and BFD Eco loaded with the Zildjian Z-Pack (which is a very nice set of cymbal samples). That way I can use the AD2 kits and the Z-Pack cymbals.
 
The next thing I want to do with this map which I think is part of the drum map uses is be able to trigger both synths with my padKontrol. So the pads I have set up for the kit would trigger AD2 and the pads set up for cymbals would trigger BFD Eco.
 
So that is the most important part of the plan. I think this is possible but perhaps I am misunderstanding something and of course since I have not tried this yet there may be pitfalls along the way.
 
My question(s) is/are... am I understanding drum maps correctly? Is this even possible? What should I be concerned about or be aware of while attempting this? Does anybody have any general insights on this subject (seriously any old thing helps get the thnkulating bone working)?
 
After that, and this is just a scheme/pipedream I've come up with. I have not read about this anywhere and I doubt it would work BUT since I would likely be using some of these fancy new AD2 kits (Fairfax, Indie, Metal) and their presets (to start with then I'd create my own) is their ANY way to somehow route the BFD Z-Pack cymbal signals INTO AD2 so I can make it seem like those cymbals are occupying the same space the AD2 kit is in. Like if I were using the Fairfax kit can I somehow route BFD to send my cymbals into the cymbal channels to take advantage of whatever settings or IRs are associated with that ADPak? Obviously the Z-Pack cymbals were not recorded in the Fairfax soundroom so that aspect is not possible but maybe if the clean signals can be routed into AD2 then I could have them audible in the Room/Overhead mics and using whatever presets I have set in AD2.
 
Probably impossible but if there IS a way to route external signals into AD2 it could be a cool experiment. Otherwise I would just try to create a virtual room using Sonar for both the AD2 and BFD sounds.
 
So there ya have it. No emergency by any means. I'm just curious and hoping to learn something or just start an interesting convo about these features/techniques.
 
And now I must go do boring meatworld stuff.
 
Cheers!

PS: By pitfalls I mean routing/logical fallacies or potential bugs within the programs themsleves. System resource stuff can be managed separately. Having two drum synths running is pretty intensive but my system is pretty powerful and I have strategies to avoid maxing out my system so no worries there.
 
PPS: This experiment has been in the back of my mind for a while anyway so no matter what I'll be trying it and will update with results. May not be any time in the immediate future but I would like to get some solid drum maps together for specific creative projects.

If I understand your question correctly, you want to know if you can trigger two synths from one midi track using the drum map.  Yes, you can do that.  I had a map a few years ago that used the drums in EZD but the cymbols in something else.
 
If your padControl device is sending unique midi note values for each kit piece, the drum map approach will work fine.  What I don't think you can do is have two separate midi devices talk to the same midi track.  If you need to do that you could create separate midi tracks, with each receiving input from a different device.  Each track would use the same drum map to map to the correct synth.

Jim Kalinowski
If I understand your question correctly, you want to know if you can trigger two synths from one midi track using the drum map.  Yes, you can do that.  I had a map a few years ago that used the drums in EZD but the cymbols in something else.
 
If your padControl device is sending unique midi note values for each kit piece, the drum map approach will work fine.  What I don't think you can do is have two separate midi devices talk to the same midi track.  If you need to do that you could create separate midi tracks, with each receiving input from a different device.  Each track would use the same drum map to map to the correct synth.

Perfect. That is exactly what I want but I am glad you exapnded the thought into the realm of using multiple devices (this is the type of comment that gives me ideas).
 
Some day I would like to have a proper MIDI drum set up (instead of the pK). Obviously V-Drum units would be ideal but they are EXPENSIVE. So a way to possibly save money would be to purchase V-Drum kit pieces for the more sensitive components of a drum performance (snare, hi hat, double kick, ride) then use other less expensive modules (like from Alesis or other brands or just simple pads) for the less sensitive/less used parts (toms, crashes, perc). That of course is an even further in the future plan but interesting to consider.
 
Thanks.

Beep.
 
Part of the answer is to assign the Out Port inside the drum map manager to your different drum vst's
In this example they are all set to Session drummer but it's easy to reassign them
 

 
You will need to hold Control + Shift to reassign them in bulk
 
Hope this helps!

Hiya, Jonesey. Indeed helpful and I appreciate the visuals. I've skimmed the materials on this stuff but it's pretty complex for my simple little brain without actually doing a step by step on my own system (which I will do but I'm just trying to get ideas). I see what you mean about bulk reassign. The "Port" thing is confusing me a bit but I'll review the material and I'm sure I'll get it.
 
Just happy that aspect seems to be possible. MIDI routing really still turns me around quite a bit and the Drum Map thing seems to be something that requires a good grasp of what terms mean what. I'm kind of like an old creaky man easing into the warm bathtub of MIDI concepts. I'm reaching that momentarily and alarming ball level point before fully settling into the warm embrace of understanding. It'll burn for a second but totally be worth it.
 
Hope you've been well.
 
These maps are gonna happen.
 
Cheers.

Love your verbal imagery!!!!
 
Drum maps were to me, totally arcane, complex and completely unintuitive.
 
I learnt all of this from Scott Garrigus' Sonar Power book - Sonar 6 I think it was.
 
He takes it step by step with examples all the way. If you don't already have a copy, grab one, though I don't think he's done a Splat one yet.
 
 

Yanno... that's a good idea. I don't think the drum mapping has changed significantly enough between X1 and now so the Power book I do have should still be relevant. Between that, Karl's vid and the manual I'm sure I can totally twist that drum map thingie to my will.
 
I really should too because as I learn more about stuff I realize that all these darned things (synths, instruments, samplers, etc) may or may not respond the same way and I do not want to have to endlessly map things on my devices or in the synth options (which would require learning each device's internal mapping system).
 
Drum maps... be warned. You will be conquered.

Drum maps have other uses besides the obvious one.
 
For example, I read a tutorial which used them to split up note data from articulation data which is invaluable when doing complex orchestral mockups which I do from time to time.
 
At a glance, I can see the notes and the artic switches in the same screen and as a bonus, they scroll across the screen at exactly the same rate (all my other workarounds failed in this respect)
 
My orchestral template now consists of approx 135 tracks, split more or less equally between midi tracks, audio tracks and articulation tracks/maps
 
It's about 9Gb when everything is loaded

Way above my head but dammit I will figure it out.
 
Just being able to manage my drum hits properly (I go crazy on drums and use many artics) in a more compact window will be a massive benefit to me. I've been doing it all in the PRV and... well obvioulsy that is not ideal. I'm good at it that way but now I want more and the concept of splitting things out to various synths AND assigning things to a static map out to my devices is very appealing.
 
The pK also has some funky, yet unweildy, features on it like it's X/Y pad, Flam and Roll options. They are very cool when I can get them to do stuff but currently I have absolutely no control over what sounds I can manipulate with them. I know there are other ways to map those things but the DM stuff seems like one very useful way to go about it... or at least manage it all.
 
Thanks for the input. Makin' me think.