Re: Audio driver starting delay
Re: Audio driver starting delay
- Subject: Re: Audio driver starting delay
- From: Jeff Moore <email@hidden>
- Date: Wed, 22 Mar 2006 11:34:04 -0800
There are no guarantees about the amount of time that will pass
between telling the HAL to start IO and it actually starting.
Further, starting the hardware is inherently an asynchronous. In
order to know when the hardware starts or stops, you need to listen
to the property, kAudioDevicePropertyDeviceIsRunning.
On Mar 22, 2006, at 9:00 AM, Stéphane Letz wrote:
On a Mac mini intel, we see a several second delay between the call
to "AudioOutputUnitStart" (we are using AUHAL to drive the real
driver) and the first time the audio callback is called. This delay
seems also to depend of the underlying driver we are using (less
for MOTU 828, more for Built-in). This behaviour was never seen on
PPC machine (G5 for example).
Is this a normal behaviour? Is there a simple way to be sure the
driver is really running when we get out of our "Start" function?
or do we need to implement a synchonization procedure ourself?
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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