Re: Recommended way to setup a timer in a CoreAudion application?
Re: Recommended way to setup a timer in a CoreAudion application?
- Subject: Re: Recommended way to setup a timer in a CoreAudion application?
- From: Stéphane Letz <email@hidden>
- Date: Wed, 16 Jan 2008 10:49:24 +0100
Le 16 janv. 08 à 10:44, Brian Willoughby a écrit :
My first reaction is that you should not need to set up a timer to
poll for an audio failure condition. It seems like you could
register a callback for a notification when the audio driver stops
running. If you're writing a custom driver, then perhaps you should
send such a notification.
Brian Willoughby
Sound Consulting
On Jan 16, 2008, at 01:33, Stéphane Letz wrote:
In my CoreAudio based application, I need to setup a timer to check
that a failure condition has been triggered (like the underlying
driver is not more running). I tried to play with
CFRunLoopTimerCreate, CFRunLoopAddTimer API without much success up
to now. Is there a recommended way to do that?
The thing is that my code is listening to
kAudioDevicePropertyDeviceIsRunning so that do detect the observed
device is not running anymore. But in lot of cases I see a sequence of
kAudioDevicePropertyDeviceIsRunning OFF followed by
kAudioDevicePropertyDeviceIsRunning ON just a few millisec after (for
example when a sample rate change is done on the device that is
observed).
The result that listening to kAudioDevicePropertyDeviceIsRunning OFF
is not enough: I would need to be sure this condition stay for a
certain amount of time, thus the timer idea. But maybe there is a
better way to do that.
Thanks
Stehane Letz _______________________________________________
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