QLab from EOS is skipping cues

Pretty much what the title says. I am working on an Ion, firing sound through QLab, linked over OSC. However, the lights are firing correctly every night but a random sound cue is getting skipped each night. All of the settings look correct to me, and I can't figure for the life of me why it's a different cue every night. My mate there had swapped out all the hardware incase it was a bad connection, but it's still misbehaving even with a new switch, cables, and control computer. Does anyone have any suggestions? Thanks in advance!

EDIT: Working on getting some information from my mate there. I'm going in later and will update. Sorry for the delay.

0 sktusing over 3 years ago

Are you using TCP or UDP?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bharvey over 3 years ago in reply to sktusing

He doesn't know, and I'm not getting my hands on it until 3 PM today, but my guess is TCP from what he's said previously.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ueliriegg over 3 years ago in reply to bharvey

I don't think you can use TCP between Eos and Qlab unless there is a software in-between to establish the TCP connection (e.g. OSCrouter). If you don't have that then I don't think you're using TCP.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bharvey over 3 years ago in reply to ueliriegg

I'm just going by what he's saying until I can get my hands on things, but that makes sense. Thank you! If worst comes to it, I may have to download OSCRouter and do some rewriting, but that's not the worst.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 richardWilliamson over 3 years ago

A few things to check/test.. (I am assuming that you are hitting GO on the Ion, with sound fired over the network)

- Is your TX address (in eos show control settings) set to the actual IP address of the mac, or a broadcast address (ending in .255), if the latter then change it to the actual IP address of the mac as the broadcast messages often don't get through

- Is your mac connected directly to your ion with a single cable? If so try adding a switch in between, some people have found this helps

- Some people have had success making things more solid by constantly pinging the ion from the qlab machine (open a terminal any type "ping " followed by the IP address of the ion. This shouldn't make a difference but theoretically may serve to keep the network port open and active.

Richard
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bharvey over 3 years ago

So I went in, used your advices and stuff from a few other forums and friends, and there were certainly some issues with how it was set up - subnet issues, gateways etc. Fixed them all, and a new issue manifested. So I'm erring closer and closer to either bad hardware (it's an old Trashcan, and my sound guy says it's been playing up, so that could well be it), or a bad operator - they aren't experienced with EOS and I don't entirely trust they aren't just missing cues or double-tapping.

Thanks for your help, all.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ueliriegg over 3 years ago in reply to bharvey

don't forget that you can always pull logfile to help you diagnose things. you would see when cues were fired, but by default OSC strings don't log.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel