There are three different settings for objective-c garbage collection:
Unsupported (which is the default setting for XCode)
Supported
Required
If a plugin is compiled with the Supported code generation option, it
should work in both gc and non-gc environments. An unsupported plugin
would crash in a GC required host as would a gc required plugin in an
unsupported host.
The coreaudio sdk has a sample host application in /Developer/Examples/
Audio/Services/ called CocoaAUHost. This host supports garbage
collection and you can use it if you want to experiment. At this time,
however, I know of no shipping commercial audio unit host that
supports garbage collection. Not sure when they plan to support this
feature.
Hope this helps!
-michael
On Jan 23, 2008, at 5:51 PM, Todd Blanchard wrote:
A thread on the Cocoa list implies that any app that uses plugins
can only use plugins that were compiled with the garbage collection
option set the same. IOW, an AU host compiled with GC on, can only
load AU's compiled with GC turned on?
Or is GC something that just doesn't make sense in an audio
processing situation for performance reasons?
Just wondering where this is going. Are AU's all going to use GC
one day or is this not at all likely?
-Todd Blanchard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
