Jump to content

VoodooHDA 3.1.2

Slice

By Slice,
in VoodooHDA

 Share
1042 posts in this topic

Recommended Posts

LockDown
LockDown
Posted
Posted (edited)
On 3/6/2026 at 5:40 AM, deeveedee said:

EDIT 2: I did not need to rename / change my "layout-id" property in DeviceProperties, since VoodooHDA.kext 3.1.0 is designed to "Read alc-layout-id (preferred) or layout-id from IORegistry".

Hi again @deeveedee

Im a little bit confused regarding "layout-id" even though 3.1.0 works for me.

Does this mean we need HDEF for layout-id to work? I asked coz i did nothing but installed 3.1.0 and it just works

Sorry. I really can't think of the right term for my inquiry

Edited by LockDown
  • Like 1
Slice
Slice
Posted
  • Author
Posted
3 hours ago, LockDown said:

Hi again @deeveedee

Im a little bit confused regarding "layout-id" even though 3.1.0 works for me.

Does this mean we need HDEF for layout-id to work? I asked coz i did nothing but installed 3.1.0 and it just works

Sorry. I really can't think of the right term for my inquiry

I think no. VoodooHDA doesn't depend on ACPI name vs AppleHDA.

  • Like 1
  • Thanks 2
deeveedee
deeveedee
Posted
Posted
10 hours ago, LockDown said:

Hi again @deeveedee

Im a little bit confused regarding "layout-id" even though 3.1.0 works for me.

Does this mean we need HDEF for layout-id to work? I asked coz i did nothing but installed 3.1.0 and it just works

Sorry. I really can't think of the right term for my inquiry

 

Not sure I understand, but I think what is important is that I installed VoodooHDA.kext 3.1.0 to replace VoodooHDA.kext 3.0.3 and I didn't need to change layout-id name or value and I didn't need to make any ACPI changes.  Just replace VoodooHDA.kext 3.0.x with 3.1.x and it should work.

  • Like 3
jlrycm
jlrycm
Posted
Posted
52 minutes ago, deeveedee said:

 

Not sure I understand, but I think what is important is that I installed VoodooHDA.kext 3.1.0 to replace VoodooHDA.kext 3.0.3 and I didn't need to change layout-id name or value and I didn't need to make any ACPI changes.  Just replace VoodooHDA.kext 3.0.x with 3.1.x and it should work.

@deeveedee have you noticed any audio quality improvement after installing the new version? 

Max.1974
Max.1974
Posted
Posted
8 horas atrás, deeveedee disse:

 

Não tenho certeza se entendi, mas acho que o importante é que instalei o VoodooHDA.kext 3.1.0 para substituir o VoodooHDA.kext 3.0.3 e não precisei alterar o nome ou o valor do layout-id e não precisei fazer nenhuma alteração no ACPI. Basta substituir VoodooHDA.kext 3.0.x por 3.1.x e deve funcionar.

 

In some preliminary tests I ran, changing the layout in config.plist to voodoo-layout-id made the names appear as if it were AppleALC. 😉 

 

7 horas atrás, jlrycm disse:

@deeveedeevocê notou alguma melhora na qualidade do áudio depois de instalar a nova versão?

 

Unfortunately I had some crackling in the test versions, so for now I will stay on the previous one, but the new PrefPane works well. 

  • Like 4
deeveedee
deeveedee
Posted
Posted
12 hours ago, jlrycm said:

@deeveedee have you noticed any audio quality improvement after installing the new version? 

My old ears aren't as sharp as they used to be, so take this with a few grains of salt ...  I don't notice any audio quality difference between VoodooHDA.kext 3.0.3 and 3.1.0.  Both produce outstanding audio quality.

  • Like 3
  • Thanks 1
deeveedee
deeveedee
Posted
Posted
38 minutes ago, chris1111 said:

Personally, I think it would be much better to manage to get VoodooHDA working from the bootloader,

as was the case before Big Sur. :D

 

Totally agree.  It was the first thing I tried (unsuccessfully) with 3.1.0.

  • Like 3
jlrycm
jlrycm
Posted
Posted
7 hours ago, Max.1974 said:

 

In both my friend ;) not so good now, but will be great!! 

I have the same ALC897 and I tried the newer VoodooHDA kext version with Clover and OpenCore and I haven’t noticed any audio improvement. Still waiting to see the effect of changing the config file to voodoo-layout-id as the computer is being used by my wife.

Max.1974
Max.1974
Posted
Posted
31 minutes ago, jlrycm said:

I have the same ALC897 and I tried the newer VoodooHDA kext version with Clover and OpenCore and I haven’t noticed any audio improvement. Still waiting to see the effect of changing the config file to voodoo-layout-id as the computer is being used by my wife.

 

My layout-id is 12. It works, but with distortion. I prefer using the old compiled kexts, which work fine. 

 

deeveedee
deeveedee
Posted
Posted (edited)

EDIT: @Slice The volume slider doesn't work for me with VoodooHDA.kext 3.1.1.  The volume is either full or off.  I'll revert to 3.1.0 and report findings here.

 

EDIT2: Normal volume slider bar functionality is restored after reverting to 3.1.0.  I am testing with Open Core 1.0.6.

 

EDIT3: The volume slider wasn't working properly for me with version 3.1.1 because I had an older VoodooHDA.prefPane installed in /Library/PreferencePanes.  After removing VoodooHDA.prefPane from /Library/PreferencePanes, the volume slider works normally.

Edited by deeveedee
  • Like 1
Max.1974
Max.1974
Posted
Posted (edited)
8 hours ago, Slice said:

The version 3.1.1 working fine for me in Tahoe 26.3.1

VoodooHDA.kext.zip 113.81 kB · 10 downloads

Thanks my friend, I will teste again... 

 

Edited: @Slice Input gain, if in use, causes distortion, but it also works fine when set to 0.

 

I will try compile kext 

 

CapturadeTela2026-03-10s08_01_28.thumb.png.26ff4f83ad70916d8b191582f09b7808.png

 

 

 

 

Edited by Max.1974
  • Like 1
deeveedee
deeveedee
Posted
Posted (edited)

VoodooHDA.kext 3.1.0 is still working perfectly for me.  I tried 3.1.1 another time, but still experienced the non-working volume slider.  No worries, since I'm happy with 3.1.0 for now.

 

Here's why layout-id or voodoo-layout-id both work with VoodooHDA.kext in Tahoe (I'm still using layout-id property for VoodooHDA.kext 3.1.0):

  

        /* voodoo-layout-id is set by bootloader (OpenCore DeviceProperties);
           layout-id on the PCI device may be overwritten by AppleHDA or the system */
        OSData *layoutData = OSDynamicCast(OSData, mPciNub->getProperty("voodoo-layout-id"));
        if (layoutData && layoutData->getLength() >= sizeof(UInt32))
                mLayoutId = *(const UInt32 *)layoutData->getBytesNoCopy();
        IOLog("VoodooHDA DBG: voodoo-layout-id -> mLayoutId=%u\n", (unsigned)mLayoutId);
        if (mLayoutId == 0) {
                layoutData = OSDynamicCast(OSData, mPciNub->getProperty("layout-id"));
                if (layoutData && layoutData->getLength() >= sizeof(UInt32))
                        mLayoutId = *(const UInt32 *)layoutData->getBytesNoCopy();
                IOLog("VoodooHDA DBG: layout-id -> mLayoutId=%u\n", (unsigned)mLayoutId);
        }

We don't have AppleHDA in Tahoe, so no issues with using layout-id.

Edited by deeveedee
  • Like 2
deeveedee
deeveedee
Posted
Posted

I was wrong about VoodooHDA.kext 3.1.0 and its need for a AppleGFXHDA blocker.  On my HP EliteDesk 800 G4/G5 Mini, I still need to load AppleALC.kext with VoodooHDA.kext 3.1.0, so that AppleALC blocks AppleGFXHDA.  Otherwise, AppleGFXHDA binds to HDAS (HDEF) preventing VoodooHDA.kext 3.1.0 from loading.  It is only on my HP EliteBook 850 G7 that I do not need AppleALC to block AppleGFXHDA when using VoodooHDA.kext 3.1.0 with macOS Tahoe.

 

My apologies for incorrect information earlier.   I should have performed more careful testing before reporting.

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