EXS 24 Logic Sampler Users Group

On a fine day, 12-05-2004, ben franklin wrote:

>solution: instead of using an 8-way cable switcher and 8 channel 
>splitter with 16 outs each, use a 16-way cable switcher (IS THERE 
>SUCH A THING?) and 16 channel splitters with only 8 channels each 
>(cha 9-16). change map accordingly.

Re: the cable switcher: yes, there's such a thing -- see Peter's post.

The disadvantage of using mc-EXS's (which you've surely realised) is 
that you have to create your own 8-output-instruments for this 
purpose.

>3. the volume & pan settings of midi tracks using the EXS 
>multichannel instruments would have to somehow bypass the EXS (mc) 
>and be sent straight to the AUX object.

Cable straight into the Aux-objects.

>4. RE.: the patch you described using a monitor hooked into two 
>transformers, then into a cable switcher, & from there into 8 
>channel splitters (now 16). What's the setting at the very top? (you 
>know, you get choices like: "apply and let non-matching pass thru 
>unaltered",  "apply and filter non-matching", etc. )

That somewhat depends on the work you've done before the Monitor.  If 
you use the Monitor as the track instrument in Arrange, and want to 
send different kinds of data to different destinations (notes 
straight to the EXS, volume/pan to the Auxes, etc) you would probably 
use a Condition Splitter (transformer) to split the data accordingly. 
Subsequent transformers are then sure to receive the proper data and 
can thus be left at their default mode of "apply operation and let 
non-matching events pass thru".  If you're afraid that the wrong kind 
of data might reach the transformer somehow, you would set it to 
"apply operation and filer non-matching data".  Even though it's 
simple, it does require some care: wrong data can mess up whatever is 
supposed to happen in a next phase, so in general you want to make 
sure that that doesn't happen.
Usually I tend to set transformers to "apply & filter non-matching" 
just for safety's sake.  Be aware that "non matching events" can also 
be generated in the patch itself.  If you bang a fader with an even 
value (meta-99, value's 0,2,4..) the message tends to percolate 
through the entire patch, unless stopped by a filtering transformer. 
So either use odd values for the meta-99, which don't suffer from 
this behaviour, or build in some safety net by setting transformers 
to "apply & filter".

>I'd simply go for "apply and let non-matching pass thru unaltered" 
>Is that correct? [There are some settings that start with "Copy and 
>..." - i don't use those, right?]

The "copy..." modes are normally only used for special purposes. -- 
e.g. when you want to duplciate an event and alter one of the 
duplicates.  I don't think you'll need those here.

-- 
Hendrik Jan Veenstra   h @ k n o w a r e . n l
Omega Art: http://www.omega-art.com/