EOS firing OSC to Qlab - working, but inconsistently?

[Jay Ashworth]

Eos has 2 modes of sending OSC strings: implicit and explicit. Explicit cues can be sent in a variety of ways including cues, macros, and magic sheets.

• Cue x Execute String /cue/<qlab cue number>/start

There's also this recently introduced syntax. I'm not sure how it's supposed to work, or whether the feature is fully baked.

• Cue x Execute OSC Cue Send String ...
• Cue x Execute OSC Cue Recv String ...

Documentatiion on the feature is pretty scant. Allegedly, it applies to the cue list instead of a specific cue. It may be intended to provide a means of translating implicit OSC messages sent to other devices, or parsing incoming OSC messages received from other sources. There was a bug report that incorrect use of the feature could cause an infinite cue loop, but I haven't kept up on whether it's resolved.

Those are the syntax of how you write the cue on the QLab side, then? Cause my guy who does that only ever writes the OSC /slash/path/string...

 

[almorton]

That's the syntax on the EOS desk, Jay.