(Feature Request) Capture OSC in cue triggers

[Craig K]

Unless I've missed something, using OSC to fire a QLab cue can only happen with the QLab syntax for /cue/*/go.

Not all devices can send a specific OSC message, but will just broadcast their current state - snapshot number, channel mute status etc. Being able to capture this and use it as the cue trigger (much like capturing a midi string) would be a nice addition.

eg: Digico S21 has no way to add an out going OSC message to a snapshot, but I have companion listening for /digico/snapshots/fire 1 and then have companion send a go to QLab to have it trigger an audio cue.

Perhaps adding a capture function like midi triggers in cues have?

Thanks,

Craig K

[adenb...@gmail.com]

+1 for this request. 

[Paul]

I would suggest a sensible way to implement this would be to be able to designate a Script cue (in Settings-Network) which could handle any unrecognised OSC message coming into to Qlab and then take appropriate action (fire a cue or whatever). Such an OSC handler could filter and generally be more flexible than just starting a particular cue.