Jump to content

VoodooHDA 3.1.2

Slice

By Slice,
in VoodooHDA

 Share
1042 posts in this topic

Recommended Posts

chris1111
chris1111
Posted
Posted (edited)
7 hours ago, deeveedee said:

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.

@deeveedee

Try my Package of the Old antipop I remember in Yosemite using the antipop for a poping sound not for sleep

Its differant of the one you are trying

Test a reboot and Shutdown, If is not work use uninstall command

Hope that help 

Antipop-Package.zip

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

Thank you, @chris1111.  I'm currently testing simple LogoutHook and LoginHook scripts that mute and unmute audio.  If this works, it would be my preference rather than installing something else.  When I get some time, I will create a new test volume for Tahoe and try your package.  Thanks again!

 

EDIT: The two simple scripts are as follows 

file: mute-on.sh

#!/bin/bash
osascript -e "set volume with output muted"


file: mute-off.sh

#!/bin/bash
osascript -e "set volume without output muted"

 

Edited by deeveedee
  • Like 2
deeveedee
deeveedee
Posted
Posted (edited)

The scripts recommended by ChatGPT are currently working for me to address the audio "pop" when using VoodooHDA.kext 3.0.2 with Tahoe.  I tested a few of ChatGPT's recommended approaches and have condensed the recommendation to the following:

 

  1. Copy the attached mute-on.sh and mute-off.sh scripts to /usr/local/bin
  2. 'sudo chmod +x /usr/local/bin/mute-on.sh' and 'sudo chmod +x /usr/local/bin/mute-off.sh'
  3. Add a LogoutHook to mute audio at logout with the following command 
    sudo defaults write com.apple.loginwindow LogoutHook /usr/local/bin/mute-on.sh
  4. Implement a "LoginHook" (which Apple has removed from macOS), by doing the following
    1. Create directory ~/Library/LaunchAgents if the directory does not exist
    2. Copy the attached com.local.unmuteonlogin.plist to ~/Library/LaunchAgents
    3. Execute the following command 
      launchctl load ~/Library/LaunchAgents/com.local.unmuteonlogin.plist

 

The mute-on.sh script will run at Logout so that audio is muted for shutdown and at the next boot.  The mute-off.sh script will run at Login, so that audio is unmuted after Login.  My testing so far shows that the audio pop at boot is completely eliminated.  The audio pop at shut-down is quiet, but not completely eliminated.

com.local.unmuteonlogin.plist.zip mute-off.sh.zip mute-on.sh.zip

Edited by deeveedee
  • Like 6
verdazil
verdazil
Posted
Posted
54 minutes ago, LockDown said:

Your v3.0.2 release does not work with Audiodxe. But if i compile my own, it works.

OpenCore uses AudioDxe.efi as its own audio driver, completely independent of VoodooHDA. It is responsible for features such as the boot chime or audio feedback in the Boot Picker. This audio works even without any system audio drivers (like AppleALC or VoodooHDA), since it is handled entirely at the firmware/bootloader level.

  • Like 2
verdazil
verdazil
Posted
Posted
2 hours ago, LockDown said:

im on Clover and its a known issue since voodoohda v2.9.1

Clover also has its own audio driver, AudioDxe.efi, which works in the same way as OpenCore’s implementation. It provides boot chime and audio feedback in the boot menu, completely independent of macOS system audio drivers. For boot chime, VoodooHDA is not required and its version has no effect. However, AudioDxe.efi may sometimes conflict with VoodooHDA, but this only affects audio inside macOS, not the boot chime played by the bootloader.

  • Like 3
BuXb
BuXb
Posted
Posted
On 9/28/2025 at 4:33 AM, LockDown said:

@Slice

Just FYI

Your v3.0.2 v3.0.1 release from SF does not work with Audiodxe. But if i compile my own, it works.

And yes, im an old man who still likes startup sound 😁

LOL me too is an old man enjoying my HackBook's chime.

 

@LockDown would you be so kind and attach your self-compiled VoodooHDA? That would be very helpful ✌️because I'm also running into the issue of V-HDA 3.0.2 not working in Tahoe with boot chime enabled = played via AudioDxe (but working fine in Tahoe as soon as I disable boot chime audio).

 

Shout-out also to @verdazil for letting us know that this is a known issue. In case this could also be tackled on the AudioDxe.efi level, it would be neat if there were an alternative compile of that driver which does not have or cause this bug.

 

.. and many thanks to @deeveedee, @chris1111 and @Max.1974 for all your professional top-level contributions in this topic - kudos and respect 🤙

  • Like 2
  • Thanks 1
LockDown
LockDown
Posted
Posted (edited)
56 minutes ago, BuXb said:

would you be so kind and attach your self-compiled VoodooHDA?

Sure!

This was taken from @Slice's github using latest v3.0.2 source & MacKernelSDK.

All I did is changed the MACOSX_DEPLOYMENT_TARGET to 10.9. Rest is untouched.

Using Xcode 16.4. Lower than xcode 15 didn't work if I recall.

 

VoodooHDA_3.0.2-Startupsound.zip

Edited by LockDown
  • Like 3
  • Thanks 3
BuXb
BuXb
Posted
Posted

@LockDown YES - VoodooHDA finally fully working in Tahoe WITH boot chime/ startup sound activated - YAHOO 🤩

 

@chris1111 I strongly recommend you update your Tahoe installer with LockDown's compile. This odd bug took me countless hours of debugging until nothing but the startup sound was left, and I'm 100% certain I'm not the only one who wasn't able to get V-HDA working regardless of what they tried. LockDown managed to fix an old issue which is positively awesome 😎

  • Like 5
Max.1974
Max.1974
Posted
Posted (edited)
7 minutes ago, BuXb said:

Anybody here already updated to 26.0.1? If so, did you have to remove VoodooHDA from /L/E/ for the update to run through, or could it remain?

Hi @BuXb With VoodooHDA, there’s no need to remove it — just reinstall the patch if it’s not recognized, but it usually doesn’t lose functionality. If necessary, simply run the installation script again.

 

You can use this commands from Terminal after upgrade:

  

sudo chmod -Rf 755 /L*/E*
sudo chown -Rf 0:0 /L*/E*
sudo touch -f /L*/E*
sudo chmod -Rf 755 /S*/L*/E*
sudo chown -Rf 0:0 /S*/L*/E*
sudo touch -f /S*/L*/E*
sudo kextcache -Boot -U /
sudo kextutil -v /Library/Extensions/VoodooHDA.kext
sudo kextload /Library/Extensions/VoodooHDA.kext

After reboot you can test: 

  

log show --last boot | grep -i voodoo

 

One by One ;) 

 

Edited by Max.1974
  • Like 1
Slice
Slice
Posted
  • Author
Posted
On 9/30/2025 at 2:32 AM, LockDown said:

Sure!

This was taken from @Slice's github using latest v3.0.2 source & MacKernelSDK.

All I did is changed the MACOSX_DEPLOYMENT_TARGET to 10.9. Rest is untouched.

Using Xcode 16.4. Lower than xcode 15 didn't work if I recall.

 

VoodooHDA_3.0.2-Startupsound.zip 97.2 kB · 15 downloads

Wow! Thank you for the amazing results!

  • Like 2
Slice
Slice
Posted
  • Author
Posted
On 9/28/2025 at 5:32 AM, verdazil said:

OpenCore uses AudioDxe.efi as its own audio driver, completely independent of VoodooHDA. It is responsible for features such as the boot chime or audio feedback in the Boot Picker. This audio works even without any system audio drivers (like AppleALC or VoodooHDA), since it is handled entirely at the firmware/bootloader level.

You are wrong because AudioDxe tunes audio chip that prevents VoodooHDA to tune it properly. I just wonder if @LockDown found a solution.

  • Like 1
  • Confused 1
schrup21
schrup21
Posted
Posted
On 9/30/2025 at 2:32 AM, LockDown said:

Sure!

This was taken from @Slice's github using latest v3.0.2 source & MacKernelSDK.

All I did is changed the MACOSX_DEPLOYMENT_TARGET to 10.9. Rest is untouched.

Using Xcode 16.4. Lower than xcode 15 didn't work if I recall.

 

VoodooHDA_3.0.2-Startupsound.zip 97.2 kB · 19 downloads

Oh Man! I tried VoodooHDA to get working so many times with no luck - your creation did it! 🤩

  • Like 2
Slice
Slice
Posted
  • Author
Posted
4 hours ago, LockDown said:

i did nothing special about it. compiled VoodooHDA v3.0.2 source & MacKernelSDK with Xcode 16.4, then put back Audiodxe and VoodooHDA started to work together

It looks like old Xcode bug.

  • Like 1
  • Haha 1
verdazil
verdazil
Posted
Posted
10 hours ago, Slice said:

You are wrong because AudioDxe tunes audio chip that prevents VoodooHDA to tune it properly.

You are wrong because "prevents VoodooHDA to tune it properly" just points out the problems and shortcomings of the VoodooHDA driver. Also, this does not mean in any way that AudioDxe is somehow dependent on VoodooHDA.

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