Eos Ion to Qlab Computer (NO TRIGGER)

[DGSound1]

I don't know how to resolve this issue, but I'm going to do my best to explain what is happening.

I set up the OSC Router so it can convert the Ion's fire language to a another that Qlab can understand. It has been working inconsistently throughout the week. Sometimes, the sound cues will delay from firing or not fire at all. Yesterday, it worked perfectly, but tonight it stopped working altogether. I'm perplexed as to why this keeps happening. Anyone who has insight on this issue, your advice is crazily appreciated.

[dorfman2]

Check out this thread. I started it because I have a similar setup to your (ION firing Q Lab). Still has it's issues (I think it has to do with packet loss), but maybe it can help you ask different questions for your setup. Also, Here's a copy of my Eos Ion Show Control settings. What made a huge difference in reliability is dictating the string sent (cue/%1/start). Using that, you can bypass OSCRouter entirely. I still use OSCRouter, because I have multiple Q Lab computers that need to all receive the OSC commands, but If I only had one machine, I wouldn't use it anymore.

Hope any of this helps!

Eos Family Show Control Settings.xlsx

[tm1000]

I've written my own OSC application and I see the same result from EOS consoles. The best advice is to just setup TCP on the EOS console and have OSCRouter connect over TCP. Don't use UDP.