Eos OSC no responses.

I'm not familiar with the libraries you are using and am too lazy to dig into them. Most of my OSC experience is with embedded processors and the CNMAT/OSC library.

The diagnostics tab (Tab 99) will confirm Eos is sending and receiving OSC messages. That will help isolate the problem to your code.

If Eos is not sending /eos/out/<whatever> messages in response to your /eos/<whatever> message then confirm OSC TX is enabled and OSC UDP TX Port is set to 8001.


After that, it's likely due to your code. /eos/subscribe and/or eos/filter can suppress responses. SLIP settings may influence whether your OSC library can decode the message.

Wireshark is a useful tool in the early stages of debugging an OSC app.

Thanks sk8rs_dad . I have been using the diagnostics tab and I can see the packets going out, but I do not see them going through wireshark unless they are encrypted. the library I am using relies on UDP.  Below is my Configuration and output. I am suing OSC 1.0 and not SLIP 1.1. 

Thanks sk8rs_dad . I have been using the diagnostics tab and I can see the packets going out, but I do not see them going through wireshark unless they are encrypted. the library I am using relies on UDP.  Below is my Configuration and output. I am suing OSC 1.0 and not SLIP 1.1. 

The packets are going out on [USB 1] but they aren't going out on [Global/UDP]. Specify an OSC UDP TX IP Address in setup. If you don't know your client's IP then try using your network's multicast IP. For a 192.168.1.1/24 network that would be 192.168.1.255.

You should also have a look at the packets going into Eos. Just because you're getting Eos to react to them, doesn't mean that they're actually formatted correctly. Use Wireshark to check if what you're sending (and receiving) is actually OSC and not just any regular UDP packet.