So I have this feature working perfectly but it is a little arduous to setup, especially because I have to do this for about 10-20 different functions. You can see that I demultiplexed an incoming OSC message from my software and then applied a MIDI template event to each incoming message. To do this required 12 MIDI templates for the 11 lights (plus off) and then spreading those out across 101 (including 0) incoming OSC messages.
A little explanation, my lighting software sends several messages that OSCulator is receiving like this
/eos/out/wheel/1
/eos/out/wheel/2 etc. etc.
these messages can send several things, wheel 2 can send several values like /eos/out/wheel/2/[Red] 24, /eos/out/wheel/2/[Pan] 212, /eos/out/wheel/2/[Cyan] 14
I demultiplexed it so that I could separate out the various messages and then make them output a MIDI cc that corresponds with the specific light that I want to light up around my encoders. I was just wondering if I can do this without demultiplexing.
An Idea I had was to use substitutions but (Understandably) there is no info on this as the version 3 manual isn't out and I couldn't figure it out by reading on the forums. I don't entirely get how it works but it sounds like it could potentially be a solution? I would need to subsitute the MIDI CC velocity with the argument from the OSC message but with one only for red, one for pan etc.
It would be much better to do it this way because I would only have to toggle off one event and trigger on one other event to change the midi template from red to pan. Right now I would have to toggle off 101 events and then toggle on 101 events to switch from red to cyan.
Again I don't know if this is possible already
Comment