OSC Message Format?

We've recently updated our console software to v2.6.2, and we seem to no longer have OSC control the way we did. The only system which works is to create events on the EOS listening to custom OSC strings and set an action for each. As the output OSC commands seem to have changed, have the input commands changed - or is the only way now to create events listening for each cue that wants triggering? When sending "/eos/cue/1/250/fire", diagnostics shows the receipt of the OSC string when an event isn't set up, but it doesn't seem to process at all.

I'm guessing I've missed something obvious, but I can't see what at the moment. Does anyone have an idea which might help?

Many thanks,

Dave

Parents

0 Druuka over 6 years ago

I would suggest downloading the show control supplement Rev C. OSC has changed a little but in general it has more options now than it did before.

What are you trying to do?

What was working before that is not working now?

What software are you transmitting from?






Run C ues
/eos/cue/fire	number of cue to run	/eos/cue/fire=1
/eos/cue/<cue number>/fire	number for button edge: 1.0=down, 0.0=up (optional)	/eos/cue/1.5/fire
/eos/cue/<list number>/<cue number>/fire	number for button edge: 1.0=down, 0.0=up (optional)	/eos/cue/1/1.5/fire
/eos/cue/<list number>/<cue num- ber>/<part number>/fire	number for button edge: 1.0=down, 0.0=up (optional)	/eos/cue/1/1.5/2/fire

This is an excerpt from the show control supplement.

Reply