AudioUnit plugin vs. GarageBand sandboxing
AudioUnit plugin vs. GarageBand sandboxing
- Subject: AudioUnit plugin vs. GarageBand sandboxing
- From: Jeremy Friesner <email@hidden>
- Date: Mon, 06 Apr 2015 19:07:38 -0700
Hi all,
I’ve written a little AudioUnit effects plugin that uses a semaphore and a shared memory region in order to communicate audio data to/from a companion application. (it does this because only the companion application has access to all of the contextual information necessary to process the audio properly)
This plugin works fine under some 3rd party applications that support AudioUnit effects plugins, but when I try to use it within GarageBand, it fails to initialize. On investigation, this I found that it fails because because semget() returns -1 and sets errno to EPERM.
I’m pretty sure that is because newer versions of GarageBand run the plugin code inside a sandbox for security reasons.
My question is — is there any way to either get GarageBand to run the plugin without the sandbox restrictions, or for my plugin to request permission to use a semaphore and shared memory despite the sandbox? Or am I just out of luck here?
Thanks,
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden