Jump to content

VoodooHDA 3.1.2

Slice

By Slice,
in VoodooHDA

 Share
1042 posts in this topic

Recommended Posts

deeveedee
deeveedee
Posted
Posted

There has been a lot discussed here and I have tested all of the recently recommended steps/commands.  Here's the very simple VoodooHDA.kext installation that works for me at this time:

  • Use VoodooHDA.kext 3.0.2 from here - I am not building my own VoodooHDA.kext nor have I found the need to re-sign the kext.  I'm using the pre-built VoodooHDA.kext as provided.
  • Set SIP and copy VoodooHDA.kext to /Library/Extensions as stated here.  Relaxing SIP restrictions more than setting csr-active-config = <03080000> will work but is not necessary
  • If tighter SIP restrictions are desired after installing VoodooHDA.kext, follow this

I am currently using VoodooHDA.kext with csr-active-config = <01000000>.  Only "Allow Untrusted Kexts" bit is set.  No other SIP restrictions need to be disabled after VoodooHDA.kext is installed.  

 

In summary, I am using the pre-built VoodooHDA.kext as provided, I am copying VoodooHDA.kext to /Library/Extensions using "cp -R" (no need to chmod or chown or any other commands) and then I am tightening SIP restrictions after VoodooHDA.kext is installed.  I am currently using VoodooHDA.kext with SIP set using csr-active-config = <01000000>.  Sound quality is excellent.

  • Like 6
jlrycm
jlrycm
Posted
Posted (edited)
6 hours ago, deeveedee said:

There has been a lot discussed here and I have tested all of the recently recommended steps/commands.  Here's the very simple VoodooHDA.kext installation that works for me at this time:

  • Use VoodooHDA.kext 3.0.2 from here - I am not building my own VoodooHDA.kext nor have I found the need to re-sign the kext.  I'm using the pre-built VoodooHDA.kext as provided.
  • Set SIP and copy VoodooHDA.kext to /Library/Extensions as stated here.  Relaxing SIP restrictions more than setting csr-active-config = <03080000> will work but is not necessary
  • If tighter SIP restrictions are desired after installing VoodooHDA.kext, follow this

I am currently using VoodooHDA.kext with csr-active-config = <01000000>.  Only "Allow Untrusted Kexts" bit is set.  No other SIP restrictions need to be disabled after VoodooHDA.kext is installed.  

 

In summary, I am using the pre-built VoodooHDA.kext as provided, I am copying VoodooHDA.kext to /Library/Extensions using "cp -R" (no need to chmod or chown or any other commands) and then I am tightening SIP restrictions after VoodooHDA.kext is installed.  I am currently using VoodooHDA.kext with SIP set using csr-active-config = <01000000>.  Sound quality is excellent.

@deeveedee @Max.1974 I added VoodooHDA to Tahoe using the package created by @chris1111 and it is working for me without having to apply chmod, chown or any other commands, while setting SIP using csr-active-config = <01000000>

 

Last login: Mon Jun 30 14:45:05 on ttys000

jorgerodriguez@Jorges-Mac-Pro ~ % csrutil status

System Integrity Protection status: unknown (Custom Configuration).

 

Configuration:

Apple Internal: disabled

Kext Signing: disabled

Filesystem Protections: enabled

Debugging Restrictions: enabled

DTrace Restrictions: enabled

NVRAM Protections: enabled

BaseSystem Verification: enabled

 

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

jorgerodriguez@Jorges-Mac-Pro ~ %

Edited by jlrycm
  • Like 3
deeveedee
deeveedee
Posted
Posted (edited)

@jlrycm Thank you for reporting your findings.  It's good to have another approach that independently validates the use of csr-active-config = <01000000> after installing VoodooHDA.kext.  

 

Just to clarify for others who are following this, first you set csr-active-config = <03080000> to use Chris1111 installer.  After installation of VoodooHDA, you set csr-active-config = <01000000>.  Correct?

 

Edited by deeveedee
  • Like 2
jlrycm
jlrycm
Posted
Posted
2 hours ago, deeveedee said:

@jlrycm Thank you for reporting your findings.  It's good to have another approach that independently validates the use of csr-active-config = <01000000> after installing VoodooHDA.kext.  

 

Just to clarify for others who are following this, first you set csr-active-config = <03080000> to use Chris1111 installer.  After installation of VoodooHDA, you set csr-active-config = <01000000>.  Correct?

 

Correct. I did it as you explained.

  • Like 1
  • Thanks 1
Max.1974
Max.1974
Posted
Posted
7 minutos atrás, o LockDown disse:

@Fácia

Oi. Existe uma maneira de fazer o áudio Intel iGPU HDMI funcionar?

 

I saw today he said its not working 

 

image.thumb.png.a015210a2eccd614e83707f146ff9682.png

 

"Any chipset, but not start USB sound or HDMI" 

 

https://www.applelife.ru/threads/ustanovka-macos-tahoe-26-beta-na-intel-pc.2979499/page-47#post-1066165 

 

 

  • Thanks 1
deeveedee
deeveedee
Posted
Posted (edited)

Just a quick update on the installation of VoodooHDA.kext 3.0.2 in /L/E with csr-active-config = <01000000> as described here.  I am finding that once VoodooHDA.kext is installed, I don't need to worry about VoodooHDA.kext / csr-active-config for subsequent macOS Tahoe upgrades.  SIP remains configured with csr-active-config = <01000000> (no need to change it) and VoodooHDA.kext remains in /L/E.  Once VoodooHDA.kext was installed in Tahoe Beta 2, upgrading from Tahoe Beta 2 -> Beta 3 required no additional actions for working audio.

 

So far, I'm very pleased with how simple it is to install, maintain and use VoodooHDA for working audio in macOS Tahoe.

Edited by deeveedee
  • Like 6
  • 1 month later...
tlac
tlac
Posted
Posted
On 7/12/2025 at 3:19 PM, deeveedee said:

Just a quick update on the installation of VoodooHDA.kext 3.0.2 in /L/E with csr-active-config = <01000000> as described here.  I am finding that once VoodooHDA.kext is installed, I don't need to worry about VoodooHDA.kext / csr-active-config for subsequent macOS Tahoe upgrades.  SIP remains configured with csr-active-config = <01000000> (no need to change it) and VoodooHDA.kext remains in /L/E.  Once VoodooHDA.kext was installed in Tahoe Beta 2, upgrading from Tahoe Beta 2 -> Beta 3 required no additional actions for working audio.

 

So far, I'm very pleased with how simple it is to install, maintain and use VoodooHDA for working audio in macOS Tahoe.

 

I installed VoodooHDA and the VoodooHDA.prefPane with csr-active-config = <03080000> and they were working fine. Then I switched to <01000000>. While the sound is working, the prefPane is not.

Have you tried using the VoodooHDA.prefPane with <01000000>?

 

Screenshot2025-08-24at17_47_31.thumb.png.a0c46b88e4a8f34d9db732507b30514b.png

 

jlrycm
jlrycm
Posted
Posted (edited)
On 8/24/2025 at 12:00 PM, tlac said:

 

I installed VoodooHDA and the VoodooHDA.prefPane with csr-active-config = <03080000> and they were working fine. Then I switched to <01000000>. While the sound is working, the prefPane is not.

Have you tried using the VoodooHDA.prefPane with <01000000>?

 

Screenshot2025-08-24at17_47_31.thumb.png.a0c46b88e4a8f34d9db732507b30514b.png

 

@tlac for me the preference pane is working with 01000000. Have you tried removing the pane from quarantine and signing it in terminal?

 

to deal with Gatekeeper I use Sentinel.

Edited by jlrycm
tlac
tlac
Posted
Posted
21 hours ago, jlrycm said:

@tlac for me the preference pane is working with 01000000. Have tried removing the pane from quarantine and signing it in terminal?

 

to deal with Gatekeeper I use Sentinel.

 

Thanks, did it just work out of the box for you or did you need to tweak anything you mentioned earlier?

jlrycm
jlrycm
Posted
Posted
On 8/25/2025 at 4:46 PM, tlac said:

 

Thanks, did it just work out of the box for you or did you need to tweak anything you mentioned earlier?

I believe I had to go Privacy and Security and allow the installer to run but other than that, I don’t recall doing anything else.

xeu
xeu
Posted
Posted (edited)

Hi all,

 

I'm testing macOs 26 Tahoe right now, I stumbled upon VoodooHDA

I was using it ages ago then ditched it for AppleALC ; but it has a dependency on AppleHDA, which was unfortunately removed in Tahoe

 

There's a way to bring back AppleHDA from an older release, but you gotta install KDK package

And at each system update, you gotta do it again 😕

 

 

Long story short : i've tested VoodooHDA on my hardware - Lenovo T480 & X260

latest release 3.0.2 isn't working at all 😕

 

I've took a look onto VoodooHDA source-code and found out that both chipset T480 = ALC257  and X260 = ALC293 weren't supported, which explains.

 

then I've made a patch, build it locally with Xcode : it's working great !

 

I've made a PR https://github.com/CloverHackyColor/VoodooHDA/pull/4

 

Perhaps it could help other people

 

Regards,

Edited by xeu
  • Like 2
jlrycm
jlrycm
Posted
Posted (edited)
3 hours ago, tlac said:

@xeu

nice

Have you happened to check the HDMI/DP audio too?

HDMI shows up on my Intel 10th gen (UHD 630) but no sound, I'm thinking maybe those IDs are missing too.

I installed VoodooHDA using @chris1111 installer.

 

https://github.com/chris1111/VoodooHDA-Tahoe

Edited by jlrycm
  • Like 2
naiclub
naiclub
Posted
Posted
3 hours ago, jlrycm said:

I installed VoodooHDA using @chris1111 installer.

 

https://github.com/chris1111/VoodooHDA-Tahoe

2568-08-2810_13_33.thumb.png.e7a6d3bd6f69b65f96da4dcff459464e.png

 

The sound is excellent. After many years, it works 100% today. Thank you very much.

  • Like 3
  • 4 weeks later...
deeveedee
deeveedee
Posted
Posted (edited)

Now that macOS Tahoe Audio is working "perfectly" for me with VoodooHDA.kext 3.0.2, I'd like to focus on the only annoying behavior (for me) of VoodooHDA.kext.  I know it's been discussed before and solutions have been proposed, but no posted solutions that I have tried are working for me.

 

What causes VoodooHDA.kext loud audio "pop" when booting / re-booting?  My audio is Conexant CX20632 (spec attached).  I'm currently using VoodooHDA.kext without modifications to Info.plist, although I have tested different settings without resolving the audio "pop." 

 

Thanks for any explanation about why the audio "pop" happens at boot / re-boot and for any suggestions that resolve the issue.

 

EDIT: Note that audio quality with VoodooHDA.kext 3.0.2 is outstanding in macOS Tahoe.  The loud audio "pop" at boot does not affect the quality of audio once macOS is booted.  The audio "pop" is not an issue when sleeping / waking.

120547.pdf

Edited by deeveedee
  • Like 1
chris1111
chris1111
Posted
Posted (edited)

You need antipopd https://github.com/mttrb/antipopd?tab=readme-ov-file

The Old project is antipop  by Robert Tomsick 

EDIT**** I have build a Resource for Packaging antipop, easy install

 

 

Edited by chris1111
  • Like 1
  • Thanks 1
deeveedee
deeveedee
Posted
Posted

@chris1111 Thank you for the prompt response.  Antipopd did not resolve the "pop" that I reported in my previous post which is "not an issue when sleeping / waking" but is an issue that "happens at boot / re-boot."

 

I installed antipopd by following the instructions and then allowed antipopd in Tahoe's "System Settings > Privacy & Security > Security."  After testing Tahoe with antipopd over 5 boot cycles, I am not finding that antipopd has any effect on the audio "pop" that I reported.  

 

I read antipopd documentation and see that it is intended to resolve the following: 

antipopd is a utility program which keeps the audio system active to stop the popping sound that can occur when OS X puts the audio system to sleep

The "pop" that I am reporting is not occuring during sleep / wake.  It is occuring when my hack is booted and when macOS Tahoe is restarted.

  • Like 1
chris1111
chris1111
Posted
Posted (edited)
28 minutes ago, deeveedee said:

@chris1111 Thank you for the prompt response.  Antipopd did not resolve the "pop" that I reported in my previous post which is "not an issue when sleeping / waking" but is an issue that "happens at boot / re-boot."

 

I installed antipopd by following the instructions and then allowed antipopd in Tahoe's "System Settings > Privacy & Security > Security."  After testing Tahoe with antipopd over 5 boot cycles, I am not finding that antipopd has any effect on the audio "pop" that I reported.  

 

I read antipopd documentation and see that it is intended to resolve the following: 

antipopd is a utility program which keeps the audio system active to stop the popping sound that can occur when OS X puts the audio system to sleep

The "pop" that I am reporting is not occuring during sleep / wake.  It is occuring when my hack is booted and when macOS Tahoe is restarted.

did you try changing the PCM value to 50 ? 🫤 I dont know?

key>PCM</key>

<integer>100</integer>

Edited by chris1111
  • Thanks 1
deeveedee
deeveedee
Posted
Posted (edited)

@chris1111 Thanks again.  I think I tested that, but I will test again.

 

Also, I am currently using AppleALC.kext (not disabled in Tahoe) to block loading of AppleGFXHDA.kext which I found interferes with VoodooHDA.  Could it be that loading both AppleALC.kext and VoodooHDA.kext is causing the audio "pop" at boot?  If so, what is the "correct" way to block AppleGFXHDA.kext  so that it does not interfere with VoodooHDA?

 

Thank you for your help.

 

EDIT: Note that I tried to block AppleGFXHDA.kext with Open Core's Kernel > Block but that did not work for me.

Edited by deeveedee
chris1111
chris1111
Posted
Posted
5 minutes ago, deeveedee said:

@chris1111 Thanks again.  I think I tested that, but I will test again.

 

Also, I am currently using AppleALC.kext (not disabled in Tahoe) to block loading of AppleGFXHDA.kext which I found interferes with VoodooHDA.  Could it be that loading both AppleALC.kext and VoodooHDA.kext is causing the audio "pop" at boot?  If so, what is the "correct" way to block AppleGFXHDA.kext  so that it does not interfere with VoodooHDA?

 

Thank you for your help.

Maybe here

https://github.com/5T33Z0/OC-Little-Translated/blob/main/Content/11_Graphics/GPU/Disabling_AppleGFXHDA/README.md

  • Thanks 1
deeveedee
deeveedee
Posted
Posted

@chris1111 Thanks again.  That technique is for disabling HDAU associated with a dGPU, not for preventing AppleHDAGFX from binding to Intel HDEF.  I'll test your PCM idea (which I think I already tested, but will test again) and one other idea that I'm working on.  I'll report back if I find something.

  • Like 1
deeveedee
deeveedee
Posted
Posted

According to ChatGPT, the audio pop at boot and shutdown when using VoodooHDA is because VoodooHDA is improperly initializing the CODEC.  A solution provided by ChatGPT involves scripts that mute audio at shutdown and unmute at login.  Since I don't care about audio before login, this is a workable solution for me.  I am currently experimenting with the scripts provided by ChatGPT and the audio pop at boot has been completely eliminated.  I need to experiment more to eliminate the audio pop at shutdown.  When I have more time to experiment and I finalize a solution based on these scripts, I will post my findings.

 

Note that I tried setting "IOKitPersonalities > VoodooHDA > VoodooHDAEnableMuteFix" in VoodooHDA.kext Info.plist, but this did not make a difference.

  • Thanks 1
 Share
Go to topic listing
×
×
  • Create New...