Re: Channels, Busses and I/O Configurations
Re: Channels, Busses and I/O Configurations
- Subject: Re: Channels, Busses and I/O Configurations
- From: Art Gillespie <email@hidden>
- Date: Sun, 26 Oct 2003 18:22:51 -0500
>
>> (2) Introduce a new property:
>
>>
>
>> kAudioUnitProperty_I_O_Configuration
>
>> and kAudioUnitProperty_I_O_ConfigurationName
>
>> and kAudioUnitProperty_I_O_NumConfigurations
>
>
I dig this solution more than my (don't blame poor Urs!) silly iterative query
mechanism suggestion and *much* more than the 'two-builds' proposal. But see
below for my *real* feelings on the topic...
>
> This in a way seems nice, although on the other hand, I think that it
>
> starts to make the AU API seem too complicated to newcomers.
>
>
True - but this is in response to requests from AU developers (we're
>
not pushing this),
FWIW, I'm not nearly as interested in solving this theoretical 'problem' as I
am in some sort of advocacy to encourage host developers to support the API as
it's written now. I'm not sure if adding more complexity to the API while
nobody has yet managed to get the 'simple case' right is the solution.
If you can't get Brand X Audio Unit host to query homegeneous output busses,
complex heterogeneous i/o configurations with dependencies might be a bit off
yet.
Best,
Art
>
>0xBA
_______________________________________________
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.