EOS Nomad OSC Output bug/issue

Nomad PC 2.3.2 - Primary.

I'm working on an app to read data from the EOS output stream and I'm finding that eos/out/pending/ does not output reliably for every cue. I'm using OSC Router to view the stream as well as my app and it drops */pending/* about once in 20, but not reliably on a consistent cue.

Parents

Druuka over 9 years ago

If you are using OSC over UDP as your method of communication you should know that UDP packets are not guaranteed to get to their destination and that they may get there out of order. TCP is the method you want to use if you need more reliability. Depending on the traffic during those packets you may miss some of them.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Druuka over 9 years ago

If you are using OSC over UDP as your method of communication you should know that UDP packets are not guaranteed to get to their destination and that they may get there out of order. TCP is the method you want to use if you need more reliability. Depending on the traffic during those packets you may miss some of them.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

cjLights over 9 years ago in reply to Druuka

Thanks Andrew! Although the code library I'm using doesn't support TCP, i learned how to use it properly for my show and syncing between QLab and the ION.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel