You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you make a custom OSC target and set oAddress to another computer, it will fail with an unhelpful error message. This is because Tidal now sends OSC using the socket listening to cCtrlAddr, so the receiver can send OSC back to the port it received it from. This fits with supercollider's way of doing things.
Currently the default is 127.0.0.1. It is probably too much of a security issue to change that to listen and send from all interfaces with 0.0.0.0. But Tidal should at least print a warning the oAddress is changed and the cCtrlAddr isn't.. Or change the default to 0.0.0.0 in that case (and print a security warning).
The text was updated successfully, but these errors were encountered:
If you make a custom OSC target and set
oAddress
to another computer, it will fail with an unhelpful error message. This is because Tidal now sends OSC using the socket listening tocCtrlAddr
, so the receiver can send OSC back to the port it received it from. This fits with supercollider's way of doing things.Currently the default is
127.0.0.1
. It is probably too much of a security issue to change that to listen and send from all interfaces with0.0.0.0
. But Tidal should at least print a warning the oAddress is changed and the cCtrlAddr isn't.. Or change the default to 0.0.0.0 in that case (and print a security warning).The text was updated successfully, but these errors were encountered: