Hi,

As I promised(with some delay) here I will write the new guide.
It will take some time so be patient until is done.

Intro
There is already a better solution for sound here: VoodooHDA
This guide is for those who want to use AppleHDA and/or try to learn how it works.

Credits: To be filled.

Chapter I: Collecting codec info/dumps/etc.

There are several way to get codec info, my advice use them all.

From Linux:
Boot any live linux distro(try to use latest avail, and also if possible use latest ALSA drivers)
Once you are in GUI start terminal and run this command:
cat /proc/asound/card0/codec#1 > ~/Desktop/codec_dump.txt
or
Use this script from zhell



Save it in a safe place, mail it etc.

On OS X we must use the dump to get a graphical interface, convert it to decimal(I will explain later why), get the codec verbs from it and fix them for OS X.

a. Creating Codec Graph:
- Download and install GRAPHVIZ for Mac OS X
- Download CodecGraph, unpack it to descktop, copy on it the linux codec_dump.txt then start terminal and type:

-Now you should have in the codecgraph folder a file codec_dump.txt.svg
If u like to see it open it with Safari or Firefox

b. Converting CodecGraph and CodecDump from hex to decimal:
- Download convert_hex_to_dec.rb.zip Thanks to Munky who made it.
- Unpack it in the same folder used earlier(codecgraph)
- Type in terminal:


From Vista/Windows7:
Open RegistryEditor and search for PinConfig
Dump all keys if there are more, in particular should be one bigger that contain all PinConfigOverRides(aka codec verbs)
Open the dumped key with a text editor, it should look like this:

Copy all and then go to DiaboliK's Vista HDA Verb Converter paste data in window and convert them, copy the result and save it in a text document for later usage.
After convert they should look like this:


Using VoodooHDA dump tool:

Save the dump for later usage.

After all this you should have:
- codec_dump.txt in hex
- codec_dump_dec.txt in decimal
- codec_dump.txt.svg in hex
- codec_dump_dec.txt.svg in decimal
- Vista converted PinConfigOverRides
- VoodooHDA codec dump
Save them all in a safe place.


Chapter II: Enabling audio

By default OS X can't see your audio device b/c on PC's is under different name on DSDT: AZAL or some other name instead HDEF, or is not present at all.
Since I don't like so called "efi strings"(device-properties injection) i will show only two way:
- Simple way is to use an Enabler like HDAEnabler.kext

- Complicate way(my preferred) is to fix and/or add it on DSDT:
On most cases audio device is on DSDT on _ADR 0x001B0000, find Name (_ADR, 0x001B0000) and replace the Device name from AZAL(or whatever name has) to HDEF, if the device is not present it must be added.
Then comes the injection required for audio:
This is an general audio injection and should work for all codecs:

It will be a nice addition to DSDT patcher made by fassl
Also make sure DTGP Method is present in your DSDT, if not add it after/before first Method you find in DSDT.
It should look like this:


Chapter III: Fixing AppleHDA.kext

There are two way to do it, editing original plists or patching it "on the fly" using a dummy.kext.
I will explain the second method b/c it apply on first one too.
So what we have to fix on this kext?
If you look on it(right click show package contents) you will find under Content folder the main Info.plist(don't touch it) and a Plugins folder. There are the plugins that we have to fix, but not all just the Info.plist from this one:

a. AppleHDAController.kext
B. AppleHDAHardwareConfigDriver.kext (present only on Snow/10.5.7+)
c. AppleHDAPlatformDriver.kext

I will treat each one separate, and on the end I will show you how to join them in one single dummy.kext

Chapter III-a: Fixing AppleHDAController.kext Info.plist

Lets take a look on AppleHDAController Info.plist(make a copy from original kext on your work directory)

Under IOKitPersonalities/BuiltInHDA/HDAConfigDefault is our area of interest.
You will notice a lot of Item's, you will need just one for your codec so make some room and delete the rest.
As you can see in the picture this is what we have to do/fix:
- CodecID from decimal codec_dump_dec.txt copy/paste Vendor Id value.
- ConfigData here we will add fixed codec verbs, see dedicated section on how to make/fix them.
- FuncGroup must be 1
- LayoutID must be 12 a short notice on this one do not change it to other value unless you are change it also in HDAEnabler.kext or DSDT injection, by default is set to 12 in HDAEnabler.kext or my generic DSDT injection, best way to leave it like that and do "cosmetic" stuff after you get the sound working...

ConfigData/CodecVerbs how to:
You can fix them in two way, manual or automatic thanks to Signal64 who put all our findings in one script for easy use called VerbIt
Unpack it in the same codecgraph folder you used earlier then start terminal and type:



After is done it will output two files verbs.txt and verbitdebug.txt

Verbs.txt:


Verbitdebug.txt:

The codec I used in example, gigafail ALC889A(rebranded ALC885) was a easy one to fix, it just needs some minor adjustments(like setting one of the mics as internal and so on) and is ready to go, so to completely understand how it goes you need to go deeper, next is manual patching/explanation.

So what is a codec verb?
For each input/output there is a sequence of 4 verbs.
Lets take an example from codec used before:


Its about NodeID(NID) 0x14 in hex, 20 in decimal:

The default verbs for it: 21471c10 21471d44 21471e01 21471f01
21471c10:
2471c10 = CAd (Codec Adress)
21471c10 = NID (NodeID)
21471c10 = Verb Commands like 71"c" then "d", "e" ,"f"
21471c10 = Verb Data
And the same for the rest.

I think Cad, NID and Verb Commands are pretty simple to figure out: first 2 you get them from linux dump, and commands are standard 71c, 71d, 71e, 71f.
Lets see about verb data:

- 71cXY X=Default Association Y=Sequence

Default Association and Sequence are used together by software to group Pin Complexes (and therefore jacks) together into functional blocks to support multichannel operation. Software may assume that all jacks with the same association number are intended to be grouped together, for instance to provide six channel analog output. The Default Association can also be used by software to prioritize resource allocation in constrained situations. Lower Default Association values would be higher in priority for resources such as processing nodes or Input and Output Converters. Note that this is the default association only, and software can override this value if required, in particular if the user provides additional information about the particular system configuration. A value of 0000b is reserved and should not be used. Software may interpret this value to indicate that the Pin Configuration data has not been properly initialized. A value of 1111b is a special value indicating that the Association has the lowest priority. Multiple different Pin Complexes may share this value, and each is intended to be exposed as independent devices.

Sequence indicates the order of the jacks in the association group. The lowest numbered jack in the association group should be assigned the lowest numbered channels in the stream, etc. The numbers need not be sequential within the group, only the order matters. Sequence numbers within a set of Default Associations must be unique.

*My notes for this, if you look on the vanilla codec verb(no matter what codec) you will see that Sequence is always 0.
Why that, and why for us on our codec verbs is different? Simple b/c Apple dosen't have multichannel analog out! so you must change it to 0.

*About Default Association, Keep the default one, in order, and on those that are the same replace them with new one that dosen't exist already in the dump... the values you can use are: 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d and f.(see what does verbit if you still don't understand)

- 71dXY X=Color Y=Misc

Color indicates the color of the physical jack for use by software.


Misc is a bit field used to indicate other information about the jack. Currently, only bit 0 is defined. If bit 0 is set, it indicates that the jack has no presence detect capability, so even if a Pin Complex indicates that the codec hardware supports the presence detect functionality on the jack, the external circuitry is not capable of supporting the functionality.
Reserved 3
Reserved 2
Reserved 1
Jack Detect Override 0

*Use 0 for Jack Detect - External Device(e.g. Headphones Mic etc)
Use 1 for Jack Detect Disabled - Internal Device(e.g. Internal speakers, Internal mic)

71eXY X=Default Device Y=Connection Type

Default Device] indicates the intended use of the jack or device. This can indicate either the label on the jack or the device that is hardwired to the port, as with integrated speakers and the like.


Connection Type indicates the type of physical connection, such as a 1/8-inch stereo jack or an optical digital connector, etc. Software can use this information to provide helpful user interface descriptions to the user or to modify reported codec capabilities based on the capabilities of the physical transport external to the codec.


71fXY X=Port Connectivity Y=Location

Port Connectivity indicates the external connectivity of the Pin Complex. Software can use this value to know what Pin Complexes are connected to jacks, internal devices, or not connected at all.
00b - The Port Complex is connected to a jack (1/8", ATAPI, etc.).
01b - No physical connection for Port.
10b - A fixed function device (integrated speaker, integrated mic, etc.) is attached.
11b - Both a jack and an internal device are attached. The Information provided in all other fields refers to the integrated device. The PD pin will reflect the status of the jack; the user will need to be queried to figure out what it is.

Location indicates the physical location of the jack or device to which the pin complex is connected. This allows software to indicate, for instance, that the device is the “Front Panel Headphone Jack” as opposed to rear panel connections.

*Details:
Convert the 2 digit hex number to binary.
Pad the front with zero's to make it 8 dgits.

Example:


Thanks again to Signal64 for his VerbCheatSheet
*All info came from High Definition Audio Specification Read it for more details!

Conclusions:

The script does a great job, still is not perfect b/c it dosen't know what are your options...maybe a GUI app will add that in the future.
So what can be those options?
- you may want to setup mic as internal to get ambient noise reduction for it.
- some codecs like my AD2000b has only line outs same trick can apply and you can set first output as speaker and get as an option software dsp for it.
- for front panel support you may need to transform back mic in line in as I did for AD2000b.
And so on...

Chapter III-b: Fixing AppleHDAHardwareConfigDriver.kext Info.plist

This is a new plugin for applehda, IMO it will replace hdacontroller(on each new build it takes some of the functions from it)
Patching it is the same as for hdacontroller(just copy/paste HDAConfigDefault from it)

The interesting part(that I'm still investigate) is that PostConstructionInitialization entry, it might be good for some unsupported codecs or to add some extrainitialization stuff, will see...

Chapter III-c: Fixing AppleHDAPlatformDriver.kext Info.plist

This is the hard part to fix, so we need to set some rules to follow:



To be continued...

Awesome, I am very happy to see your guide. I have gotten pretty far on my own but could really use some sage direction. Despite the fact voodooHDA is out and my hardware (MSI wind) is particularly stubborn with audio, from what I gather I am really more interested in learning how it all works while attempting to make improvements (like a working mic). Oh and for the right brained, AI also opens .svg. Its nice to have control and speed to nav the graph.

Thank you: fascinating stuff & really clearly expressed.

KiNG, thank you for the guide. I'm finding it an easy read, and I had no issues following it thus far.

Do you have any idea on when the rest of it will be ready? I have an Intel board with a genuine ALC889 (as opposed to the ALC885/889A) that doesn't work correctly under VoodooHDA, so I need to patch AppleHDA. After messing with the PathMaps, I'm clearly lost. The rest of your guide would be most helpful, if it's going to be done any time soon.

The KiNG
We are waiting for you to continue.
You said nothing about VREF, MuteGPIO, Amp, boost, detectdelegate...

I said it will take some time, is not easy to put things in order and post correct data in a n00b way...
Plus I have my problems/real life to cover, I'm not living in a hack.
If you can do it better/faster be my guest.

[off topic]Could you please upload your codec dump?.[/off topic]

EDIT: thanks

Sure. Click to view attachment

The interesting bit is that it has an Audio Selector at d36, that's not in any documentation.

Unfortunately the board croaked this morning due to other circumstances, so I'm not sure if I'll even be able to get a replacement.

And King, I understand. Thank you for your work thus far.

For what it's worth, the replacement arrived. It's not the same mobo (this time it's an Asus Rampage II Extreme) so I won't be able to tinker with the real ALC889.

However while I'm at it, the codec that comes on the Rampage is the AD2000b, a codec King actually wrote a modified plist for. Audio out works great, but mic-in levels are way too low - I have to basically eat the Mic to get anything among a ton of background noise. If anyone has some insights to offer, I'd appreciate it. Looking at the file, I can't see anything wrong.

You may want to try my new AD2000b.kext
It is designed with front panel support(mic as internal and headphones) 3 line out(first as speaker) digital in/out and back mic(as line in, I will explain later why 3 analog inputs dosen't work with hda)
It should work aslo for AD1988b with CodecID replacment in plist.

Enjoy!

That did the trick. Thank you King, you are my hero.

Awesome, thanks for all your work.

Is there a way to make HDAEnabler ignore my X-Fi Titanium..or is that not how it works?

I put the IDs of my ADI2000B in the plist replacing what was there, but that didn't work, it just broke everything!

Am I correct in assuming that adding the "Device (HDEF)" to the DSDT replaces HDAEnabler?

My understanding is that HDAEnabler injects all HDA audio devices witht he proper tag, so no, I don't believe there's a way to keep it from doing that to your X-Fi Titanium. I'm don't have the foggiest on why that would screw up anything for you though.

As for the DSDT method, I've never been able to get it working myself.

Yes
Just use my example from guide.

@Nemes Is not that hard..., if you want to learn how to do it manual google is your best friend, if you want help you can use DSDTSE.app

Okay, done - it works.

I couldn't find the AD2000B in the DSDT so I inserted the HDEF Device among the other devices, before the SATA.

Why does it do this..twice..during bootup? I'm guessing one could possibly be the X-fi. I should try removing it.

AppleHDAController is where it's supposed to be though, in the plugins folder of AppleHDA.kext (vanilla 10.5.8)

Is it something AD2000B.kext does?

The weird thing is, it does load, look (kextstat -k):


It doesn't make a difference if AD2000B.kext is in EFI/E/E or /S/L/E.

Those AppleHDAController warnings are normal b/c the dummy.kext loads earlier in the boot process and since it cant find AppleHDAController.kext (that is loaded later) it prints that.
The only way to get rid of those is to patch/fix original applehda.kext info.plist's, but that say bye to "on the fly" patching...
After AppleHDAController will be deprecated and removed by apple we will get rid of those "natural"

Hello King, I hope you are abel to clarify this. My sound chip is ALC 883 and codec_dump from Ubuntu says codec address is 2. My config data dump from Vista registry has entry all ended with '01' such as "0000"=hex:10,1c,47,01..... My understanding was '01' byte flip will give you codec address '0'. The sound system is working perfectly in both Ubuntu and Vista. Do you have any idea why? Anyway I should used codec address '2' as detected by Ubuntu?

1. What motherboard for you?
2. Make a Linuxdump & VoodooHDAdump.. (Attach here)
3. Try this Click to view attachment
and
Click to view attachment
or
Click to view attachment

or DSDT patch

P.S. I am sorry for my English

Thanks for the guide. I've been following it for quite some time but haven't been able to post a reply. Didn't realize there's a quiz which I needed to pass in order to post! lol

Anyway, I've found the same weirdness as ihosc above. While trying out a plist by someone else to see if it works better on my alc 888, I accidentally copied ConfigData blindly and didn't notice that the codec address is different than the one I've been using. It turned out, my sound works just as well as before. I've always had the impression that codec address is a fixed value, specific to your hardware. I later looked at the official docs and I think it's a value that is assigned during hardware initialization. I might be wrong on this though.

New User, 1st post: Whoa, didn't know that I've got a quiz to take... Whatever ...

Now, to the point, I have an Intel DG33FB (ALC888) CAd 2. (had sound in Leopard using Taruga's Patcher & efi). It has:
Rear: Line out, Line in, Mic In
Front: HP, Mic In

What I've done so far:

1. Took a codec dump.
2. patched dsdt
3. prepared pin config from verbit script
4. tried to patch HDAEnabler HDAController etc. (failed.... of course)

Would somebody be kind enough to get my audio working. I'm attaching the list of all the files. (I don't need fancy System Profiler o/p at the moment, just 1 line out, 1 mic in that's all).

I hope you can give me a hand. I have been reading this excellent tutorial so far, as well as working on the path maps element for my board (a ZOTAC 9300 with ALC662).

I have got a long way, and have the Snow Leopard AppleHDA.kext working with stereo Line Outs (front and back), digital and Line In functioning and I have the DSDT mod working correctly to inject the audio.

The thing that is frustrating me is that, I cannot get the microphone inputs to work. For the moment I am just trying to get the front mic (node 25) to function.

I would really value some help to point me in the right direction, I am not sure if it is the path map that needs modifying, or the ConfigData.

I have attached plists for the Platform Driver and HardwareConfigurationDriver.

The Microphone path is item 1 in the first path map (nodes 9 34 25) of the platform driver. The config data from the HardwardeConfiguration driver is made up from Verbit corrected verbs from my Linux dump.

I have attached the linux dump and the verbitdebug output along with my plists.

I have tried different config. data generated from Windows 7, my original Linux dump and from a VoodooHDA dump and I am running out of ideas now, so maybe a fresh pair of eyes would help.

Thank you for looking at this.
Click to view attachment

EDIT: PLEASE IGNORE ABOVE, PROBLEM NOW SOLVED AFTER COMPARING TO KEXT FROM tmongkol (THANKS!!).

The AD2000b Kext keeps working fine in 10.6.2, thanks again (I tested Speakers, Microphone input, front panel + auto switching and everything is perfect)!
There was just a small issue: they added "PCIVendorDeviceID" in the AppleHDAController plist, that was not present in the legacy kext and caused a single "sound assertion" error.
I added the default value (fix it if it needs to be) and the error is gone, here's the kext:
Click to view attachment

Sorry for the double post
I found a bug with the AD2000B legacy kext: after sleep, the microphone automatically switches to the front panel one (even if it's not present), and you have to unplug the microphone and plug it again to fix that.
I'm using 10.6.2 with HDEF in DSDT (no HDAEnabler), I'm not sure if this problem existed in 10.6.1.
I tried to fix it but no luck (I guess I'm not good enough )

I have a better fix then that(that fix also HDAController load error since is not used anymore)
New DSDT HDAEnabler:
For Intel ICHx:

For nVidia boards:

A little explication, if you look on lspci -nnvv you will see something like this:
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03)
Subsystem: ASUSTeK Computer Inc. Device [1043:1763]

Then look on Apple MacBookPro:
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03)
Subsystem: Apple Computer Inc. Unknown device [106b:00a0]

Macmini3,1:
00:08.0 Audio device [0403]: nVidia Corporation MCP79 High Definition Audio [10de:0ac0] (rev b1)
Subsystem: nVidia Corporation Device [10de:cb79]

Or no Subsystem at all on MacPro4,1:
00:1b.0 Audio device [0403]: Intel Corporation Device [8086:3a3e]

Enjoy!

P.S. Remove BuiltIn entry from dummy.kext(AD2000b or whatever..)

Thanks.

I swapped LineIn and Mic (in both verbs and MuteGPIO in "PathMapRef") and it worked, the problem is gone (front panel is now LineIn, and it still works). I also noticed that Snow hasn't "HDAConfigDefault" in AppleHDAController anymore, so I deleted the legacy AppleHDAController to get no "not loading kext" warnings in kernel.log.

Thanks for the new DSDT fix

Click to view attachment

hello, here is codec dump from linux using latest alsa driver on opensuse 11.2, also codecverbs from win7 using latest driver from realtek, anyhow, I will post more of the stuff I got for chipset alc272 on acer aspire one d250, mic works fine on both win7 and opensuse but not on osx, well... thanks to the guys behind these scenes, thank you.

Click to view attachment

Click to view attachment

thanks again.

Hello, i've been following these AppleHDA patching posts and replies and i respect the work.
While following I tried very hard to fix my ALC882 on my ASUS Z96Js laptop but got nothing.

Can you guys help me out or guide me in any ways possible.
I have attached my DSDT + CODEC DUMP from linux.

Click to view attachment
Click to view attachment

My current system is as follows.

Snow Leo 10.6.2

ALC882 with
1 - 1/8" headphone/speaker jack in front
1 - 1/8" line-in jack in front
1 - Internal Speakers
1 - Internal Mic


Please help me out guys, i will be very thankful

Notebooks are very specific on sound, most depends on how OEM's chose to use the codec.
Is very hard for me or anyone else to fix it w/o the hardware b/c it require tons of tests, is not that simple....
Sorry but you are on your own with this, use the guide and god luck!...

Hi THe KiNG

I am very grateful to you for sharing this knowledge. Thanks to your tutorial, I managed to make almost perfect LegacyALC882 for ASUS'a P5W DH Deluxe. Click to view attachment
Tested and works:
Green line-out as a Speaker
HP On the front panel - after connecting headphones muted green line-out.
Orange Line-out
Black line-Out
Mic on front panel
Line-in
Digital-out with DD / DTS passthru
You can combine 3xLine-out, one 5.1 Line-out using Audio MIDI Setup

Only left for me to get rid of these errors on startup:


If you know what can cause it, then I would be grateful for tips on how you can get rid of them.

Hi to all, with the ad2000bfix on my p5q deluxe, all working but the SPDIF don't work like the grey exit, nothing sound. It's normal? Also with voodoohda the option is grey and don't work.. I would say, it's normal that the spdif option is grey, just when i will connect the jack spdif will work? And for the grey exit on rear panel, nothing audio from her, is there a solution?

Thans so much..
Sorry for my english

When the guide with the third part will complete?

Sorry for the late reply, but thanks for replying atleast.

Thanks THe KiNG (and Phoenix Wright) great work as always.

And thanks to BasementJack over at the VoodooProjects forum for making me revisit this thread.

New DSDT patch applied, AD2000B.kext installed and working on P5Q-E.

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.
so open AppleHDA binary in a hex editor, and search for 8508ec10 (apple alc885) in my case I needed support for ALC888 so I just replaced all 8508ec10 with 8808ec10, and now works...

Looking for a better sollution on this(don't try DSDT patch, is not working)

hm, hm.. my codec ID is 8086:284b not works with 10.6.2 What the search string for my device? Help

That is not your codec id, read first post again.

I did the same on my desktop since apple still has in binary stuff for AD1984(0x11D41984) I searched for all 8419D411 and replaced with 9B98D411(0x11D4989B AD1989b found under cosmetic name as AD2000b) and surprise, didn't worked!
So things are more bad then I tough...

EDIT:

I was wrong trying to replace AD1984 with mine, instead worked using AD1988b as replacement, that mean those who have AD1988b are lucky...

Hi there KiNG,

can you point me to the right direction for creating a legacy version for my alc889a audio device
The device is id 0x1458A102 layout 12 0x0000000c ; 0x0c, 0x00, 0x00, 0x00 (ga-eg45m-ud2h)
Right now i'm using the patched applehda.kext version 1.40 (see attachment) it's working great but only at x32
I can't find any legacy version for this device.

In my dsdt i have this to enable the hdef


Thnx for any help
T.


edit; uploaded files won't show somehow (applehda1.4.0a22.kext

Yes I can point you: Read first post.
The purpose of the guide is to help you understand how to do it, not how to use Google(to search for dozen legacy kexts that already exist for your codec) or anything else.
If you don't want to learn then use VoodooHDA.

Thnx for the answer, no suitable kext found yet
Your tutorial is my last option.

T.

sorry, stupid mistake. My codec id is Vendor Id: 0x83847627 and Subsystem Id: 0x80863001

Hello

Can you help me here http://www.projectosx.com/forum/index.php?...pic=946&hl= or point me to tutorials that completes missing informations?

Why Am I ignored ?

Nobody is ignoring you, I don't think it is possible to do what you want within OSX, in Windows you have specific drivers to change the inputs to outputs, you don't have that in OSX.

Could be wrong!

Ok thank you for your answer

THe KiNG, did you find a solution to use a legacy kext with 10.6.3 or Apple screwed us over?

Legacy dosent work, only way hack the binary...or use a board with supported codec(apple list)
That's it

Hey THe KiNG,
Is there any way you could upload your binhacked AppleHDA.kext for P6T?
-thanks

Or can anybody help me binhack it? Do I need something like 0xED to binhack?

Sorry, if I'm suggesting nonsense, but have you tried this solution: http://www.infinitemac.com/f7/applehda-by-...l-10-6-3-t5405/ ?
The guy there suggests DSDT patch to inject codec-id, I don't think it would work, but might be worth a shot.

You can get it same way as you got the fix, on irc...


I said already: No.