Check out the post on the Cakewalk Blog by Dan "Sonar X3 Quicktip: Setting up your Addictive Drums", he shows an example of setting up the multiple audio outputs for Addictive Drums

 
I made my set up a little different, to save on track numbers, where I was happy to combine the L&R outputs into one stereo track I did (e.g. Room and OH mics), but left others, e.g. Kick, as there own track.  Then you can start mixing and adding effects, e.g. limiter on the kick drum.
 
Set up some track icons then export the lot as a track template, then you can import this ready to go each time you have a new project.

wisebaxter442
...say I've recorded all of my drums in one track but I want to split them all up so I can mix them separately. Is there an easy way to do this? I've tried cloning the track but that just copies all mini events as opposed to the ones I've selected (i.e snare).  I've tried just a simple copy and paste into a new track but that seems to make the new track related to the first so I can't solo separately etc. I don't want to have to record each drum sound separately if I can help it.

If you are planning to do a lot more of this in future, then I recommended that you spend some time learning about drum maps. This provides a convenient method of mapping individual notes to different drums (or to trigger other sounds) and allows the whole kit to be controlled from a single midi track.

wisebaxter442
Thanks Tomix. But I'm still confused as to how being able to record all of the drum tracks separately with this approach is different to just cloning one track over and over again and then removing the midi you don't need for each track. Not that I really want to do it this way. Was just wondering if both approaches achieved the same result. Ta

Imagine editing a MIDI drum break in which every hit is on a separate track :o/ Having the MIDI tracks separated by kitpiece does not bring you any advantages (in average). Why would you spend time on cloning and deleting? I have difficulties understanding the logic behind your workflow.
 
As you self mention in your opening post, and Brundlefly confirms, you want the audio output of each kitpiece to be routed to separare tracks for mixing, EQ and FX, and keep the MIDI all on one track. This is, uness you want to do all mixing inside Addictive Drums own mixer.
 
You talk about "recording" in a little confusing way. You record the MIDI, you maybe have the audio output of every kitpiece routed to a track of it's own. Then, in case you want to change those to audio tracks, you either freeze or bounce, but that's not necessary, if your computer can handle the load.

I tend to agree.
 
I've never really understood the need to split out your midi into separate tracks -  you gain nothing!
Audio on the other hand - I've hsd as many as about 30 audio tracks set up in Sonar, each one picking up a different kit piece from the drum synth.
Using drum maps makes it a whole lot easier to mute/solo individual drums and is a lot easier on the eyes than a standard prv pane

 You talk about "recording" in a little confusing way. You record the MIDI, you maybe have the audio output of every kitpiece routed to a track of it's own. Then, in case you want to change those to audio tracks, you either freeze or bounce, but that's not necessary, if your computer can handle the load.

 
Ok it's all making sense to me now. The midi will appear on one track and will be routed to separate outs by AD for mixing. Can I also ask you why I might want to change midi tracks to audio in the way you suggested. As you've probably guessed by now I'm a little new to music production.

If you are planning to do a lot more of this in future, then I recommended that you spend some time learning about drum maps.

Cheers Kev, will do. Not come across drum maps yet really
 

Rob from Sydney
Check out the post on the Cakewalk Blog by Dan "Sonar X3 Quicktip: Setting up your Addictive Drums", he shows an example of setting up the multiple audio outputs for Addictive Drums

Dude that blog just saved my arse, you're a star

You certainly don't need to freeze or bounce your midi tracks to audio - but a lot of people like to work that way when mixing.
The only time you will definitely want to consider it is if you're working on an underpowered computer that is exhibiting signs of dropouts/glitches etc.
Freezing will render all of your midi down to audio, thus removing a potentially memory hungry vsti from the equation.
A bounce will also convert midi to audio but you will have to archive the tracks yourself after the bounce

wisebaxter442
 
Dude that blog just saved my arse, you're a star

Thanks wise - yeah, I came across it at just the right time, I was about a week ahead of you in trying to figure out the same things for the separate drum instruments.
 
Although really all the thanks are to Dan for the awesome blog in the first place!

Cheers Jonesy, that all makes sense. I have a feeling I may need to do some freezing at some point.