|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Jun 30, 2009, at 2:29 PM, Daniel Mack wrote:
we're developing USB based audio hardware and driver stacks for it since
a couple of years, and haven't had any serious trouble for a long time.
However, we've recently got many reports from users of newer MacBook(Pro)s describing strange effects with audio processing after some hours of runtime.
The first suspect was the driver, but the effects are too weird to
be explained by a simple software bug, especially because not even
unplugging and reconnecting the device (which involves destroying and
re-creating the AudioEngines from the kernel side) makes any difference.
Sometimes, not even restarting the whole machine solves it, they say.
And the installations are all brought up to 10.5.7, which unfortunatly
doesn't help either.
Sadly, I don't have access to any machine showing the effect. But given that there are quite some sanity checks on the hardware protocol level and considering that the driver works pretty well on a varity of different Mac hardware models (we've run test for severeal weeks in a row), I more and more tend to blame some other layer for these issues, possibly CoreAudio.
Sorry for not providing more information and more details, but that vague reports is all I currently got.
Has anyone seen similar things recently?
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
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.