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