Jump to content
1042 posts in this topic

Recommended Posts

Thank you, @MaLd0n.  could you please post the link to the source for that version of VoodooHDA?

 

EDIT: I am currently using VoodooHDA.kext 3.3.4 Pre-Release version posted here.  The alert "echo" problem was introduced by one of the 4 commits between this pre-release and the final version of 3.3.4.

Edited by deeveedee
  • Like 1
1 hour ago, deeveedee said:

Thank you, @MaLd0n.  could you please post the link to the source for that version of VoodooHDA?

 

EDIT: I am currently using VoodooHDA.kext 3.3.4 Pre-Release version posted here.  The alert "echo" problem was introduced by one of the 4 commits between this pre-release and the final version of 3.3.4.

There was many fixes related to hdmi on amd in 3.3.5 branch. It would be nice for further fixing process if somebody with Tahoe could test it with the included utility (a guide is also in the repo) and put here the resulting archive with some feedback on how it was.

  • Thanks 3

@Dmitry R Thank you for your reply!  My tests of VoodooHDA.kext 3.3.4 pre-release and VoodooHDA.kext 3.3.4 Release are with Intel HD Audio internal speakers (not AMD HDMI).  I will try to test AMD HDMI and post my results.  With Intel HD Audio, I find that 3.3.4 pre-Release works well. With 3.3.4 Release, alerts (like emptying trash) are played 2 or more times).  The alert audio problem was introduced by one of the 4 commits between 3.3.4 pre-release and 3.3.4 release.

 

Thank you for your hard work and effort!

Edited by deeveedee
  • Like 2
1 hour ago, Dmitry R said:

There was many fixes related to hdmi on amd in 3.3.5 branch. It would be nice for further fixing process if somebody with Tahoe could test it with the included utility (a guide is also in the repo) and put here the resulting archive with some feedback on how it was.

Thanks Man! ;) 

  • Like 1
On 4/25/2026 at 10:26 AM, MaLd0n said:

Use this version. Work fine in all cases here.

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

I'll test it!

Thank you!

 

This version is perfect.

But when it starts up on the Apple logo, there's a very loud popping sound.

The version I use here doesn't have that popping sound!

Edited by Pc Bacabal
  • Like 1
Posted (edited)

@Pc Bacabal I'm glad you asked the question again.  The "pop" issue has been discussed in this thread, but using DisableInputMonitor=true has never been offered as a solution to the "loud bump" before in this thread.  I found one reference to it in this thread here and saw It in plists on this page, but never as a solution like this.

 

Thank you for asking.  I have desktop platforms that exhibit this problem and will be sure to test the solution when I'm able.

 

@Slice Is there any reason why DisableInputMonitor=true isn't the default setting in Info.plist?

 

EDIT: I found another thread titled "VoodooHDA - Common Problems" that mentions DisableInputMonitor=true as a solution for the loud "pop"

Edited by deeveedee
47 minutes ago, deeveedee said:

@Pc Bacabal I'm glad you asked the question again.  The "pop" issue has been discussed in this thread, but using DisableInputMonitor=true has never been offered as a solution to the "loud bump" before in this thread.  I found one reference to it in this thread here and saw It in plists on this page, but never as a solution like this.

 

Thank you for asking.  I have desktop platforms that exhibit this problem and will be sure to test the solution when I'm able.

 

@Slice Is there any reason why DisableInputMonitor=true isn't the default setting in Info.plist?

It decreased considerably, as the sound was very loud. I only notice if I stand really close to the speakers.

11 hours ago, deeveedee said:

 

@Slice Is there any reason why DisableInputMonitor=true isn't the default setting in Info.plist?

 

 

Agree, it is better to be default true. But with a possibility to change  to false. One of the possible application of the Input Monitor is a possibility to record karaoke:
 you open some player with music and simultaneously open QuickTime to record from microphone. Your record will contain the music if good tuning.

  • Thanks 1
Posted (edited)

@Slice @Pc Bacabal I'm confused.  I just downloaded VoodooHDA.kext 3.3.5 and see that DisableInputMonitor is already True.

Screenshot2026-05-07at10_11_13AM.png.a6b47a54f4fe0e35259fad8e0a2ca134.png

 

I checked back as far as VoodooHDA.kext 3.1.2 and it was also defaulting to True.

 

@Pc Bacabal If DisableInputMonitor is already true, what did you change?

 

 

EDIT: I checked VoodooHDA.kext 3.0.3 and see that DisableInputMonitor = False, so the default value of DisableInputMonitor was changed to True after version 3.0.3.  I looked for the change in the change logs and don't see it, so maybe I just missed it.  Note that when I implemented this fix for the "loud bump" I was testing VoodooHDA.kext 3.0.2, so I still need to test the newer versions with DisableInputMonitor=True to confirm that this is a fix on my hacks.

Edited by deeveedee
1 hour ago, deeveedee said:

@Slice @Pc Bacabal I'm confused.  I just downloaded VoodooHDA.kext 3.3.5 and see that DisableInputMonitor is already True.

Screenshot2026-05-07at10_11_13AM.png.a6b47a54f4fe0e35259fad8e0a2ca134.png

 

I checked back as far as VoodooHDA.kext 3.1.2 and it was also defaulting to True.

 

@Pc Bacabal If DisableInputMonitor is already true, what did you change?

 

 

EDIT: I checked VoodooHDA.kext 3.0.3 and see that DisableInputMonitor = False, so the default value of DisableInputMonitor was changed to True after version 3.0.3.  I looked for the change in the change logs and don't see it, so maybe I just missed it.  Note that when I implemented this fix for the "loud bump" I was testing VoodooHDA.kext 3.0.2, so I still need to test the newer versions with DisableInputMonitor=True to confirm that this is a fix on my hacks.

It looked false to me! I just changed it to true, did the repair, and restarted.

Posted (edited)

@Pc Bacabal If DisableInputMonitor was False, then you must still be using a version of VoodooHDA.kext older than 3.1.2.  In 3.1.2 and newer, DisableInputMonitor is already defaulting to True.  The other possibility is that you had initially changed DisableInputMonitor to False when you installed VoodooHDA.kext, but I suspect that's not the case.

Edited by deeveedee
  • Like 1
18 minutes ago, deeveedee said:

@Pc Bacabal If DisableInputMonitor was False, then you must still be using a version of VoodooHDA.kext older than 3.1.2.  In 3.1.2 and newer, DisableInputMonitor is already defaulting to True.  The other possibility is that you had initially changed DisableInputMonitor to False when you installed VoodooHDA.kext, but I suspect that's not the case.

I think I changed it to false when I was adjusting the volume controls. I am using this version https://olarila.com/files/Utils/VoodooHDA.pkg.zip @MaLd0n

@Pc Bacabal You must have changed it when you installed VoodooHDA.kext using MaLd0n's installer package (a good trick, since it's not easy to do that accidentally).  The default value of DisableInputMonitor is True in MaLd0n's installer package that you linked.

 

Screenshot2026-05-07at12_13_13PM.png.4b5612c3809d4d710277525811d4238d.png

10 hours ago, deeveedee said:

@Pc Bacabal You must have changed it when you installed VoodooHDA.kext using MaLd0n's installer package (a good trick, since it's not easy to do that accidentally).  The default value of DisableInputMonitor is True in MaLd0n's installer package that you linked.

 

Screenshot2026-05-07at12_13_13PM.png.4b5612c3809d4d710277525811d4238d.png

I need to edit voodoo.kext and alter the volume controls. Maybe I'll end up accidentally altering it.

  • Like 1

I found commits in Dmitry's VoodooHDA.kext repo that address the startup "pop" which we should have seen starting with VoodooHDA.kext 3.1.2.  

Spoiler

Screenshot2026-05-08at10_47_18AM.thumb.png.c85143ca14feda7bcf44f7866d15f81d.png

 

Some of the commits like this claim that the fix is independent of DisableInputMonitor.

 

It does appear that we should have seen resolution of the startup "pop" in VoodooHDA.kext 3.1.2. 

Posted (edited)
53 minutes ago, deeveedee said:

I found commits in Dmitry's VoodooHDA.kext repo that address the startup "pop" which we should have seen starting with VoodooHDA.kext 3.1.2.  

  Hide contents

Screenshot2026-05-08at10_47_18AM.thumb.png.c85143ca14feda7bcf44f7866d15f81d.png

 

Some of the commits like this claim that the fix is independent of DisableInputMonitor.

 

It does appear that we should have seen resolution of the startup "pop" in VoodooHDA.kext 3.1.2. 

Exactly! I agree.

Edited by Pc Bacabal
  • 2 weeks later...
Posted (edited)

I have confirmed that DisableInputMonitor=True in the VoodooHDA.kext Info.plist fixes the loud "pop" at startup.  I am using VoodooHDA.kext 3.3.4 pre-release and no longer need the previous fix that I had implemented here.  As discussed earlier, DisableInputMonitor=True is the default setting in VoodooHDA.kext in versions 3.1.2 and later.  Thank you for this fix, @Slice.

 

EDIT: To remove the fix that I provided here, open terminal and issue the following commands:

sudo defaults delete com.apple.loginwindow LogoutHook
sudo rm /usr/local/bin/mute-on.sh
launchctl unload ~/Library/LaunchAgents/com.local.unmuteonlogin.plist
sudo rm ~/Library/LaunchAgents/com.local.unmuteonlogin.plist
sudo rm /usr/local/bin/mute-off.sh

To confirm removal of the fix, issue the following commands in terminal

launchctl list | grep unmute
sudo defaults read com.apple.loginwindow LogoutHook

 

Edited by deeveedee
  • Like 1

I'm still using VoodooHDA.kext 3.3.4 Pre-release for my Intel HD Audio (I don't need AMD Radeon HDMI Audio) because later versions of VoodooHDA.kext that I tested produced an alert "echo" (alerts like trashcan emptying are played multiple times).  Is anyone using a newer version of VoodooHDA.kext? If so, which version and what did you configure to resolve the alert echo problem?

×
×
  • Create New...