• State Not Answered
  • Date
    cdzink
  • Date
  • Replies 6 replies
  • Subscribers 85 subscribers
  • Views 6023 views
  • Users 0 members are here

ETC Element running Q lab from ETC OSC router

I am new to the use of OSC.  I followed the guide found through this website and was able,to get a command string to go from the console to the ECT Router command text window.  It did not fire the Q lab cue.  I am running Q lab 4 and the latest EOS update on the Element.  I am sure I am missing something simple between the router software and Q lab.  Any help would be appreciated as I am not even really sure what questions to ask.

Parents
  • 0

    Hey,

    Take a read of this: blog.etcconnect.com/.../

    Breifly you need to send an OSC address pattern of /cue/X/start to QLab to fire a cue.
    You can do this a variety of ways but the simplest would be by executing an OSC command from a cue.
    [Cue][X]{Execute}{More SK}{string} /cue/X/start [Enter]

    The final things you need to do are:
    - Set the OSC TX IP Address to the mac's IP Address within Displays -> Setup -> Show -> Show Control.
    - Set the OSC TX Port Number to be 53000 (This is the port number OSC is received on within QLab) within Displays -> Setup -> Show -> Show Control.
    - Enable String and OSC TX within Displays -> Setup -> Show -> Show Control.

  • 0 in reply to Sammy
    if you have many cues that should trigger something in qlab, you could also use Eos' implicit OSC output. this is sent automatically with every Go. since the syntax Eos uses to do that is different than what qlab understands, you need to go to Setup > Show > Show Control > OSC Cue Send String and enter /cue/%1/start .

    you will still need to do the basic OSC config like Sam described above.
  • 0 in reply to ueliriegg

    Hi Ueliriegg,

    Nice to be able to spit out OSC messages with every EOS go, but how does one distinguish between OSC messages that are just blank outputs and those that are meant to actually do something with,  like fire the cue in Qlab?

    I hope this makes sense.

    ETC router makes it easy , but I can't figure how, with just using Eos and Qlab

    any suggestions for a newbie?

    Cheers,

    Mark

    Mark

  • 0 in reply to Mark Sutherland

    Qlab will not react to Eos messages unless you make Eos change the format of certain Eos messages so Qlab can understand them.

    if you use the Setup > System > ShowControl > OSC > OSC Cue TX String with the aforementioned string it will make Eos send every cue it fires in a format Qlab can understand. all the other implicit OSC output from Eos is still there, but since Qlab can't understand those it will just ignore them.

  • 0 in reply to ueliriegg

    By using "the Setup > System > ShowControl > OSC > OSC Cue TX String with the aforementioned string it" is OSC output from Eos not now a gobal command that Qlab will react to.

    How do I use it for one cue and not for another? Not sure I'm understanding correctly.

    I'm able to everything I want thru ETC Router, but not understanding how to make things work with out it.

    But I keep hearing that as of EOS v. 2.6.x  it is possible.

    Thank you for taking the time, to help. much appreciated

    ms

     

  • 0 in reply to Mark Sutherland

    ah, got it. it's not a general Go, it's a Go for a certain cue. the whole idea is that between Eos and Qlab you give things the same number if they should happen at the same time

Reply Children
No Data
Related

www.etcconnect.com