Paul Najar wrote: > > The big crunch with this way is that you loose your plugin delay > compensation. This is a real pain when using the Mixtend drums since > the ambient drum versions rely on sample accuracy for phase alignment. I am using Logic PC so I think the PCD thing is moot for me. > > > 3. You can also load the whole kit into multiple instances and send > > only Kick > > midi parts to one and only Snare midi parts to the next etc - ie > > multiple midi > > sequences - not so great for hyperediting. The additional instances of > > the kit > > use no additional RAM but the extra instances of the EXS24 do I > > believe. > > This is my preferred method. Even way before EXS when using hardware > multitimbral drum boxes I preferred to have each drum sound on it's own > midi channel so it was always quick to globally edit one sound - either > in the box or the midi data. It also allows me to use the EXS filter > and amplitude envelope - which is also a time saver in that you don't > need to save edited versions of a stock kit. It's all done when you > save the song. Yes - if you want to use the filters and envelopes this is the best way (filter offsets etc are less powerful). This is the most compelling advantage of splitting to separate instances. I like to see the whole pattern in the hypereditor when I am programming so it is a bit fiddly in that I need to edit one pattern and copy the sequence to the other instrument channels. It is a shame Logic has not followed Cubase/Nuendo in offering presets for sections of the mixer so that you can set up a complete multi-instrument set with all FX and sends and recall it. Regards, Murray