OSC Goto

Currently not.

Thanks Anders for the confirmation. I'll vote for there being one in future! [:)]

Richard

Out of interest Richard were you using the OSC command from a show control system?

The use here would be to fire cues from a QLab system. I have used MSC many times for this, and was hoping for a direct OSC replacement that would solve a particular cableing issue and reduce the number of hardware boxes needed. It's not a huge problem MSC does the job, just not as neatly and means needing a dedicated midi interface when the QLab system is outputting sound via Dante, so no "free" midi interface in the audio interface.

Richard

The use here would be to fire cues from a QLab system. I have used MSC many times for this, and was hoping for a direct OSC replacement that would solve a particular cableing issue and reduce the number of hardware boxes needed. It's not a huge problem MSC does the job, just not as neatly and means needing a dedicated midi interface when the QLab system is outputting sound via Dante, so no "free" midi interface in the audio interface.

Richard

If we would implement commands like these, would you be able to use a Cobalt style command from QLab (like /cobalt/playback/goto xxx) or does it need to follow some format with restrictions? How would the cue number be passed over OSC to be most convenient with QLab?

Hi Richard . I had the same or similar issue with Qlab. When I get home I will pm you the qlab syntax which worked for me when written in qlab

Hi Anders,

This is where I stretch my knowledge I'm afraid! Figure53 describe QLab's OSC cue as able to "...send any OSC message over the network. You can also send raw UDP messages to equipment that doesn't speak OSC."

You can definitely send any custom OSC message so your example should be possible. For what it's worth the Eos "/eos/cue/xxx/fire" command works fine from Qlab.

Richard

That would be very helpful Andy!