Re: AUHAL Full duplex issues
Re: AUHAL Full duplex issues
- Subject: Re: AUHAL Full duplex issues
- From: Brian Willoughby <email@hidden>
- Date: Tue, 10 Aug 2010 22:09:41 -0700
On Aug 10, 2010, at 21:38, Aridis-Lang, Simon wrote:
... I don't understand why if the AUHAL is an audio unit, and my
'IOProc' is registered on the audio unit, why an audio unit
property is the wrong answer? Could you elaborate on how the AUHAL
abstracts the HAL and how these two settings interact (is one
ignored? is it the minimum / maximum of the two?). A lot of
example code out in the wild is setting both so it would help to
understand why others have settled on this arrangement.
AUHAL is a convenient translating link between an application and the
HAL, but AUHAL is still completely separate from the HAL. If you
want to change the hardware buffer size, then you need to find the
AudioDevice via a different API and send it the message that Bill
mentioned. I don't think he meant that you could send the HAL
message to the AUHAL and expect it to work, although it might be an
interesting feature to request (i.e. that the output scope of the
AUHAL pass buffer size messages on to the HAL device).
Brian Willoughby
Sound Consulting
_______________________________________________
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