EXS 24 Logic Sampler Users Group group photo

Yahoo Groups archive

EXS 24 Logic Sampler Users Group

Index last updated: 2026-04-28 23:25 UTC

Message

Re: [EXS] processing each drum hit from an exs kit when mixing?

2005-06-30 by Eli Krantzberg

On Jun ,29, 2005, at 9:41 PM, tony vincent wrote:

> after you have programmed a drum kit, how do you all process each drum 
> in
>  the mix stage?  do you all separate the MIDI information (that goes 
> to the
>  exs kit), bouncing it to disc and the process each drum independently?
>  that¹s how i¹ve done it in the past- but there really HAS to be an 
> easier
>  way for this....

I don't think there's any one magic soloution. But there is certainly 
no need to actually print each part as audio first.

I usually just create multiple instances of the same EXS instrument, 
and then separate the midi information as needed. Sure it uses up more 
EXS instruments, but it doesn't really take up any significant 
additional system resources. You still have all the data as midi, so it 
is editable up to the end; and you can process the different EXS 
instruments as needed. I also often output them all to a bus to act as 
a subgroup where I can apply some general processing to all of them at 
once, and control the overall pre-mixed drumkit level - the best of 
both worlds.

Alternatively you can use the multiple output/aux feature; but to tell 
you the truth, unless you're setting up a template for repeated use, it 
seems like more work to me than just splitting the midi information 
across several instances of the same instrument. And you don't need to 
deal with the latency issues of putting plugins on auxes. Yeah, yeah, I 
know PDC in L7.1 takes care of that. But that's also not so simple; 
there are other issues the full PDC option brings to the party that 
need to be dealt with. I prefer to just keep it ol' skool:-)


--------
Eli Krantzberg
http://www.nightshiftorchestra.com
Almat Productions

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.