Closed alx-s closed 2 years ago
@jvlyndark I believe this is not relevent to the current state of the OSC and must be an older bug you fixed since. can we close?
Is this bug still occurring? Answer: yes.
Refactoring this might require the OSC sender to be access the generator that sends the OSC message. (?)
Question: Can't we simply add an argument to a new method of the OSC sender?
We might fix this bug later, but we'll probably need to make sure we still have a backward-compatible OSC Interface, and keep the existing legacy OSC message signature within the same major version.
Current output messages are in the form
/input /SpinkingNet_01/output f f f f
Instead, they should be:/SpinkingNet_01/output f f f f