Re: AU Components on the fly
Re: AU Components on the fly
- Subject: Re: AU Components on the fly
- From: Chris Reed <email@hidden>
- Date: Thu, 9 Jan 2003 13:31:13 -0600
Hi Urs,
Sure, it should be possible. If you look at the AUPublic headers,
ComponentBase.h in particular, there's the ComponentRegistrar class
that will do exactly this for you. And the COMPONENT_REGISTER macro to
make it easier. To go a little lower-level, the Component Manager has
the RegisterComponent() and RegisterComponentResource() functions.
The only thing I'm not sure about is if when you register a component
in your app, will it be made available in other processes?
-chris
On Thursday, Jan 9, 2003, at 10:32 US/Central, Urs Heckmann wrote:
Hi,
derived from the fact that the "real" API for AUs is that System stuff
and the whole AUBase is there for convenience, I asked myself if an
AudioUnit must be in a .component Bundle or could _any_ software
register to the OS as an AudioUnit?
Would it be possible to have a standalone application, name it
"FooAU.app" , that tells the System "Hi, I am here!" and when I launch
an AU host to have FooAU.app provide AU functionality for the host?
If not, would it be possible to create an AU .component that gets
loaded in a host but also talks to another app or would memory
protection kill my idea before even thought more about it?
Cheers,
;) Urs
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.