AppleHDA HDMI Audio [Guide]

[ftulio]

See Post #1/IV. Problem Reporting; attach all requested files

Do you believe that the fact that I have two displayports outputs connected (one directly to the DisplayPort input and another using an adapter DisplayPort to HDMI) could gerente the error in the script?

Or the fact that I have installed the whatevergreen and Lilu to the "Clover\kexts\other" directory?

If not, I will send all files to the report error during the weekend.

 

[toleda]

Both Clover Configurator and checking manually in the config.plist file itself via XCode show both of those options are in fact there and enabled

My mistake, both must be NO; Clover HDMI audio does not work.

guessing that it's either that the Pascal GPUs all have an HDMI device ID that is outside what worked before

The Fermi edit supported 4 Nvidia display instances while Kepler/Maxwell/Pascal support 6.

Would still love to know why the 780 shows up as @PEG0 while the 1080 Ti shows up as @P0P2

Likely, Clover setting.

I guess this is the peril of running Pascal GPUs under OS X when you have Apple doing everything they can to make doing so a PITA.

Nvidia problem, made an architectural decision not to compete with AMD Eyefinity (6 displays) years ago. Interestingly, Nvidia's software strategy enables "unsupported" Maxwell/Pascal products to be macOS supported.

 

[toleda]

Do you believe that the fact that I have two displayports outputs connected (one directly to the DisplayPort input and another using an adapter DisplayPort to HDMI) could gerente the error in the script?

No

Or the fact that I have installed the whatevergreen and Lilu to the "Clover\kexts\other" directory?

No

2nd request, attach the requested files.

 

[SquishyTia]

My mistake, both must be NO; Clover HDMI audio does not work.

The Fermi edit supported 4 Nvidia display instances while Kepler/Maxwell/Pascal support 6.

Likely, Clover setting.

Nvidia problem, made an architectural decision not to compete with AMD Eyefinity (6 displays) years ago. Interestingly, Nvidia's software strategy enables "unsupported" Maxwell/Pascal products to be macOS supported.

Thank you again. I'll try disabling those settings and rebooting. Not like I can't just re-enable them if necessary.

Quick question: Will disabling FixHDA also disable onboard audio? It'd be nice to be able to retain both onboard and HDMI audio like I was able to previously. If not, not a deal breaker now that I have a working home theater setup again with its own headphone jack (and better DACs on all channels to boot).

Also, regarding the "Fermi" DSDT edit - it should still function properly even on Pascal as long as I only have a single display connected, yes? Or is it a hard "if the GPU has more than four total ports, it MUST have the ≥Kepler edit instead? If the latter is the case, what would be the best method of switching the Fermi edit out for the ≥Kepler edit since building clean DSDT is much more difficult now with PJALM's Gigabyte repo gone.

 

[SquishyTia]

This post is an addendum to the previous post.

Nope, unchecking those two settings (FixHDA, AddHDMI) did not work. However, with both enabled, the DisplayPorts closest to the motherboard work for audio, and if I boot with the TV connected to the DP connector (either of the two on the GPU closest to the motherboard) and then move the connection to the HDMI port, I get native HDMI.

Here's how my GPU is configured:

Motherboard - DP1 -> DP2 -> HDMI -> DP3
DVI

DP1 and DP2 provide alt-mode HDMI audio on bootup. HDMI provides HDMI audio if I connect to DP1 or DP2 on bootup and then move the connection to HDMI. DP3 does not output any audio at all and no audio device shows up in Audio MIDI Setup regardless of whether or not DP1 or DP2 is used as the initial connection on bootup.

This seems to mirror what I've seen reported here regarding how HDMI audio is working in 10.13.4 and later with Maxwell/Pascal GPUs, and it's happening in 10.12.6 w/ the latest security update, so it looks like it isn't only 10.13.4+ that's affected by the HDMI audio problem.

I can live with having to use the DP connection for now, though if I move to a 4k TV I know I'll need to get an active DP to HDMI adapter if I want 4k60 @ 4:4:4 (ARGB2101010 30-bit color if I'm lucky enough to get a 10-bit panel on the TV like I have now).

 

[toleda]

It'd be nice to be able to retain both onboard and HDMI audio like I was able to previously

All AppleHDA Realtek Audio and AppleHDA HDMI Audio methods work together. Some other method conflict.

what would be the best method of switching the Fermi edit out for the ≥Kepler edit

Edit Device (GFX0) as shown
1. edit Package to 0x0e
2. copy one of the connector-type code, paste 2 time and edit as @4 and @5

 

[toleda]

unchecking those two settings (FixHDA, AddHDMI) did not work

See Post #1/IV. Problem Reporting; attach all requested files

This seems to mirror what I've seen reported here regarding how HDMI audio is working in 10.13.4 and later with Maxwell/Pascal GPUs, and it's happening in 10.12.6 w/ the latest security update, so it looks like it isn't only 10.13.4+ that's affected by the HDMI audio problem.

Two Nvidia HDMI audio issues
a. 10.13.4 and newer dropped native Nvidia HDMI audio codec support, AppleHDAController patch required; see Post #2
b. HDMI port on all Pascal graphics cards does not support HDMI audio, Nvidia web driver bug; workaround is DP2HDMI adapter (If DP audio is working, active adapter for 4K)

 

[SquishyTia]

Hrm. This looks interesting:

5.0.0.0

• Released Clover Configurator Global Edition
• Added RenameDevices key in Acpi section - New Acpi patching feature (Clover Rev 4468+)

Could this be used to rename the graphics card from within clover to what you said to do in the DSDT manual edit?

 

[toleda]

Could this be used to rename the graphics card from within clover to what you said to do in the DSDT manual edit?

Only changes name, cosmetic. Does not inject required HDMI audio properties. DSDT edit or ssdt does both.

 

[SquishyTia]

Only changes name, cosmetic. Does not inject required HDMI audio properties. DSDT edit or ssdt does both.

Roger that. I have a dump of my current DSDT edited and will try it out later. Good thing this was a simple edit because the DSDT was customized with one of PJALM's USB device rename edits and his repo is gone, so I really didn't want to have to muck around with that as it's the only solution that gives me proper amperage current on my USB 3 ports.