Re: Multichannel configs etc.
Re: Multichannel configs etc.
- Subject: Re: Multichannel configs etc.
- From: Glenn Olander <email@hidden>
- Date: Fri, 12 Nov 2004 11:56:40 -0800
On Friday, November 12, 2004, at 11:19 AM, William Stewart wrote:
But, there's a problem currently... We're going to introduce a new
property
called ElementInUse (EIU) that a host can set on these buses... The
problem
is that for an input you know whether you have a connection or not,
but for
an output you don't, until you are called for the first time! So, you
have
to assume currently that all of your outputs are in use.
So, the idea would be this. We'd default the implementation (for
compatability reasons) of this EIU to true for each bus. A host can go
through and enable/disable elements as the AU is configured...
With all due respect, are you sure you want to make things more
complex? Mike is one of the smartest people I know, and if he's
confused, maybe we should be taking that as a signal that multi-outputs
are over-engineered. I don't think it's a coincidence that after 2
years we're still waiting to see a host which properly supports
multi-outs.
For instance, you can do up to 16 channels. So your
SupportedNumChannels is
published as { 0, -16 } (BTW, that's ALL you need to publish!)
Then the host will go and configure some number of combinations of
buses and
channels (your AU doesn't really care!!!) as long as that total channel
count is <= 16
That's one of the places where the current model breaks down. Yes, the
AU cares. It will generally have GUI and other state changes to be made
to reflect the change in the output configuration.
- Glenn
_______________________________________________
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