On Mon, Jul 06, 2009 at 03:25:51PM -0700, Jeff Moore wrote:
> Without a better description of the problem, particularly what the
> distortion sounds like, how often it happens, precisely when it started,
> etc. There really isn't much we can do to help you out.
Well, I know. Guess what I tell users to come up with ;) Unfortunately,
this vague reports (but many of them) is all we currently have. I've
only ever got to hear one piece of recorded audio material as evidence
for it all - hope to be able to provide that by tomorrow.
I'm totally aware that such an error description doesn't help much, I
just wanted to share our state of awareness, hoping someone with similar
problems chimes so we could look for commonalities.
> FWIW, the usual cause of problems like this is that somebody somewhere
> has rolled over a 32 bit number. Basically, somebody is using a 32 bit
> number where they should be using a 64 bit number.
The recorded audio material shows audio artefacts every 128 samples.
While this is in general something the driver could be made resposible
for, there is still the fact that the issue persists after unplugging
and replugging the device. As the device is bus-powered, everything is
reset electrically, and the IOAudioEngine is deregistered. My verdict is
that if that doesn't help anything, the bug is supposed to be in some
other software layer. And again - this is something that only newer
machines with 4GB of RAM show. After many hours of usage.
Anyway, I'll provide more input on this as soon as I can.
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