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: Verizon <email@hidden>
- Date: Sat, 03 Nov 2012 14:21:43 -0400
- Importance: Normal
Hello Ross,
""I'm not sure I follow you here. Can you clarify what you mean by "in use
for other plug-in types" please?""
It has been a long time but I believe this may only be a problem if you host
both VST and AU at the same time. If you unload the executable for one it
may crash the other.
it is important
(and mandatory on certain plug-ins, e.g. Korg) to do a check on the
retain count.
""Are you suggesting that some plugins retain their own bundle? Would you
be able to give a specific Korg plugin as an example so I can test it?""
I think all of the Digital and Analog Korg Legacy collection.
""I'm wondering whether in the code below your app is holding multiple
references to the bundle, or whether you're only holding one and the
other reference(s) are held by the plugin itself.""
No. I am not holding any references. I just don't want to unload the
executable if it is use by something other than me.
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