Re: Using an AU directly
Re: Using an AU directly
- Subject: Re: Using an AU directly
- From: William Stewart <email@hidden>
- Date: Thu, 10 Sep 2009 17:34:06 -0700
On Sep 10, 2009, at 2:27 AM, Darrell Gibson wrote:
Bill,
Sorry for the delay in replying (I've been out from the office.)
Thanks for your very detailed post, which has cleared up a lot of
confusion and vagueness I had.
Can I just clarify a couple of points with you? Is it possible to
have an AU that has an input callback AND a connection? If it is
what would happen in this situation?
An AU has a collection (zero or more) of elements (members) of a given
scope. We call the input and output scopes, buses (input and output
respectively of course). A bus can have any number of channels valid
for a given AU's configuration.
An input bus can only get input from one source, either a callback or
a connection.
It is also expected that only one caller is calling AudioUnitRender -
so, we do not support fan in or fan out types of modalities (mainly
because if every AU had to support this, certain memory optimisations
are not possible). If you want to use a fan in, fan out semantic, we
provide the AUMerger and AUSplitter audio units to do this for you.
Bill
_______________________________________________
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