VST3 future support or workaround?

Peter Verbeek — Tue, 19 May 2026 13:13:45 -0000

Unfortunately the developer isn't very active. He only responds on a few posts and tickets per year. I guess the solution of the VST 2 host (loading VST 3's) is one to try.

VST3 future support or workaround?

Thibault Barthelet — Tue, 19 May 2026 10:51:46 -0000

A lot of bots are spamming AI generated messages, which doesn't help the cause. If you're the one doing that, please stop.

That said, yes, I should be able to load VST3 plugins without workarounds or compromises! Please add this to the roadmap!

Equalizer not opening on windows 11, Need help.

Jayden Cameron — Fri, 15 May 2026 02:30:13 -0000

Hi Peter,

Following up on your analysis about DeviceSelector reading devices from the registry instead of the Windows API. I've spent several hours debugging this with detailed registry analysis and can share everything I found.

System:

Equalizer APO 1.4.2, installed at C:\EQ
Windows 11 Pro 10.0.26200 (x64)
Target device: HyperX QuadCast S (capture)

The crash:
Both Editor.exe and DeviceSelector.exe crash on startup with Access Violation (0xC0000005). The crash is inside the executables themselves at consistent offsets — Editor.exe always at 0x856b3, DeviceSelector.exe always at 0x26d34. Benchmark.exe launches fine.

What I tried (none fixed the crash):

Created qt.conf for the Qt platform plugin (fixes Benchmark.exe, but Editor/DeviceSelector still crash)
Removed all 26 orphaned Child APO entries from HKLM\SOFTWARE\EqualizerAPO\Child APOs — none matched any of the 75 current MMDevice GUIDs
Found and restored 9 devices that still had EQ APO's CLSID ({62DC1A93-AE24-464C-A43E-452F824C4250}) in their FxProperties from a previous installation — replaced with original system CLSIDs
DisableProtectedAudioDG = 1 was set and rebooted
Verified the Start Menu folder exists (your fix app #4 confirmed it does)
Ran your fix app #2 — removed all Configuration Editor registry keys
Ran your fix app #1 — deleted windowState key
Verified 0 EQ APO GUID references remain anywhere in the MMDevices registry
Confirmed the crash happens with or without config.txt present

The device situation:
My system has 75 MMDevice entries (39 capture, 36 render). Your scan tool lists all 75 without any issues. Many are ghost/phantom devices with non-standard DeviceState values:

5x "Internal AUX Jack" (NVIDIA) — state 0x31000004
8x Realtek surround endpoints (Front, Rear, Center, Side, Subwoofer, color-coded jacks) — state 0x10000004
4x "Digital Audio (HDMI)" — state 0x21000004
Duplicates of Speakers, AORUS FI25F, NVIDIA Output, Microphone entries
Devices from occasionally-connected hardware: DualSense controller, Oculus VR, OsmoAction5pro camera

Your scan tool reads all 75 fine. Editor.exe and DeviceSelector.exe crash before even displaying a window. The crash offset never changes regardless of what registry fixes I apply.

I've been dealing with this issue since 2024 and haven't been able to get the Configuration Editor or Device Selector working at all in that time. I really need help getting this resolved.

I have a full registry backup and can provide whatever additional data would help. Happy to test a debug build or try anything else you suggest.

Thanks for your time.

FabFilter plugins break 30 days after activation/license

Alex — Wed, 13 May 2026 14:59:59 -0000

I tried to use this *.bat file, but it didn't solve the problem with the plugin.

FabFilter plugins break 30 days after activation/license

Peter Verbeek — Wed, 13 May 2026 08:02:55 -0000

As the developer of the Peace equalizer I don't need and use any VST plugins so unfortunately I only know about the GVST plugins. Perhaps I integrate these into Peace as they are free to use.

FabFilter plugins break 30 days after activation/license

Alex — Wed, 13 May 2026 07:49:59 -0000

For example, what free VST plugins can replace the functionality of Pro Q4?

FabFilter plugins break 30 days after activation/license

Peter Verbeek — Wed, 13 May 2026 07:46:15 -0000

That's easy explainable. Any Audio Processing Object (APO = sound effect/enhancement) like Equalizer APO is running in the Windows audio service. This service doesn't have much access to your computer. This is how it should be as it's a security measure. However, for finding a license by a plugin running in Equalizer APO this presents a problem. Usually the Windows audio service only has excess to some user folders so this could be a good location for a license amongst other files also needed by the plugin.

Knowing above free (no license required) VST plugins could be the better option.

FabFilter plugins break 30 days after activation/license

Alex — Wed, 13 May 2026 06:31:50 -0000

Hello everyone! It's still unclear: if the issue is with the FabFilter Pro-Q 3/Q 4 license, then why isn't this problem with this plugin present in the foobar2000 player or Adobe Audition? After all, the plugin never stops working there, and there are no issues with it. Why is the FabFilter Pro-Q 4 plugin unstable only in Equalizer APO? How can this be explained?

FabFilter plugins break 30 days after activation/license

Alex — Wed, 13 May 2026 06:31:48 -0000

VST3 future support or workaround?

Robin Holland — Sat, 09 May 2026 08:45:11 -0000

Given that many contemporary plugins are moving away from VST2, supporting VST3 would undoubtedly be a major step. It would therefore be much simpler to have native compatibility or a more seamless substitute for savihost3x64. Since seamless audio management significantly improves workflow, it could be prudent to pursue a closer connection with tools like Equalizer APO if the main issues are routing and device switching. It reminds me a little bit of how apps evolve over time to support contemporary formats, similar to how platforms mentioned on websites like rbtv777 adapt to new streaming standards to stay relevant. Hopefully, genuine VST3 compatibility or at the very least a cleaner bridge solution will be available soon.

Recent posts to General Discussion

VST3 future support or workaround?

VST3 future support or workaround?

Equalizer not opening on windows 11, Need help.

FabFilter plugins break 30 days after activation/license

FabFilter plugins break 30 days after activation/license

FabFilter plugins break 30 days after activation/license

FabFilter plugins break 30 days after activation/license

FabFilter plugins break 30 days after activation/license

FabFilter plugins break 30 days after activation/license

VST3 future support or workaround?