Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSC messages broadcast on subnet not detected by OSC input module #220

Open
jjpaq opened this issue Feb 21, 2024 · 1 comment
Open

OSC messages broadcast on subnet not detected by OSC input module #220

jjpaq opened this issue Feb 21, 2024 · 1 comment

Comments

@jjpaq
Copy link

jjpaq commented Feb 21, 2024

Environment

  • OS: Windows 10
  • Version 1.9.17

Describe the bug
When trying to listen to execute feedbacks from a Chamsys QuickQ lighting board, which are broadcast as OSC messages on the local subnet (10.14.4.255, in our case), the messages are not detected and do not appear in the log.

To Reproduce
Steps to reproduce the behavior:

  1. Enable OSC feedback on the QuickQ.
  2. Verify that the OSC messages are being received on the computer where Chataigne is installed (in our case, verified with Wireshark and OSCRouter).
  3. Add an OSC input and set the port where the messages are being received (9000).
  4. No OSC messages are detected or shown in the log.

Expected behavior
OSC messages sent to the subnet broadcast address should be received by the NIC with an IP on that subnet (10.14.4.20, in our case).

Additional context
I'm submitting this as a bug because the behaviour appears to be intermittent - there's no pattern that we can see, but sometimes the messages will or won't be picked up by one computer or another, with identical .noisette files loaded. It's possible that it's not a "bug" per se, if it's due to a networking limitation or something else, but since OSCRouter can detect these packets so reliably, I'm inclined to think there's a solution. (I wish we could just leave OSCRouter running in the background to forward the packets to Chataigne, which works perfectly, but this is a production machine and we're trying to minimize the number of applications running in the background.)

Thank you!!

@benkuper
Copy link
Owner

Hello,
Chataigne can't listen to a port that is already used by another software. Can you make sure no other software is bound to that port ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants