Jump to content
3 posts in this topic

Recommended Posts

The USB Audio Adapter stutters

 

WARNING: AppleUSBAudio has detected that clock_get_uptime () value changed radically from previous values

WARNING: AppleUSBAudio has detected that clock_get_uptime () value changed radically from previous values

WARNING: AppleUSBAudio has detected that clock_get_uptime () value changed radically from previous values

WARNING: AppleUSBAudio has detected that clock_get_uptime () value changed radically from previous values

 

bla-bla-bla-bla

 

USBF: 1.177 AppleUSBHub[0x3564400]::RearmInterruptRead - unexpected power state (3)

USBF: 1.181 AppleUSBHub[0x3564a00]::RearmInterruptRead - unexpected power state (3)

USBF: 1.236 AppleUSBHub[0x3564800]::RearmInterruptRead - unexpected power state (3)

 

How to fix it?

 

I tried it with AppleUSBAudio.kext from 10.4.10, but it stutters too, so its a USB problem

Link to comment
https://www.insanelymac.com/forum/topic/57184-usb-audio-problem/
Share on other sites

  • 1 year later...

I don't know. This can happen in 10.5 as well. It causes audio stuttering, pausing, etc.

 

Try restarting. Also try reseating the USB plugs in the ports. Try a different USB cable if you use an extension. Try another USB port.

 

This could be related to power saving features that slow the CPU clock, which the USB audio is relying on for timing. I did not disable this feature, and my audio is working again after the steps above.

 

Apparently there are nanosecond APIs available, but not in use for these drivers. OS X is getting better with integrated audio cards, so try your motherboard's audio chipset again if the USB can't be helped.

I apologize, I had thought I had fixed the issue on my machine. It returned.

 

In searching for instances of the kernel function clock_get_uptime, I found some people talking about it while overclocking their Macintosh G5's. I remembered I had overclocked. Looking at my BIOS settings, I see that I enabled the motherboard's automatic overclocking feature, not wanting to damage anything and let it do modest speed increases. The description for my Asus feature is "When N.O.S. is enabled FSB frequency will be optimized automaticall (SIC) depending on CPU loading". Clearly this would change timing dynamically, and "radically".

 

I've set up a moderate overclock, but set manually. I'm not seeing the error. If it returns, I'll try disabling all overclocking.

 

I don't mean to be annoying with the double post, but this kind of information is very useful when searching for information on errors like this.

×
×
  • Create New...