• State Suggested Answer
  • Date
    John Demaree
  • Date
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 84 subscribers
  • Views 4882 views
  • Users 0 members are here

qlab controlling eos nomad cue timing issue

I got qlab calling cues in nomad thanks to this forum. However,  when I call a cue out of order it snaps to the cue.  I have used midi with our old 250 board and I am used to calling cues out of order because it always uses the timing of the called cue. Without this I'll have to rethink this whole setup.   Can this be fixed?   FYI:  Using osc string. eos/cue/xx/fire  in qlab.  Maybe I should try direct midi instead?  Or a different string?  

Thanks.

Parents
  • 0

    An update to my previous reply, it is a bit simpler than I said.

    You can simply send the command line via osc.

    So you should be able to send

    /eos/cmd/Go_To_Cue/100/enter

    The "Eos Integration via OSC.pdf" manual says

    "Your may also modify Eos show data. Typically you should build Eos command lines and send them with the command /eos/cmd or /eos/newcmd. "

Reply
  • 0

    An update to my previous reply, it is a bit simpler than I said.

    You can simply send the command line via osc.

    So you should be able to send

    /eos/cmd/Go_To_Cue/100/enter

    The "Eos Integration via OSC.pdf" manual says

    "Your may also modify Eos show data. Typically you should build Eos command lines and send them with the command /eos/cmd or /eos/newcmd. "

Children
No Data
Related

www.etcconnect.com