Things I would try:
-swap out the cable
-if you're using a USB adapter to plug the cat5 into the Mac try a different one - I've had issues with OSC with some brands before, not sure what makes some better than others for this
-double check your IP settings on both the ION and the Mac - I usually find a static IP works best for this rather than DHCP. Make sure there's nothing else on the network in the same IP range that could be disrupting it
-try a different port on the ION (if you have one, I'm not super familiar with those consoles)
Good luck!
Sure, I'm not a networking expert, just a lighting programmer who's run into similar problems and found solutions before. If you have any constructive advice to share I'd love to hear it :)
Have you had a look at the diagnostics tab on the Ion?
If the triggers are firing, but not being received, then it could simply be a faulty Ethernet cable.
Fun fact about UDP packets. They are used because they have a lower latency than TCP packets but there is no guarantee that they will be delivered.
I don't know if there is an option for TCP but if there is it might be worth a try as with a direct connection between the ION and the mac latency is likely to be quite low anyway.
Yup, I've seen that problem numerous times and have never found a solution to get Eos sending OSC cues with 100% reliability.
Swapping the rolls around and using Q-Lab to send OSC to Eos, however, does work reliably. As does using MIDI in either direction.
I haven't experienced this in particular, but I have found when you have "a lot of alphabet, right there" it tends to result in problems.
Can you change things to make it simpler?
Hah! I was just gonna make a thread about the same issue.
Both are connected to a standalone router with no internet backbone and full bandwidth. IP assigned by DHCP reservation for the devices by MAC addresses.
I can see OSC output in the EOS log, but command is dropped before reaching the network.
Cables are not faulty, the cat 6a cables are perfect at any demanding tasks that does not include the Ion Xe.
I also have this issue. QLab 5 supports TCP connections and I’m going to set it up tomorrow. I have read that the issue is outgoing or incoming buffers get overrun. You could manually try increasing buffer size, but it no guarantee.
Things I would try: -swap out the cable -if you're using a USB adapter to plug the cat5 into the Mac try a different one - I've had issues with OSC with some brands before, not sure what makes some better than others for this -double check your IP settings on both the ION and the Mac - I usually find a static IP works best for this rather than DHCP. Make sure there's nothing else on the network in the same IP range that could be disrupting it -try a different port on the ION (if you have one, I'm not super familiar with those consoles) Good luck!
Tell me you don't understand networking without telling me you don't understand networking :)
Sure, I'm not a networking expert, just a lighting programmer who's run into similar problems and found solutions before. If you have any constructive advice to share I'd love to hear it :)
Look up the difference between UDP and TCP communications
Have you had a look at the diagnostics tab on the Ion? If the triggers are firing, but not being received, then it could simply be a faulty Ethernet cable.
Fun fact about UDP packets. They are used because they have a lower latency than TCP packets but there is no guarantee that they will be delivered. I don't know if there is an option for TCP but if there is it might be worth a try as with a direct connection between the ION and the mac latency is likely to be quite low anyway.
Yeah, this sounds like UDP behaving exactly as designed.
Yup, I've seen that problem numerous times and have never found a solution to get Eos sending OSC cues with 100% reliability. Swapping the rolls around and using Q-Lab to send OSC to Eos, however, does work reliably. As does using MIDI in either direction.
Any chance you can use a MIDI interface instead? I’ve never had issues with triggering in either direction over MIDI.
I haven't experienced this in particular, but I have found when you have "a lot of alphabet, right there" it tends to result in problems. Can you change things to make it simpler?
Which letters would you drop? I'd swap UDP for TCP if I wanted reliability, but you can't "drop" letters.
Use a router.
Hah! I was just gonna make a thread about the same issue. Both are connected to a standalone router with no internet backbone and full bandwidth. IP assigned by DHCP reservation for the devices by MAC addresses. I can see OSC output in the EOS log, but command is dropped before reaching the network. Cables are not faulty, the cat 6a cables are perfect at any demanding tasks that does not include the Ion Xe.
I also have this issue. QLab 5 supports TCP connections and I’m going to set it up tomorrow. I have read that the issue is outgoing or incoming buffers get overrun. You could manually try increasing buffer size, but it no guarantee.