Jump to content

VoodooHDA 3.1.2

Slice

By Slice,
in VoodooHDA

 Share
1051 posts in this topic

Recommended Posts

Max.1974
Max.1974
Posted
Posted (edited)
13 hours ago, Slice said:

The driver with latest changes concerning compatibility with some hardware (x99 for example)

VoodooHDA.kext.zip 114.21 kB · 8 downloads

And my result

image.png

The 7.1 sound is impossible with AppleALC, this is VoodooHDA feature.

And in this case the output remains the same after reboot.

 

To do this I placed four outputs in same group 1 (second digit from right).

 

image.png

 

 

Works nice too my friend!! Thank You!! 

;) 

 

 

 

CapturadeTela2026-03-20s19_19_49.png.eda17b5d1f99f9b48729ef1bf90b0d13.png

Edited by Max.1974
  • Like 3
MaLd0n
MaLd0n
Posted
Posted
4 hours ago, deeveedee said:

I was asking for the coding difference between the two versions that you posted.  In other words, what changed from the first version you posted to the second version? Thank you.  

Some commits from devs

  • Like 1
  • Thanks 1
deeveedee
deeveedee
Posted
Posted (edited)
On 3/20/2026 at 3:27 PM, MaLd0n said:

No sound with last changes. Last good for me is this version bellow with correct layout=id.

https://olarila.com/files/Utils/VoodooHDA.pkg.zip

 

Working perfectly for me on my HP EliteBook 850 G7 running Tahoe 26.4 Beta

 

EDIT: Also working perfectly for me on multiple HP EliteDesk 800 G4/G5 Mini hacks.  

 

The things I like most about the use of VoodooHDA.kext over OCLP-audio patches are

  • No root patches that break the APFS seal
  • VoodooHDA works with SIP csr-active-config = <01000000> (Allow Untrusted Kexts).  I'm already injecting "Untrusted" kexts with Open Core, so this SIP setting does not further compromise macOS security.  In addition, with csr-active-config = <01000000>, I still need to relax SIP to csr-active-config = <03000000> (Allow Untrusted FS and Allow Untrusted Kexts) if I want to allow any other "Untrusted" kexts in addition to VoodooHDA, so there's no chance that other kexts will be allowed without my approval.
  • Once I install VoodooHDA.kext for working audio in Tahoe, macOS Tahoe updates do not require any other manual operations for working audio (e.g., no re-installation of "root patches").  For example, upgrades from macOS Tahoe 26.3 -> 26.4 don't require any re-installation of VoodooHDA.  It just works.
  • I don't need to uninstall any root-patches for incremental macOS updates.  Incremental macOS update work with VoodooHDA installed.
  • VoodooHDA audio quaiity is outstanding.  The rumors of bad audio quailty with VoodooHDA are gtreatly exaggerated (maybe left over from old versions of VoodooHDA).
Edited by deeveedee
  • Like 2
deeveedee
deeveedee
Posted
Posted

@Slice Thank you for continuing to maintain VoodooHDA.kext.  I have tested the latest version 3.1.2 that you posted and the 3.1.2 installer shared by MaLd0n here.  The version shared by MaLd0n works better for me, but I don't know why since I don't have visibility into the differences.  

 

With your latest posted 3.1.2, I cannot control volume (same problem that I observed before).  Moving the Volume slider does not change the audio volume for me.   I am installing VoodooHDA.kext to /Library/Extensions with "cp -R" and I am not using VoodooHDA.prefPane.

jlrycm
jlrycm
Posted
Posted
1 hour ago, deeveedee said:

With your latest posted 3.1.2, I cannot control volume (same problem that I observed before).  Moving the Volume slider does not change the audio volume for me.   I am installing VoodooHDA.kext to /Library/Extensions with "cp -R" and I am not using VoodooHDA.prefPane.

The issue I have right now is that when I move the VoodooHDA preference pane volume slider clock wise to 12 or 2 o’clock, the audio is gone. Is this expected?  @deeveedeeIs this the issue you are having? I’ll try @MaLd0n suggestion when I get home.

deeveedee
deeveedee
Posted
Posted (edited)

@MaLd0n thank you (and also thank you to Lockdown) for the suggestion.  Enabling VoodooHDAEnableVolumeChangeFix does resolve the non-working volume slider problem.  Note that VoodooHDAEnableVolumeChangeFix is different from VoodooHDAEnableHalfVolumeFix.

 

@jlrycm I am not using the VoodooHDA pref pane, so I'm not sure if that problem is related.

 

With Slice's latest posted VoodooHDA.kext here and MaLd0n's fix here, audio in Tahoe is working perfectly for me on my HP EliteBook 850 G7.

Edited by deeveedee
  • Like 5
oSxFr33k
oSxFr33k
Posted
Posted (edited)

Does v3.1.2 work fine in Sonoma and Sequoia?  I see everyone who is running Tahoe says it’s working.   For some reason, the release 2.9.8 worked for me in Sonoma and I didn’t have to do any modifications at all in the voodoo config except Maldon’s fix, but this newest version doesn’t seem to work in Sonoma or in Sequoia. I’ll try a few more things.   Not going to run Tahoe until they have graphics patches I see no reason to do so.  
 

Asus Laptop G750JX Nvidia GTX770 works flawless with all the functionality as you find in the MacBook Pro 11,3 late 2013 15 inch, in all releases of MacOS.  The internal Intel graphics is disabled by Asus.  

 

Edited:

 

v2.9.8 is working attached maybe someone can tell my why this one works and 3.1.2 does not.  I even tried putting in the node values from 2.9.8 into 3.1.2 and nothing.

 

Edited:

 

I figured it out I had AppleALC.kext enabled in the OC plist.  The new issue is v3.1.2 shows internal and analog while v2.9.8 shows normal two speakers for this laptop stereo rear and sub bass in the front.  I use the audio midi and create multi-device.  Is the issue that Slice's post about channel issue in Sonoma fix is what I need to do in v3.1.2 for Sequoia?  Add the information he has shown in his post?

 

Edited Again:

 

Adding those values did not help actually lost one internal speaker and microphone.  I'll just use v2.9.8 until I can get some help to figure out what I need to do for v3.1.2 to get back two speakers.

 

v2.9.8

 

VoodooHDA.kext.zip

 

v2.9.8

 

v2.9.8.png

 

v3.1.2

 

v3.1.2.png

 

 

 

VoodooHDA getdump-Output-v2.9.8.txt VoodooHDA getdump-Output-v3.1.2.txt

Edited by oSxFr33k
attached a file
Slice
Slice
Posted
  • Author
Posted

The version 3.0.2 doesn't work on some computers while 2.9.8 does. The fact.

We found this mistake and correct in 3.0.4 and up. You may test 3.1.2.

Personally I am using Sequoia and 3.0.4, 3.1.2 up future 3.2.0 (with HDMI support) works in Sequoia too. Moreover it tested in Catalina now. 

  • Like 2
  • Thanks 1
oSxFr33k
oSxFr33k
Posted
Posted (edited)
2 hours ago, Slice said:

The version 3.0.2 doesn't work on some computers while 2.9.8 does. The fact.

We found this mistake and correct in 3.0.4 and up. You may test 3.1.2.

Personally I am using Sequoia and 3.0.4, 3.1.2 up future 3.2.0 (with HDMI support) works in Sequoia too. Moreover it tested in Catalina now. 

 

 

Hi Slice,  I made a mod and got the one internal speaker but only one so I can't control left and right side separately, can you have a look and a hint of what I should try.  I attached the modded voodoohda config and the dump.  It should show two internal speakers and only one shows as I said.  It looks like  speaker node 23 is in association with nid 33.   I thought I fixed this in the config?

 

Jack sensing: merged HP Out nid=33 into association 3 seq=1 (with Speaker nid=23)
Jack sensing: merged Ext Mic nid=25 into association 1 seq=1 (with Int Mic nid=18)

 

Edited:

 

I modded up to 7 different configurations and none gives the two speakers back for stereo only one.

 

 

 

 

 

 

VoodooHDA.kext.zip VoodooHDA getdump-Output-3.1.2-mod8.txt

Edited by oSxFr33k
MaLd0n
MaLd0n
Posted
Posted
On 3/21/2026 at 10:05 AM, deeveedee said:
  • VoodooHDA audio quaiity is outstanding.  The rumors of bad audio quailty with VoodooHDA are gtreatly exaggerated (maybe left over from old versions of VoodooHDA).

The quality is very good and we can easily customize it.

  • Like 3
oSxFr33k
oSxFr33k
Posted
Posted (edited)
5 hours ago, Slice said:

The version 3.0.2 doesn't work on some computers while 2.9.8 does. The fact.

We found this mistake and correct in 3.0.4 and up. You may test 3.1.2.

Personally I am using Sequoia and 3.0.4, 3.1.2 up future 3.2.0 (with HDMI support) works in Sequoia too. Moreover it tested in Catalina now. 

 

So I retested the stereo sliders on v2.9.8 and v3.1.2 is more accurate.  I actually am not controlling left and right front speakers one slider is for both and the other not sure for v2.9.8.   Are we normally able to control the stereo speakers left/right with the sliders from Audio Midi Setup in Utilities?   Does VoodooHDA give you this functionality if not then v3.1.2 is now working great.

 

Thanks

Edited by oSxFr33k
oSxFr33k
oSxFr33k
Posted
Posted (edited)
2 hours ago, Slice said:

If I understand you then we can't control volume of left and right speaker separately. Use system Balance control.


That is exactly what I’m using. It’s called the audio midi set up and there’s two sliders per speaker.   Under the old AppleHDA and older MacOs using VoodooHDA I was able to control balance but not with newer VoodooHDA in newer MacOS after BigSur.  The left or right if slidden off completely silences both sides even if one of them is full volume and as long as both are slid toward more volume I have sound and it’s always stereo the control for balance is nonexistent. 
 

Can you see if you observe this on your device.  

Edited by oSxFr33k
Slice
Slice
Posted
  • Author
Posted
2 hours ago, oSxFr33k said:


That is exactly what I’m using. It’s called the audio midi set up and there’s two sliders per speaker.   Under the old AppleHDA and older MacOs using VoodooHDA I was able to control balance but not with newer VoodooHDA in newer MacOS after BigSur.  The left or right if slidden off completely silences both sides even if one of them is full volume and as long as both are slid toward more volume I have sound and it’s always stereo the control for balance is nonexistent. 
 

Can you see if you observe this on your device.  

I checked just now. The balance work left and rightimage.png

 

 

  • Like 2
  • Thanks 1
chris1111
chris1111
Posted
Posted (edited)

Thanks @Slice It is really beautifull!
Compiling VoodooHDAPrefPane from source It's like original of Tahoe Icon :thumbsup_anim:

 

One Liner code build ⬇︎ 

git clone https://github.com/CloverHackyColor/VoodooHDA.git && xcodebuild -project ./VoodooHDA/VHDAPrefPane/VoodooHDA/VoodooHDA.xcodeproj -alltargets -configuration Release && Open ./VoodooHDA/VHDAPrefPane/VoodooHDA/build/Release

 

image.png.d08a03f85890b36d81df30d5ced1e747.png

Edited by chris1111
  • Like 2
  • Thanks 1
Max.1974
Max.1974
Posted
Posted

This work turned out so well that I created an app to compile the release of VoodooHDA.kext, downloading the original repository and creating the pkg installer.

Thanks to @Slice and @chris1111.

 

Spoiler

 

 

 

VoodooHDA-Builder.dmg

 

 

CapturadeTela2026-04-04s20_21_45.png.ab1503aeb12c291cb4d3ec371895fd7c.png

 

CapturadeTela2026-04-04s20_21_51.png.fdffef74d327c9b925a37546523c33b0.png

 

 

👓

When compiled on your own machine, the sound works more perfectly for your hardware. ;) 

  • Like 1
deeveedee
deeveedee
Posted
Posted
12 minutes ago, Max.1974 said:

When compiled on your own machine, the sound works more perfectly for your hardware. ;) 

 

This is new information for me.  Why does the build machine matter?  How does building VoodooHDA on one's own machine make it better than the same version downloaded from Slice or MaLd0n?

Max.1974
Max.1974
Posted
Posted
17 minutes ago, deeveedee said:

 

This is new information for me.  Why does the build machine matter?  How does building VoodooHDA on one's own machine make it better than the same version downloaded from Slice or MaLd0n?

 

In theory, if the same source code, compiler, and build settings are used, the result should be basically the same as the one provided by Slice or MaLd0n.

 

However, in practice there can still be differences depending on the hardware environment. For example, on my machines the kext compiled and packaged for my desktop does not behave the same way on my laptop, and vice versa. Different audio codecs and hardware implementations can lead to slightly different results. Another point is that on macOS the Xcode toolchain interacts closely with the system environment. In some cases the build process can pick up differences related to the local hardware, SDK, or toolchain configuration. These differences are not always visible, but they can influence how the driver behaves on a specific machine. 

 

So building locally is not necessarily about making the kext “better”, but about adapting, testing, and packaging it in the same environment where it will be used. This gives more control over the build and sometimes results in better behavior on that specific hardware.

 

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