#77 Equalizer APO does not work with Realtek UAD driver

[foresterr]

It installed OK, but then does absolutely nothing. No logs are created, even with trace enabled. In Configurator APO shows as installed, but in troubleshooting options, "Use original APO" checkboxes are grayed out and unselectable.

The older style drivers still work, but I'm wondering if it's something easily fixable. I found something about SFX MFX EFX entries being different between UAD and non-UAD driver, UAD one using "composite" and "offload" entries, but I don't understand any of it ;)

[alanfox2000]

Solution

1. Delete the below Single APO CLSID and Multiple APO CLSID registry key of it exist on

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render{Device GUID}\FxProperties, Device GUID is where you "Copy Device Commend to Clipboard" on Equalizer APO configurator

2. On Equalizer APO configurator, select "Install as LFX/GFX"

---

Cause

Equalizer APO configurator have not figure out Multiple APO CLSID, KeywordDetector CLSID.

If StreamEffectClsid / ModeEffectClsid / EndpointEffectClsid / KeywordDetector_StreamEffectClsid / KeywordDetector_ModeEffectClsid / KeywordDetector_EndpointEffectClsid exist, Windows will ingore PreMixEffectClsid PostMixEffectClsid

If Multiple APO CLSID exist, Windows will ingore Single APO CLSID

KeywordDetector CLSID use for Microphone.

Single APO CLSID ( REG_SZ )

PKEY_FX_PreMixEffectClsid           = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},1"
PKEY_FX_PostMixEffectClsid          = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},2"
PKEY_FX_UserInterfaceClsid          = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},3"
PKEY_FX_StreamEffectClsid           = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},5"
PKEY_FX_ModeEffectClsid             = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},6"
PKEY_FX_EndpointEffectClsid         = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},7"
PKEY_FX_KeywordDetector_StreamEffectClsid   = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},8"
PKEY_FX_KeywordDetector_ModeEffectClsid     = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},9"
PKEY_FX_KeywordDetector_EndpointEffectClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},10"
PKEY_FX_Offload_StreamEffectClsid    = "{D04E05A6-594B-4FB6-A80D-01AF5EED7D1D},11"
PKEY_FX_Offload_ModeEffectClsid      = "{D04E05A6-594B-4FB6-A80D-01AF5EED7D1D},12"

Multiple APO CLSID ( REG_MULTI_SZ )

PKEY_CompositeFX_StreamEffectClsid   = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},13"  
PKEY_CompositeFX_ModeEffectClsid     = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},14"
PKEY_CompositeFX_EndpointEffectClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},15"
PKEY_CompositeFX_KeywordDetector_StreamEffectClsid   = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},16"
PKEY_CompositeFX_KeywordDetector_ModeEffectClsid     = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},17"  
PKEY_CompositeFX_KeywordDetector_EndpointEffectClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},18"
PKEY_CompositeFX_Offload_StreamEffectClsid   = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},19"  
PKEY_CompositeFX_Offload_ModeEffectClsid     = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},20"

; --- These Multiple APOs Registry not found on Windows SDK but on Realtek UAD ---
PKEY_CompositeFX_KeywordDetector_StreamEffectClsid_W   = "{D05E087D-1F27-461B-B229-66247FDCDE2C},16"
PKEY_CompositeFX_KeywordDetector_ModeEffectClsid_W     = "{D05E087D-1F27-461B-B229-66247FDCDE2C},17"  
PKEY_CompositeFX_KeywordDetector_EndpointEffectClsid_W = "{D05E087D-1F27-461B-B229-66247FDCDE2C},18"

Processing Modes ( REG_MULTI_SZ )

PKEY_SFX_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},5"
PKEY_MFX_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},6"
PKEY_EFX_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},7"
PKEY_SFX_KeywordDetector_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},8"
PKEY_MFX_KeywordDetector_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},9"
PKEY_EFX_KeywordDetector_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},10"
PKEY_SFX_Offload_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},11"
PKEY_MFX_Offload_ProcessingModes_Supported_For_Streaming = "{D3993A3F-99C2-4402-B5EC-A92A0367664B},12"

Audio Signal Processing Modes ( Value of Processing Modes )

AUDIO_SIGNALPROCESSINGMODE_DEFAULT = "{C18E2F7E-933D-4965-B7D1-1EEF228D2AF3}"
AUDIO_SIGNALPROCESSINGMODE_SPEECH = "{FC1CFC9B-B9D6-4CFA-B5E0-4BB2166878B2}"
AUDIO_SIGNALPROCESSINGMODE_COMMUNICATION = "{98951333-B9CD-48B1-A0A3-FF40682D73F7}"
AUDIO_SIGNALPROCESSINGMODE_MEDIA = "{4780004E-7133-41D8-8C74-660DADD2C0EE}"
AUDIO_SIGNALPROCESSINGMODE_MOVIE = "{B26FEB0D-EC94-477C-9494-D1AB8E753F6E}"
AUDIO_SIGNALPROCESSINGMODE_NOTIFICATION = "{9CF2A70B-F377-403B-BD6B-360863E0355C}"

[Kaz]

Hi. I don't understand what you mean by "delete below Single APO CLSID and Multiple APO CLSID"

when I go to indicated directory, this is all I see (please refer to the attachment)

[alanfox2000]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render{Device GUID}\ ** FxProperties**

[Kaz]

I've deleted the ones you highlighted and still the equalizer doesn't work for me. Is there more that I should delete?

[alanfox2000]

Use FX Configurator which come from APO Driver

1. Run FX Configurator, select the endpoint you wanted.
2. Backup endpoint registry first.
3. Click "Product Config Tool". Select Equalizer APO from drop down list, click "Apply Product Settings to Selected Endpoints".

[Igor Baryshev]

Thank you, alanfox2000! I removed the registry entries you suggested and now Equalizer APO is working with UAD drivers.

[None]

@Kaz
Delete every REG_MULTI_SZ entry for GUID {d04e05a6-594b-4fb6-a80d-01af5eed7d1d}:

-->

[None]

Here is a simpler solution that will automatically delete the corresponding registry entries.

• Create a batch file with this code and execute it:

set guid="reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio /s /f 1 /e | findstr Render | findstr /V Properties"
for /f %%i in ('%guid%') do set path=%%i
set name=delete_multi_sz.reg
echo Windows Registry Editor Version 5.00 > %name%
echo [%path%\FxProperties] >> %name%
echo "{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},13"=- >> %name%
echo "{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},14"=- >> %name%
echo "{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},15"=- >> %name%
echo "{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},19"=- >> %name%
echo "{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},20"=- >> %name%

• Then run the resulting file "delete_multi_sz.reg" in the same directory and reboot.

[Igor Baryshev]

It might be easy, but definitely not simple.
Using just FX Configurator works really well.

[Jan Machovec]

Simply press Ctrl+F to look for you adapter in the "Render" root (just check adapter's name in the status volume bar or else), open FXProperties and delete "MULTI" keys starting with "d04e05a6".

No need to do anything more fancy...

[None]

What do you think is more pleasant to fix this issue after a driver update.
Running a script that take less than a second or examine the registry for some annoying GUID strings?