Re: AU Format Negotiation - State of Affairs
Re: AU Format Negotiation - State of Affairs
- Subject: Re: AU Format Negotiation - State of Affairs
- From: Marc Poirier <email@hidden>
- Date: Sun, 26 Oct 2003 14:58:57 -0600 (CST)
earlier today, I wrote:
>
kAudioUnitProperty_SupportedNumChannels may not be required, but not
>
implementing it has a very specific meaning: it proclaims that your AU
>
can handle any N-to-N channel configuration. So if that's not the case,
>
then you do need to implement support for the property.
Oops, I'm sorry, I didn't realize that that was only true for effect AUs
and not MusicDevices. I'm catching up on this week's emails now and I
just read this from Bill's later email:
>
If the property is not supported the following behaviours/assumptions
>
can be made by hosts:
>
>
(1) An AU is an effect type of unit (this essentially covers AU's of
>
type 'aufx', 'aufm' and 'auol' (offline units))
>
- assumption is today's practise (host assumes unit can do {-1,-1}
>
config
>
>
(2) An AU Panner unit will be expected to support this property (as it
>
is currently specified, this is a single in to out I/O path)
>
>
(3) A Synth unit ('aumu')
>
- Doesn't publish property, then it is assumed that its initial
>
configuration represents its channel and I/O possibilities.
Sorry,
Marc
_______________________________________________
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.