AURenderCallbacks occasionally stop occurring after system resumes from sleep.
AURenderCallbacks occasionally stop occurring after system resumes from sleep.
- Subject: AURenderCallbacks occasionally stop occurring after system resumes from sleep.
- From: Dale Curtis <email@hidden>
- Date: Fri, 20 Sep 2013 16:34:52 -0700
Hi,
Chrome users are occasionally hitting a problem where AURenderCallbacks stop after a system resumes from sleep. We've seen this with both default and AUHAL subtype output units over a variety of OSX versions and hardware types -- even plain up-to-date retina MBPs using nothing but the built-in speakers.
We're trying to figure out if we're doing something wrong or if this is a bug. Has anyone else encountered this issue before?
We're only monitoring kAudioHardwarePropertyDefaultOutputDevice for changes, are there other properties we should be listening to which might indicate when a stream restart is necessary?
Perhaps we should be listening for some device level properties like kAudioDevicePropertyDeviceIsAlive or kAudioDevicePropertyDeviceHasChanged?
The code is here if anyone would like to take a look:
Thanks in advance for any assistance.
- dale
_______________________________________________
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