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

Sending to another computer needs a cCtrlAddr setting #926

Closed
yaxu opened this issue Jul 13, 2022 · 1 comment
Closed

Sending to another computer needs a cCtrlAddr setting #926

yaxu opened this issue Jul 13, 2022 · 1 comment

Comments

@yaxu
Copy link
Member

yaxu commented Jul 13, 2022

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).

@yaxu
Copy link
Member Author

yaxu commented Sep 29, 2022

Duplicate of #793

@yaxu yaxu marked this as a duplicate of #793 Sep 29, 2022
@yaxu yaxu closed this as completed Sep 29, 2022
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

1 participant