Re: Registering AudioUnits at runtime
Re: Registering AudioUnits at runtime
- Subject: Re: Registering AudioUnits at runtime
- From: Marc Poirier <email@hidden>
- Date: Fri, 5 Nov 2004 12:04:44 -0500
There are Component APIs for registering Components from memory. But
the problem with this approach is that a host may very well build its
list of available AUs before your AU has a chance to register your AUs,
and thus the host wouldn't ever notice your extra AUs. The host can
get a list of all AUs using FindNextComponent() without having to
OpenAComponent() any of them.
This is arguably a shortcoming of the Component Manager. It's the
reason why packages like Pluggo, Waves, the TC|Works AUs, etc. all have
a separate app for generating the AU resources to reflect what is
present on the user's system.
Marc
On Nov 4, 2004, at 2:43 PM, Makira wrote:
Hi all,
I'm trying to make an audio unit which, upon loading, would read from a
directory some models, and then for each of them register an audio
unit. How
can I do this ?
Do I have to make a dummy audio unit, and with the help of a static
global
instance, register more in the constructor using COMPONENT_REGISTER
from
Apple's sdk ? Problem is that I don't want any dummy audio unit
appearing in
the host.. Or can I make a generic component which will register the
audio
units - but will the host load the component if no audio units are
listed in
the ressources ?
Regards,
Makira
_______________________________________________
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