Firing Qlab from EOS

Question

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

JohnnyFocus · Accepted Answer

Hi Josh, 
I noticed in your second image uder OSC Cue Send String, you have Cue instead of cue. Are you using the Cue hard key, typing it in from the keyboard? 
I wasn't able to get a track on Go Button to trigger until I physically typed 'cue' in the string. 
Hope this helps. 
 
Johnny

ueliriegg · Answer

ah sorry, that was a misunderstanding on my part. i thought you had matching numbers. sorry about that. 
 
there is some stuff to change: get rid of /cue/%1/start in setup. it's part of the automatic (aka implicit) stuff, that doesn't work for you, because that would need matching numbers. and then add a qlab specific OSC string to cue 296: Cue 296 Execute String /cue/7/start Enter. you would have to do this (with the correct qlab cue number) for all the cues you want to interact