Re: unloading plugin bundles - is it a bad idea?
Re: unloading plugin bundles - is it a bad idea?
- Subject: Re: unloading plugin bundles - is it a bad idea?
- From: Ross Bencina <email@hidden>
- Date: Sun, 04 Nov 2012 12:00:49 +1100
Hi Paul,
On 4/11/2012 11:29 AM, Paul Davis wrote:
i can tell you that we never explicit use CFBundle{Anything}. we use the
apple utility library, and our destructor for an AudioUnit basically
involves calling CAAudioUnit:::Uninitialize() which actually calls
AudioUnitUninitialize(). there are no calls to CFBundle{Anything} in the
(antiquated) apple utility lib that we use.
You're quite right. This is a VST plugin. I don't use the Apple classes
for AU, but my AU code uses Component Manager APIs (OpenComponent() etc)
not CFBundle APIs -- so the explicit bundle unloading is only happening
in my VST code. Sorry for the confusion.
A quick check indicates that unloading an Audio Unit plugin with
CloseComponent() doesn't appear to unload the plugin's bundle.
Another data point:
"Cocoa applications cannot unload bundles."
https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/LoadingCode/Concepts/MultiBundleApps.html
Thanks,
Ross.
_______________________________________________
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