Re: Multiple Output Music Device
Re: Multiple Output Music Device
- Subject: Re: Multiple Output Music Device
- From: Art Gillespie <email@hidden>
- Date: Fri, 17 Oct 2003 18:07:27 -0400
kAudioUnitProperty_SupportedNumChannels, kAudioUnitScope_Input,
Element:0
Currently, the response is kAudioUnitErr_InvalidScope
Really? That's amazing! That's what my AUBase.cpp does, too! The
coincidence is astounding.
My point was -- *if* the element parameter were added to
SupportedNumChannels, then kAudioUnitErr_InvaidElement, *would* be the
correct response for GetProperty on an element that doesn't exist.
(using the AUBase
SDK). I think that one thing that you missed here is that Global is
currently the only valid scope for querying the SupportedNumChannels
property.
Erm, that require(kAudioUnitScope_Global) in AUBase wouldn't be there
any more if you did the per-element thing, because the host would need
to send those queries on the Input or Output scope.
SupportedNumChannels on the Global scope really doesn't make any sense
in the first place if you're interested in different output elements
since
"The global scope always contains only one element, with index 0."
from the AU docs.
I think you misunderstood my message. I was comparing the current
proposal (yours) with what I think is ideal, not how the SDK works
currently.
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.