Re: interpreting HALLab IO Cycle telemetry
Re: interpreting HALLab IO Cycle telemetry
- Subject: Re: interpreting HALLab IO Cycle telemetry
- From: Jeff Moore <email@hidden>
- Date: Tue, 2 May 2006 17:55:46 -0700
That would be a bad time stamp coming from the driver. The bad time
stamp is causing the HAL to resynch.
I would get a screenshot of the telemetry and pull together as much
supporting info as you can and file a bug with the folks that wrote
the driver.
On May 2, 2006, at 2:54 PM, david tay wrote:
While tracking the playback from an application such as Amadeus II
to my usb audio device, on occasion I get an entry such as
0 Early: 113 2414.361 (+0.02) Zero: ( 114688, 2291.211, 0.000000)
and an audible pop.
How would one go about interpreting such entries?
It doesn't appear that there is an overload situation.
--
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