Stuck trying to separate drums into seperate channels/tracks properly

[Djentalist]

Hi all,

I've been using Cakewalk for some time now but there are still a lot of basic features that I have yet to figure out.

QUESTION
I have a drum track (SI Drum Kit) that I want to split up into a few separate channels, something like Kick, Snare, Toms, Hats, but I can't figure out how to do this in Cakewalk. This is mainly so I can process each group with different effects (such as separate equalizers per group). I also have a Drum Map because I use a midi drum pad as input to record notes. Ideally I would have a single midi track so I can record my drumming inputs with a single button, and the output from that is split up to the different channels like described above. It would probably be useful to also have some kind of container (bus?) for all drum tracks together, so I can for example mute or solo all the drums as a whole with a single click, or maybe to do some mixing/processing over all of them together as well. 

CURRENT ATTEMPT/SETUP
I've watched some videos explaining how to split drum tracks or route them to a bus, but I got stuck figuring out how to keep the Drum Map with this.
See screenshot below for my current setup:

If nothing else works I guess I can just add a new drum instrument track for each group, but I feel like there are easier and better ways to handle this.

I'm still not super familiar with buses and routing in Cakewalk, but before Cakewalk I worked with Reason and I remember using combinators a lot to solve similar problems.
Often I'm struggling with Cakewalk's view to visualize how tracks and buses are routed, but maybe things will click after getting more familiar with it.

Edited Thursday at 12:08 PM by Djentalist

[parboo12]

I'm assuming that you have a midi drum track with everything on one track. One easy way to do it is copy the drum track a few times (ctrl shift drag) and delete everything that isn't the kick drum on one track, everything that isn't the snare on another track, etc. Don't touch the original, in case you screw up. When you're done archive the original drum track.

[Pathfinder]

I always start by using the CAL Split Notes to Tracks. I your case you could then assign certain ones to different busses etc.

Edited Thursday at 04:11 PM by Pathfinder

[Pathfinder]

32 minutes ago, parboo12 said:

I'm assuming that you have a midi drum track with everything on one track. One easy way to do it is copy the drum track a few times (ctrl shift drag) and delete everything that isn't the kick drum on one track, everything that isn't the snare on another track, etc. Don't touch the original, in case you screw up. When you're done archive the original drum track.

Why don't you use the CALS? They work great.?

[OutrageProductions]

1 minute ago, Pathfinder said:

I always start by using the CAL split Notes to Tracks.

+1

[Djentalist]

Oh I only found out about CAL about a week ago, I didn't know there was something like the split notes thing.

Is it an action you do at the end when your track is finished? Or can you keep working/recording in a single midi track while the function wires things to separate tracks while you're working on the project?

[OutrageProductions]

A CAL script is a "one & done" operation.

After you split & consolidate the MIDI notes to the individual instrument (ex: all hats... open/pedal/closed) you can then add/edit them on the individual assigned track to your hearts desire without the distraction of other drums in the same track.

[Amberwolf]

If I understand correctly, you want to process the *audio* from SI drums as separate audio tracks for different drums?

Not just split the MIDI notes out to separate tracks (or clips)?

 

If so, you don't need any CALs (though if you can get them to work they may save some time getting the MIDI parts split if you need to use separate synths), but you do need to setup the synth being used with multiple sets of audio outputs that you can use as the input to different tracks, *or* use multiple separate instances of the same synth, each fed by just the notes for the specific drum(s) you want to use.

SessionDrummer and some other drum synths have multiple separate audio outputs that you can use for individual drums within the synth, by changing the settings in the synth (in it's mixer, or the drumpads, etc) to point the different pads or sounds to different outputs.    With these, you just use the separate audio tracks' fx bins to make your separate-drum fx chains, then set the outputs of all these tracks to your common percussion bus(es) with the rest of teh chain that is common to all of them (like a master multiband compressor, soundshaper, room space, etc). 

There is no need to split the MIDI out to separate tracks or clips, since it is all feeding the same synth and it doesn't matter for the audio side whehter the MIDI side is one track or not.  So you can leave it as a single track if you like. 

 

If your SI drums is like the ancient one I have here, it only has one stereo output, so you can't do this quite as simply and instead have to use multiple separate instances of it, each for one drum or one set of them that uses common effects, etc.  In this case, you do have to split the MIDI out to separate tracks, each one feeding just the synth for that specific drum sound or set of them.  For example, with a very basic kit if you want the kick, snare, toms, and cymbals to each have it's own chain, then you'll need at least five instances of the SI Drums to do that.  And you will have to split the MIDI out to separate tracks to go with those. 

 

If your SI drums has multiple output channels, then you just make tracks for those and assign each drum to a separate channel, just like the Sessiondrummer. 

 

To split the MIDI you can either use CALs, or there are two ways to do it manually.  I'll just specify the simplest, which is to clone the whole MIDI track for the drums to as many tracks as you have drum synths / sounds to trigger from them.   Then for the first of those tracks, go into PianoRoll View.  In PRV, first deselect all, then on the piano up the left side, click and drag on all the notes you do not want to have in that track, which selects the whole track's worth of notes except for teh ones you want there, then press delete.  

Repeat that for each separate track. 

Assign each track to the synth that you have setup for that drum.    

 

If you want to do it the harder way I'll describe that one but it's a lot more steps. 

 

If it helps to see what I'm talking about, I've attached a cut down version of a project from my ancient SONAR (which should still open in modern ones) that uses SessionDrummer3's multiple output busses to feed different audio tracks from different drums, and different effects, etc on various tracks, that are then routed to busses to get mixed down (with other more global effects on the busses). 

It also has the drum MIDI clips split out to separate tracks (which I do for ease of editing rather than anything needed for bussing / effects). 

 

 

drums split to tracks.cwp

Edited yesterday at 03:09 AM by Amberwolf

[Ross Smithe]

Scrap the drum map, honestly that is a remnant from the earlier days of MIDI before combined audio/midi VSTi's. To learn how to do what you're wanting, download a newer free drum instrument like Stephen Slate Drums. With that, you can easily route to separate outputs, which you can then assign to individual audio tracks in CW. It has a built-in mixer, and also the ability to easily map an external kit to the instrument or rearrange the assignments on a keyboard to your liking. There are numerous other choices out there that also do this (SI Drums doesn't), but Slate is a good free one to learn on, and it sounds great!

Edited 18 hours ago by Ross Smithe

[Glenn Stanton]

i think the drum map might actually benefit with some improvements as not all VSTi have built-in mapping features for the MIDI note assignments. another preference would be to not call it a "drum map" but rather an instrument map or MIDI matrix etc to better define it's function - mapping one set of MIDI notes to another set of MIDI notes and assign it to an instrument or better yet, available to multiple MIDI driven instruments 🙂 

[Bristol_Jonesey]

56 minutes ago, Glenn Stanton said:

i think the drum map might actually benefit with some improvements as not all VSTi have built-in mapping features for the MIDI note assignments. another preference would be to not call it a "drum map" but rather an instrument map or MIDI matrix etc to better define it's function - mapping one set of MIDI notes to another set of MIDI notes and assign it to an instrument or better yet, available to multiple MIDI driven instruments 🙂 

Yes, exactly this.

Back in the days before we had articulation maps, I used Drum maps extensively to map out orchestral articulations - one for each instrument

It was a monumental undertaking but it worked! I had the drum map above the note pane so I could change artics in context with the note being played

[msmcleod]

Honestly, I think the best solution is a CAL script. 

I used to record MIDI drums on my external Alesis DM5, then use a CAL script to split the drums to separate tracks, solo and record the audio for each one, then mix as if they were live drums.

[Amberwolf]

The cal still won't do what this person appears to want to do, since it cannot split the audio outputs to separate tracks so they can be fx'd/etc separately, only the MIDI notes.  

 

A drum map is great for putting the right note names on the right midi notes (so you don't have to remember which note is which drum), but it doesn't affect this either, so having the map or not doesn't change what this user appears to want.  

 

Having a drum synth that has multiple separate audio outputs (either mono or stereo) *would* do it.

 

Or using multiple separate copies of the synth, each played by only the notes for the set of drums that will have the same fx chain/etc.