Comments on: Did Steve break my audio? http://www.tipsfromthetopfloor.com/2007/06/21/did-steve-break-my-audio/ Sun, 07 Sep 2008 13:17:42 +0000 http://wordpress.org/?v=2.3.3 By: haleOnEarth http://www.tipsfromthetopfloor.com/2007/06/21/did-steve-break-my-audio/#comment-35291 haleOnEarth Thu, 28 Jun 2007 00:31:54 +0000 http://www.tipsfromthetopfloor.com/2007/06/21/did-steve-break-my-audio/#comment-35291 If you're experiencing audio problems after updating to OS X 10.4.10 you're not alone. The complaints are growing quickly and here are some of the culprits mentioned: "Confirmed that replacing /System/Library/Extensions/AppleHDA.kext with the version from 10.4.9 kills snap/crackle/pop. If you have a backup of it from 10.4.9, just copy it over, repair permissions and restart. This fixes popping issue due to overagressive power management in 10.4.10. It also fixes the increased volume level." http://gizmodo.com/gadgets/downdate/os-10410-snap-crackle-pop-271672.php "One of the changes in 10.4.10 is a revamped FWAudio.kext, with higher thread priority. Unfortunately, this is causing issues with some FireWire based audio interface units, particularly those relying on Apple's own CoreAudio. There is a small but growing number of reports of audio I/O devices such as the M-Audio Fire, failing to be recognised by the OS, even after maintenance." http://forums.mactalk.com.au/showthread.php?t=32838&page=2 Updates have their hitches, but with the Mac as a creative audio/visual hub coupled with the intended kernel extension improvements, this is an odd one for Apple engineers. If you’re experiencing audio problems after updating to OS X 10.4.10 you’re not alone. The complaints are growing quickly and here are some of the culprits mentioned:

“Confirmed that replacing /System/Library/Extensions/AppleHDA.kext with the version from 10.4.9 kills snap/crackle/pop. If you have a backup of it from 10.4.9, just copy it over, repair permissions and restart. This fixes popping issue due to overagressive power management in 10.4.10. It also fixes the increased volume level.”
http://gizmodo.com/gadgets/downdate/os-10410-snap-crackle-pop-271672.php

“One of the changes in 10.4.10 is a revamped FWAudio.kext, with higher thread priority. Unfortunately, this is causing issues with some FireWire based audio interface units, particularly those relying on Apple’s own CoreAudio. There is a small but growing number of reports of audio I/O devices such as the M-Audio Fire, failing to be recognised by the OS, even after maintenance.”
http://forums.mactalk.com.au/showthread.php?t=32838&page=2

Updates have their hitches, but with the Mac as a creative audio/visual hub coupled with the intended kernel extension improvements, this is an odd one for Apple engineers.

]]> By: Steve http://www.tipsfromthetopfloor.com/2007/06/21/did-steve-break-my-audio/#comment-35155 Steve Mon, 25 Jun 2007 20:38:54 +0000 http://www.tipsfromthetopfloor.com/2007/06/21/did-steve-break-my-audio/#comment-35155 I also had the exact same problem: I updated my MacBook Pro to OS X 10.4.10, and it stopped recognizing my Alesis io|2 as an input device. I filed bug reports with Apple and Alesis, and got a reply from Alesis. I restored from a backup I took prior to updating to 10.4.10, and am able to use the io|2. Hopefully they (either Apple or Alesis) will have a fix soon... I also had the exact same problem: I updated my MacBook Pro to OS X 10.4.10, and it stopped recognizing my Alesis io|2 as an input device. I filed bug reports with Apple and Alesis, and got a reply from Alesis. I restored from a backup I took prior to updating to 10.4.10, and am able to use the io|2. Hopefully they (either Apple or Alesis) will have a fix soon…

]]> By: Nik http://www.tipsfromthetopfloor.com/2007/06/21/did-steve-break-my-audio/#comment-34897 Nik Thu, 21 Jun 2007 19:49:47 +0000 http://www.tipsfromthetopfloor.com/2007/06/21/did-steve-break-my-audio/#comment-34897 Not noticed anything wrong myself with my M-Audio and Zoom, but 10.4.9 wasn't a nicely behaving update. I thought Apple had got it out of their system by now. ;-) Not noticed anything wrong myself with my M-Audio and Zoom, but 10.4.9 wasn’t a nicely behaving update. I thought Apple had got it out of their system by now. ;-)

]]>