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.

0 Jkar Gorostiza over 7 years ago in reply to Richard

Hi.

First of all I want to thank you for all your help.
Today I tried with a low performance swicht (10 / 100Mbps) and goes perfect. Richard, you were absolutely right. Thank you. The problem is solved. These were not erroneous configurations, but the direct connection between computers gave the failure. I followed your advice, and perfect. [:D]

I want to thank you all for your help.
Richard said:
It is always best to have a switch in the middle.

Many network cards want to see the other end running before they can properly link up. If they don't start up in the right order, you may end up with no link, an intermittent connection, or a very slow (half-duplex 10 Mbps) connection.

In some cases, both ends want the other to be turned on first - which is of course, impossible to do.

If you have a switch in the middle, it can be turned on before either machine (or application) is started, avoiding this problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel