Re: AU: interpreting kAudioUnitProperty_SupportedNumChannels & _BusCount in modular hosts?
Re: AU: interpreting kAudioUnitProperty_SupportedNumChannels & _BusCount in modular hosts?
- Subject: Re: AU: interpreting kAudioUnitProperty_SupportedNumChannels & _BusCount in modular hosts?
- From: Paul Davis <email@hidden>
- Date: Tue, 18 May 2010 20:09:51 -0400
On Tue, May 18, 2010 at 7:53 PM, William Stewart
<email@hidden> wrote:
> Should I even care about this? do most AU's return specific channel counts or -1,-1?
I guess we tend to approach from the other way around - given a particular context, what are the number of channels in and out that make sense... Given that, which AUs support those possible configs... - you just ask the AU (can you do this config...)
just to reinforce bill's description, ardour does the same. the key method related to this is bool AUPlugin::can_do (int in, int& out), which basically answers the question "can you support N inputs, and if so, how many outputs will you have?" We follow the signal path and ask each processing element along the way (which could be an AU or something entirely different) this question. The outputs from the previous processing element provide the number of inputs to give to the next element. The number of inputs is fixed by the container of the signal graph, and the number of outputs floats depending on the final answer.
--p
_______________________________________________
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