• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    jmse14
  • Date
  • Replies 8 replies
  • Subscribers 87 subscribers
  • Views 9582 views
  • Users 0 members are here

Firing Qlab from EOS

Hi everyone,

Sorry for what seems like a topic that has been pretty well covered but I'm new to using OSC and networking in general and I'm still having issues getting this to work properly. I'm working with my audio tech to get my GIO console to fire sound cues in qlab over OSC. I'm pretty confident after searching the facebook group and the forum that I have my console set up correctly but as I said I'm new to this and some of the postings were recent and some were from when v2.3 was first released so maybe I'm just confused. To us it seems as though the piece we can't get right is the syntax in the qlab GO command. We know qlab is receiving OSC commands because he is able to capture a string in the OSC controls page:

However this will only fire the Qlab cue that is attached to eos q 296 and we're trying to trigger a Qlab cue when any EOS cue has the Execute string /cue/#/start syntax attached to it. Here is what my settings look like:

 

Thank you in advance for any help/insight!

 

Josh

Parents
  • 0
    with those settings you shouldn't need separate cue execute strings. there are two basic ways of how to send OSC: they're called explicit and implicit. explicit are the ones you define specifically like execute cue strings. implicit are the ones the console sends automatically. you defined the format for the implicit Go commands in OSC Cue Send String.
    if you're familiar with Midi, you can compare the implicit ones to Midi Show Control and the explicit ones to Midi Notes.

    if you open Tab 99 (Diagnostics, Hold Tab, type 99, release Tab) and then click on OSC Output (it's only to have them displayed, not about really sending or not), you should be able to see what the console actually outputs.
  • 0 in reply to ueliriegg
    Got it. So if I were to clear the OSC Cue Send String of /cue/%1/start would everything else in our set up be correct for sending explicit strings? That was something I just found in another post and started experimenting with today; up until now I've had that field empty.
Reply Children
Related

www.etcconnect.com