'ahal' unit vs. 'def ' question
'ahal' unit vs. 'def ' question
- Subject: 'ahal' unit vs. 'def ' question
- From: Stephen Davis <email@hidden>
- Date: Mon, 22 Mar 2004 10:45:43 -0800
What's the difference? If I want to support multiple output devices
but still want to use the output unit interface so I can tell it what
format I have instead of matching our output to its format, is there
any reason to use 'ahal' vs. 'def ' or vice-versa? Assuming I set the
kAudioOutputUnitProperty_CurrentDevice property of course.
The docs imply that they are not the same but opening the 'ahal' and
giving it audio data that doesn't match the hw (8 kHz mono) seems to
work just fine so it appears to be doing everything the 'def ' unit is
documented to do as far as format conversion goes.
Further, if I do use the 'def ' device and set its "current device"
property, will that change out from under me if the user changes the
output device in the sys prefs? The wiki page at
http://www.mat.ucsb.edu:8000/CoreAudio/16 says that the 'def ' device
will switch away from you but the 'ahal' one won't.
Finally, out of all these questions/answers, which do or do not apply
on Mac OS X 10.1.5? I need to know if the same code will work from
10.1.5 on or if I need to special-case any of this.
thanks,
stephen
_______________________________________________
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.