Mac Pro Audio Update

[richardsim7]

Does anybody know if it's safe to install this update?

 

Specs in my sig

[MusicByJam]

Does anybody know if it's safe to install this update?

 

Specs in my sig

 

Hi I have a similar setup, I installed and all was fine apart from my onboard sound which stooped working, I found out that the appleHDA.kext is updated to a newer version, v1.8 and this breaks my sound. Had to put back the old v1.7 kext to get my sound working again.

[trwoolley]

Interesting read from 2/12/10 Friday xlr8yourmac:

 

http://www.xlr8yourmac.com/

 

What the 2009 Mac Pro Audio Update Really Changed

- From the author of OS X Hardware/Temperature Monitor:

"Hello Mike, when reading your web page, I noticed your question about the AudioAUUC kernel extension which should allegedly be part of the "Mac Pro Audio Update".

(In my notes in yesterday's post on the "Mac Pro Audio Update", I had mentioned I didn't see that extension listed in OS X 10.6.2 Apple System Profiler (ASP) extension list before installing the Audio Update, although the same version was already present in 10.6.2. And after the update it was listed in ASP's extensions (i.e. actually being loaded) but was the same version (1.0)/same last modified date, etc. - which made me wonder if that extension just wasn't being loaded/used before the 'audio update'.-Mike)

 

You are right: The AudioAUUC extension has nothing to do with this update. It was in fact part of the Mac OS X 10.6.2 package. Apple has published wrong instructions here.

 

(At the bottom of Apple's "About the Mac Pro Audio Update" doc, it says after the update is applied (w/required system restart) to verify that ASP's extensions list shows the AudioAUUC v1.0 extension. That seems to imply it was a new/updated extension - but it may just mean it's actually now being loaded/used after the update. (From what I saw, the latter is true.) And like many Apple updates, there's little details on what really was changed.-Mike)

 

It is undocumented what AUUC stands for, but my educated guess is that this is the "Audio Unit Upstream Client" which seems to play a role when sending audio data to HDCP-protected devices.

 

What the Mac Pro Audio Update actually does is to upgrade

- the IOPlatformPluginFamily extension from version 4.0.1d0 to 4.0.2d0 and

- the AppleHDA extension from 1.7.9a4 to 1.8.3fc1.

 

The first extension contains a collection of drivers which control the different energy-saver states of Intel processors. The second extension contains a collection of drivers for audio chips complying with the Intel High Definition Audio standard.

 

After the update, playing audio over the integrated audio chips will no longer create the unexpected change in processor performance. The temperature behavior of the CPUs (which has never been a problem) does not change, you only need different programs (not audio) to trigger a rise of temperature values now.

Best regards, Marcel Bresink

http://www.bresink.de/"

 

Regardless of what they did, I'm just happy that simply playing audio in OS X with my 09 Mac Pro no longer ramps up temps and system wattage ( 110W+ from that alone) as it did before.

(And as I said yesterday, hopefully they're release a similar patch for OS X 10.5.8. I need update my original article w/tests on this from last Nov. to include a FYI about the Audio Update for 10.6.2.)

[KariNeko]

On projectosx THe KiNG posted this:

So Apple started to play ugly again...

With new 10.6.3, AppleHDA dosen't work anymore...

What happened?

Apple hardcoded supported codec id's from mac's, if your codec is not in the list then BUM!

A temporary fix is to use old fashion way: binhack that HDA binary.

Read the complete post here.