10.4.10 Snap, Crackle, Pop - a workaround

I just installed this patched after seeing this post a few minutes ago since I was also suffering from the popping issue. So far, it sounds pretty good as the problem is not occuring anymore. Thanks for the URL.

Actually, we need no more reports at all as Apple has provided the patch/update that a majority of us have been stating was needed since a few hours after 10.4.10 - Software Update now offers up an Audio Update for all Intel-based Macs to fix an issue with the "popping" sounds produced by those systems in connection with certain types of speakers. It includes a single file only: AppleHDA.kext v1.3.3.

As a side note, it's not puzzling at all if some Macs may have included v1.3.2 before it was made available in 10.4.10. New systems are frequently shipped with a slightly modified/updated build of OS X to take advantage of new revisions of hardware.

Updated and audio issue resolved; thanks Apple!

Yes they have and it works! Weeeeeeeee!!!!

Thanks guys!

Mac MIni Mac OS X (10.4.5)

So - curious - now that Apple's posted an update (very quick of them - nice!) - what other end-user problems did "we" have that was "our fault"? Please. Enlighten us RC-R!

I can't wait for the spin. Should make industrial centerfuges look like teacup rides.

I never said all the possible problems were the fault of the user -- that is someone else's spin I will take no responsibility for.

What I did say is that some of the problems could be repaired by users without application of an update or work-around. Lost in the euphoria over this release is the fact that there are still users having problems they attribute to the update. The same logic is applied: after update; therefore, because of update. This "revised" update only convinces them that much more that there is nothing wrong with that logic & they should do nothing except wait.

That is a pity. The logic is flawed, even if it sometimes produces the right answer. By applying it, some users are going to suffer. Hardware problems will be ignored while warranties run out. File system corruption will eat files that can't be replaced. Simple things that could not only set things right but prevent other problems from occurring will not be tried ... after all, why bother if the update causes all their problems?

This isn't spin. It happens with every update. Some percentage of users will continue to argue that the update is the only possible cause even after it becomes totally obvious that something else is at fault. (Bad RAM? The update caused it! Hard drive fails two weeks later? The update did it!) It sounds silly, but it is the same logic. If you support it for one problem, it is hypocritical not to support it for all.