The OSC address definition: '/composition/layers/y/clips/x/select' points to an absolute address (i.e. /composition/layers/1/clips/1/select). It has an integer type tag with the value 0 or 1 and therefore it can only be either on or off.
They are perfect when you want to map a button to it but not a rotary switch or fader where you have 1-X positions and each position has to sequentially switch to a different OSC address.
What I am looking for is a way to establish this:
Fader position 1 = /composition/layers/1/clips/1/select
Fader position 2 = /composition/layers/1/clips/2/select
Fader position 3 = /composition/layers/1/clips/3/select
Etc...
Realtime situation:
Simply put, I want to map a controller (i.e APC 40 or Griffin Powermate) to CYCLE fast (not switch) SEQUENCIALLY through all available PREVIEWS (not clips) on a layer. (I'm not shouting here, just pointing things out
)Both devices only output MIDI or ASCII so OSC is a no go with these devices unless I find a way to translate MIDI to OSC.
But to prove that Joris is right (and he probably is
) I tried to build it in Vezer but even Vezer only accepts 1 OSC address per track.How would you solve this?
Just wondering:
Is there really a global OSC address: '/composition/layers/y/clips/x/select' or are the 'x' and 'y' only here to demonstrate the different absolute addresses for each preview position?
Life used to be so simple in Arena 5... (wink, wink...
)
