Serial UDP and OSC not working together

MacTommy said:

1.171.4 8.121

This is not a valid address for private networks, maybe this is the problem. Also have a look to your subnet setting.
Are QLab setting ok?

We doublecheck the IP-address, the right IP to our videoserver is 10.171.48.121 and not what I wrote from beginning.

So IP-adress is not the problem, our subnet mask is ok. It works either with OSC or String UDP, but not togheter. That´s the main issue...

Would you be willing to post a showfile with this issue so that we can have a look at the various settings?  We probably only need your Macros and Show Control / Setup if you wish to create a sample show without your Magic Sheets and other proprietary content.

I fix it tomorrow. I can try my testshow and enable OSC, if it's same problem I post that one. No magic. :)

I also going to sniff networkport 2 and turn on OSC-settings to see if I got my "String UDP" sending to another UDP-port when both are active.

Not a answer to why this is not working.
But it may be of interest ...

Have you checked out Chataigne?
http://benjamin.kuperberg.fr/chataigne/en

Maybe something that helps and you don't need to programm an arduino. 

Thanks... but it´s fun to code. ;)

The problem is not my code, it´s in the EOS-software I believe. ;)

Now I try my test showfile. 

This is how my network interface protocol is setup.

I connected a computer to port 3 and run Wireshark and sniff my network. When I have OSC TX disabled it send out "Serial UDP" and when i turned it on it stops sending "Serial UDP". It doesen´t matter if I had my extra computer connected to the consolles or not.

I changed interface protocol to same as port 4 when I tested it with WireShark. So the picture is my normal setup for OSC and Serial UDP.

I also try to set an IP for my OSC to my computer with Wireshark. When I turn OSX TX enabled it send a OSC-command to the computer and no "Serial UDP". OSX TX to disabled it send Serial UDP again.

So it look like I can´t send OSC and Serial UDP in same show in this software version. 

I email the showfile to you Matt to the email in your profile. Is there another way to upload it in the forum? Only found image and video-upload. Thinking of sprend but it is just 5 people that could download it before it stops because i´m not PRO.

I also try to change my macro number from 9xxx to 1-8. So it´s not a macro number issue. But, same same... ;)

Hello MacTommy , thank you for sending the showfile.  It was very helpful.

The issue you are running into is that your Send String macros (and maybe other Strings you might send Executed by a Cue) are formatted like OSC.  So they look like this:

/thing/all/1>1/

When Eos encounters a string like that to send, it assumes you want that to be sent as OSC since it is following OSC norms, so Eon sends it down the "OSC Pipe" (in your case, sending to Port 53000).  Eos v3.1.1 Operations Manual - Explicit OSC Output

To force a string to use the "String" pipe (in your case, Port 8001), preface it with "udp:"

Send_String udp:/thing/all/1>1/

I do not see this documented in the User Manual, so I will see about getting it into a future version.

EDIT: This option was added in v2.3.2: [EOS-32588] Serial strings with "udp:" prefix should never be sent as OSC - Jira

I did find this forum post from many years ago that describes this feature: sending Strings over Ethernet, Bug, Question - Eos Family Show Control Support (MIDI, SMPTE, OSC, RTC, etc) - Eos Family Consoles - ETC - Community 

Hi and thanks for that clearifaction Matt. 

I rebuild my script so it filter out all non "OSC IDK"-commands, because EOS send out "fire"-command every GO. I also change networkport so it´s same as our QLab-machine and added my Arduino-IP on the OSC-setup so I have multiple IP on OSC-output. So now it works fine when I tested it whitout serial UDP enabled...