EXS 24 Logic Sampler Users Group

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

>first of all: many thanks for all your advice. the project is in the 
>works. of course, it's a huge environment, what with 64 audio 
>instruments and eight of them controlling another 64 aux's. lots of 
>scrolling.....

Sounds like a fun job to do... not... :-)

>i can't get transformer 2 [program change to cha (mapped)] to send 
>the data to the channel i've designated in the map.
>[...]
>The program change number is NOT controlling the channel# of the 
>channel splitter (as it should).
>[...]
>then i set up the map: 0->8, 1->9, 2->10, 3->11, 4->12, 5->13, 
>6->14, 7->15, 8->8, 9->9 10->10, 11->11 etc.
>
>what am i missing? is there another setting i should make that i'm forgetting?

It seems that everything is basically okay.  I think your approach is 
sound in principle, but you might indeed have forgotten one vital 
thing.  You want the program change's -1- byte to control the 
channel, right?  Now in the transformer window you see 3 vertical 
lines between Conditions and Operations, linking Cha to Cha, -1- to 
-1- and -2- to -2-.  This is the usual mode of operation: normally 
you want to transform some -1- value to some other -1- value for 
example.  In your case however, you want the -1- value to control the 
Cha.

If you click on the leftmost vertical line, the picture will change 
from "| | |" to "/ | |", linking the Conditions -1- byte to the 
Operations Cha byte.  Now the -1- byte of the incoming message will 
be used: it will be sent to the map, get transformed there, and then 
get used as the new Cha byte.  So all you have to do (hopefully) is 
click the leftmost vertical line once, until it links -1- to Cha.

Note: the fact that it doesn't work in your current setup is no 
wonder.  You send cha-1 messages into the transformer.  This "1" is 
then mapped and used as the output cha, which will yield the same 
output channel for every cha-1 message that is received, regardless 
of the value of the program change.

>is it worth using a condition splitter? (see below)

No, I don't think so.

>P.S.: just in case i get around to worrying about vol/pan settings for AUX:
>
>Hendrik Jan Veenstra <h@...> wrote:
>>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.
>
>Have never used a condition splitter before, and could use some advice.

In the top popup of the transformer window, you can pick "Condition 
Splitter".  A Condition Splitter only operates on data matching the 
transformer's Conditions (as usual).  It then applies the Operations 
(as usual) and sends out the result through the topmost outlet.  All 
non-matching data is sent out the *second outlet*, and this is where 
the name 'condition splitter' stems from.  In programming terms, a 
Condition Splitter is a kind of "if..then..else.." object

You use a Condition Splitter if you e.g. only want to affect program 
changes and want to pass all other data unaltered.  Use a Condition 
Splitter as the very first object and have it match 'program change'. 
Now use the 1st outlet of the transformer to feed your environment 
patch and use the 2nd outlet to cable e.g. straight into the 'To 
Sequencer' object.
Obviously you can use a chain of CS's to split incoming data into 
several streams.  The 1st selects prg-changes, and its 2nd outlet 
goes into a 2nd CS which selects controllers, and this 2nd CS's 
outlet goes to a 3rd CS which selects channel pressure... etc.

Let me know if you get your patch working -- I'd be curious to know. 
And don't hesitate to ask if you run into more problems, or if my 
proposed solution doesn't work.

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