• State Not Answered
  • Date
    Jkar Gorostiza
  • Date
  • Replies 16 replies
  • Subscribers 87 subscribers
  • Views 22260 views
  • Users 0 members are here

Eos-Nomad with Qlab Instability

hello everyone.

I can not run Qlab (v 3 .... v 4) in stable mode with EOS-NOMAD via OSC. By midi (MSC) the interaction is totally reliable and does not present any problem ... but OSC has a greater potential of instructions, there my obsession to make it walk.

My goal is for EOS-NOMAD to activate the QLAB cues, and it does so but in an irregular way which gives a lot of insecurity. In the soft EOS does not seem to be the problem, if we go to Tab 99 (diagnostics) and put (On) Outgoing OSC we see how EOS sends the instruction string (send String: / cue / 1 / start) (OSC Packet), in Qlab click Status, open the Logs tab and activate OSC input to see what goes in ... and here we see that sometimes the instruction string arrives and others do not, it is lost.

These are the configurations. What am I doing wrong? Where is the error?

Thank you.

Parents
  • 0
    This feels like you want to use OSC through TCP and not UDP, but I don't know if Qlab supports that...
  • 0 in reply to ueliriegg

    Hi ueliriegg.

     
    Thanks for showing interest. In the qlab tutorial says:

    QLab accepts incoming OSC messages via TCP and UDP over a local network.

    All software or devices which support OSC have their own dictionary of commands. You can use hardware like ETC's EOS family to send messages that exist in QLab 4's OSC dictionary.

    Any other suggestions?

    Thank you.

     

    Launch from EOS cue 1 to activate in Qlab (/ cue / 1 / start).

    Qlab does not receive the order, the music track does not activate.

    Second try. I throw again from EOS the cue 1 containing for Qlab (/ cue / 1 / start).

    Now if the audio track sounds. In the status window for OSC in Qlab, the EOS command is seen to have entered.

    I shoot the cue 2 of EOS to tell Qlab (/ cue / 1 / stop), for the audio ..

    ... but qlab continues to play the audio .... the stop order is lost ...

    Puff ... I do not know ... what to try... [C] [*-)] [C] 

  • 0 in reply to Jkar Gorostiza
    How do you decide, that qlab should listen to TCP and not UDP?
  • 0 in reply to ueliriegg

    I wanted to check in reverse ... activate with Qlab (v 4.0.4) the cues of Eos through OSC, but I have to say that I find it impossible for now, however with Qlab (v 3.1.24) without problems .

    In the version of Qlab 4.0.4 to activate the signals from Eos you have the options to send by OSC or communicate by UDP, but I can not do either.

    My conclusion is that Qlab in its new version presents difficulties to work with OSC .... problems that will correct. 

    Corrections in the new version.

    QLab 4.0.5 Release Notes

    FIXED: QLab is now less strict about requiring the expected number of arguments for certain OSC commands, allowing third-party software that always sends OSC arguments (e.g. TouchOSC) to again work with certain QLab OSC methods.

    .........????? 

Reply
  • 0 in reply to ueliriegg

    I wanted to check in reverse ... activate with Qlab (v 4.0.4) the cues of Eos through OSC, but I have to say that I find it impossible for now, however with Qlab (v 3.1.24) without problems .

    In the version of Qlab 4.0.4 to activate the signals from Eos you have the options to send by OSC or communicate by UDP, but I can not do either.

    My conclusion is that Qlab in its new version presents difficulties to work with OSC .... problems that will correct. 

    Corrections in the new version.

    QLab 4.0.5 Release Notes

    FIXED: QLab is now less strict about requiring the expected number of arguments for certain OSC commands, allowing third-party software that always sends OSC arguments (e.g. TouchOSC) to again work with certain QLab OSC methods.

    .........????? 

Children
Related

www.etcconnect.com