macOS audio dropouts (multiple kAudioDeviceProcessorOverload's)
macOS audio dropouts (multiple kAudioDeviceProcessorOverload's)
- Subject: macOS audio dropouts (multiple kAudioDeviceProcessorOverload's)
- From: Ricci Adams <email@hidden>
- Date: Sat, 17 Sep 2016 08:33:40 +0000 (GMT)
Hi all,
I'm dealing with a rare situation where all audio in macOS drops out for a few seconds. It may have started around 10.11.
Sometimes my audio app receives a chain (10+) of kAudioDeviceProcessorOverload notifications during the drop out, other times there is no indication of an issue (except the audio glitching/dropping out on the speakers). The situation is rare: I receive a few monthly reports of it. However, as my app is used during live dance events, it's catastrophic when it happens.
I'm fairly certain the issue is issue isn't in my app (due to other applications being affected). Just to be sure, I audited all library functions called during my audio render callback:
mach_thread_self()
vDSP_maxvi()
vDSP_minvi()
vDSP_vsmul()
OSAtomicIncrement32() // Used when a kAudioDeviceProcessorOverload since we can't call dispatch_async()
AudioUnitRender()
The only thing I can think of is that AudioUnitRender() is trying to take out a lock?
Assuming the issue isn't in my app, is there a way to enable logging at the coreaudiod or kernel level? I'd like to file a bug report about this, but I have no data. When it happened on my test machine, there was nothing relevant in Console.
Thanks!
- Ricci
_______________________________________________
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