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

How to let Mac AU audio plugins communicate with each other via network stack while blocking access to the internet #658

Open
bythesea123 opened this issue Nov 3, 2024 · 1 comment

Comments

@bythesea123
Copy link

bythesea123 commented Nov 3, 2024

Hi!

The Mac AU plugins on Apple Silicon run in separate instances, so the way some of these communicate is via the network stack. Many AU plugins, for example those from iZotope, crash when they cannot access this. I believe the relevant app is AUHostingServiceXPC or AUHostingServiceXPC_arrow.

Is there a way to keep internal communication going while blocking it to the outside? Must one enter certain ports or wildcards, for example, instead of a star to block it all? Should they be separated with a special character, i.e. '21; 990; 443' or '*.com; *.net'?

I don't think AU plugins should have the right to access the internet without any notice or control. License management for example can be handled with separate apps, and there is no reason to enable AU plugins tracking when a producer is working on a song.

Thanks

@bythesea123
Copy link
Author

Okay, as no one answered here, this info is for anyone using Sonible plugins. These communicate via AUHostingServiceXPC_arrow on port 226.0.0.1, so this has to be allowed.

Regards

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