I have not seen a shred of evidence to support this notion in the
HAL's timing.
There have been bugs in the Power Management portions of the OS over
the years. And to be sure, there certainly could still be bugs lurking
today. But, the likelihood of a Power Management bug causing a glitch
of the sort that Mr. Ashworth is describing is pretty remote. It is so
remote that Power Management falls pretty close to last on my list of
suspects when I'm diagnosing glitches. I'd pursue it only after
exhausting other leads.
On Mar 30, 2007, at 1:41 PM, Dominic Feira wrote:
One thing to keep in mind with the G4s, is that their clock speed
isn't skewed like a G5. It is always 1.25GHz. As I understand it
the adjustment of clock speed on the G5 (which you can't disable)
can take a relatively long time to occur. Real-time apps sometimes
run "better" on G4s because of this. I'm sure the core audio guys
can fill you in on this as they have to deal with it for their
predictive audio callback scheduler.
This might not be part of your problem at all. I just thought I'd
mention 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:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
