Re: audio unit deinstantiation thread
Re: audio unit deinstantiation thread
- Subject: Re: audio unit deinstantiation thread
- From: Paul Davis <email@hidden>
- Date: Wed, 13 Jul 2011 10:31:53 -0400
On Wed, Jul 13, 2011 at 10:18 AM, Jeremy Todd <email@hidden> wrote:
> Hello,
>
> We recently noticed that Soundtrack Pro 3.0.1 is instantiating our plug-ins on the main thread, but in some cases (Render to Action) deinstantiating them on a different thread. This is not something our plug-ins expect, and I'm wondering if it's considered a valid host behavior?
>
> We're also seeing that the component representing our Audio Unit is closed before our UI is deallocated (we have a Cocoa view in this case). This is also unexpected, although much easier to work around than the above behavior.
Neither aspects are documented, since basically, being an AU host is
almost completely undocumented. I can tell you that both Ardour and
Mixbus will close your AU component before deallocating the GUI in
almost all cases. We will also make no conscious effort to
deinstantiate the plugin in the same thread as the one it was
instantiated in, but given that there's no way to delete a plugin via
MIDI or OSC control, it will generally happen in the GUI thread that
created the plugin. I would consider entirely valid to do this in
another thread, and you won't find anything from Apple that says
anything about this.
_______________________________________________
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