robert_e_bone
Sure - I'll try to do a better job of explaining.  Sorry for any confusion.
 
 <snip>
What I MEANT to explain is that I NEVER put any single kit piece set of midi events onto its own midi track.  So, I would never have a midi track for just kick drum events.  Doing things that way would mean I would have to edit multiple midi tracks just to adjust a simple drum beat - as I would have to edit the kick events on one track, the snare hits on another, each cymbal on yet more tracks, and each tom's events on even more tracks.  Hence, an editing nightmare, and something I just never ever never ever would do. <snip>
 
I hope that is a better explanation.  If not, let me know which parts you are still confused about, and I will drink some more coffee and try again.
 
Bob Bone
 

 
Got it now ! Thanks for the clarification because I was concerned that  the OP would become very confused. Fwiw, you will really like it when you to get into PRV with a drum map setup.
 

Guitarpima - nice even # post count.

I stated that. I clone the midi track in case I want to make changes to what I've written. I delete the split midi clips, make the changes to another cloned drum (midi) track, then clone that midi drum track as well and then split the cloned. I always want to be able to go back to an original or edited track. You never know when you may need it.
 
I route all the separate midi tracks to Addictive Drums and I use all the outputs from AD. I end up with two tracks, one midi and one audio except for cymbals, for every kit piece plus two tracks for the overheads and room audio outputs. The hi hat has it's own audio out as well. I also clone the bass drum midi track and route it to SD3. The AD kicks have good boom but I mis it with a good punchy BD in SD3.

However it works for you is fine.
 
I am a bit confused though, on what advantage you see in having a separate midi track for each drum kit piece.  I completely understand about the audio, but what does also splitting the midi up like that assist you with?
 
I am only trying to understand - not picking on it or anything like that.  I am just not understanding the benefits from all of the midi tracks having only 1 kit piece's events.
 
Thanks for trying to educate me on it, 
 
Bob Bone
 

Bob-
 
What problems have you found using the step sequencer with drum maps? I've done that ever since ere's been a step sequencer and never seen a drum-map related problem (using it to run SD3/3, an Alesis SR16 used as an expander and an MFB503 hardware drum synth).
 
One reason for creating seperate MIDI tracks for sections within kits is if you're using a drum synth that responds to lots of MIDI CC messages like the 503. It makes editing the CCs in the PRV much easier if you're only dealing with a few drums at a time.

I think I know what your after Bob. I find it easier to edit midi data, velocity etc, with each track individually. Maybe others can do that in one track but with my eyesight, it's much easier if they are separate.

That explanation makes PERFECT sense.  As I had said, whatever works for YOU is the right choice.  I was just trying to understand.
 
My own eyeballs are getting worse and worse myself, and I too may need to do the same thing one day.
 
I am already using a 46" HDTV as a primary computer display, and STILL have trouble.
 
Thank God my work still brains.
 
:)
 
Bob Bone

There is one little bit I don't understand.
 

robert_e_bone
THEN, in Sonar, I set up a track folder for Drums, and insert one midi track and one audio track for each of the kit pieces.  

I understand a separate audio track to be able to apply FX separately for each kit piece.  I don't understand why you would need ANY MIDI tracks, other than the one that is feeding into your drum synth in the first place.

cparmerlee
There is one little bit I don't understand.
 

robert_e_bone
THEN, in Sonar, I set up a track folder for Drums, and insert one midi track and one audio track for each of the kit pieces.  

I understand a separate audio track to be able to apply FX separately for each kit piece.  I don't understand why you would need ANY MIDI tracks, other than the one that is feeding into your drum synth in the first place.

YIKES!  I did NOT mean to convey that at all.  
 
I meant to say that the Drums track folder would contain only a SINGLE midi track, and that I would then insert multiple AUDIO tracks - one audio track for each kit piece.  I NEVER would have a separate midi track for each kit piece - NEVER.
 
The way I originally wrote it up, it looked like I was adding a midi track for each and every kit piece - NO WAY would I ever do that - it's just how I typed the sentence - DOH!
 
Sorry for any confusion, 
 
Bob Bone
 

robert_e_bone
YIKES!  I did NOT mean to convey that at all.  
 
I meant to say that the Drums track folder would contain only a SINGLE midi track, and that I would then insert multiple AUDIO tracks - one audio track for each kit piece.  I NEVER would have a separate midi track for each kit piece - NEVER.
 
The way I originally wrote it up, it looked like I was adding a midi track for each and every kit piece - NO WAY would I ever do that - it's just how I typed the sentence - DOH!

I read it over and over, and I didn't see how it could be true, because you were adamant NOT to split up the MIDI file.  Now that you explained, I see how the sentence can be read two different ways.  The glory of the English language.  :)
 
This is all very timely for me because until now I have been using "simple instrument tracks".  Last evening, before seeing this thread, I spent 3 hours going through the steps of setting up the connections for the various synths that support multiple outputs.  Each one is a little different, so I took copious notes as I figured out how to map each synth.  Session Drummer is more complicated because you have the added issue of the different kit pieces corresponding to different notes within a given MIDI channel, so I don't really have that sorted out in my mind yet.  But the thread was very helpful in solidifying what I was seeing in my experiments.
 
Thanks.