Re: MacBook pro : bug in the internal audio driver ?
Re: MacBook pro : bug in the internal audio driver ?
- Subject: Re: MacBook pro : bug in the internal audio driver ?
- From: Jeff Moore <email@hidden>
- Date: Wed, 29 Sep 2010 11:13:41 -0700
On Sep 29, 2010, at 7:29 AM, Stéphane Letz wrote: Le 29 sept. 2010 à 16:24, Doug Wyatt a écrit :
On Sep 29, 2010, at 0:18 , Stéphane Letz wrote:
Hi,
I see strange behaviour of the internal audio driver on a MacBook pro OSX 10.6.4. We have audio test applications that probably produce "non-correc"t samples that cause the driver to mis-behave. Applications cannot play anymore, the machine issues "pop" when starting/stopping an audio application and the only way to get normal behaviour is to restart the machine.
Is this a known problem? Could it be an issue with speaker protection code that is part of the driver on MacPro?
Hi,
The symptoms are what I'd expect if some of the samples being output are NaN's. Sometimes they can stay around indefinitely once introduced into a signal chain.
Arguably the driver ought to be resilient to them, but maybe there is a simpler solution in your test applications?
Doug
Possibly... but having to restart the machine is not the best option. So are you CoreAudio guys going to fix that?
Probably not without a bug about it. Be sure to include your test program that produces the signal with bad numbers in it.
--
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