User Ratings

★★★★★
★★★★
★★★
★★
★
2
2
0
0
1
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • 4 out of 5 stars
    I still have to load VST2s because they don’t automatically reset the adjusted levels; a nice improvement is that all the plugins are now fully visible at once, rather than just one at a time. I’m really looking forward to an update that brings stable VST3 support.
  • 4 out of 5 stars
    Very nice! I would like to see a way to resize the modules, because now they are very big and there is a lot of blank wasted space, so now I have to scroll down in my config pages a lot, whereas I previously didn't have to. Other than that, great improvement over the original EAPO!
    Reply from EqAPO64_with_VST3_support
    Posted 2026-10-13
    Hello! Please open a issue here: https://github.com/Mixomo/EqAPO64_with_VST3_support/issues You can attach screenshots of your editor.exe, so I can view the exact problem you have. Thanks!
  • 5 out of 5 stars
    Bro, please get rid of that hideous, half-page warning that pops up when a VST plugin is open—the one saying it might not work—and please add icon scaling for all resolutions, just like in standard Equalizer APO. I have a 3440x1440 monitor, but the icons look like they're sized for 1920x1080.
    Reply from EqAPO64_with_VST3_support
    Posted 2026-07-31
    Hey, thanks for your comment! I just uploaded a custom release (based on v2.0.4—Custom Release 1) to the “Files” tab, which removes the explanatory notes from the VST module and hides the side buttons under a single dropdown menu, freeing up a lot more space. As for the icons, I’ll look into that. My screen resolution is 2560 x 1440, and I haven’t had any issues, but of course, it’s not ultrawide, so I can’t test how they behave on those aspect ratios. Maybe by setting the DPI compatibility for editor.exe in the shortcut properties? In the next version, I’ll include several aesthetic options and integrated components as optional choices when running the installer, so each user can customize it to their liking and, if they wish, save space. But it’s taking me a while, and there are some issues I haven’t been able to resolve, so I don’t have a completion date yet.
  • 5 out of 5 stars
    Bro you're a life saver. tysm
    Reply from EqAPO64_with_VST3_support
    Posted 2026-05-31
    You're welcome! If you have any problems, please let me know!
  • 1 out of 5 stars
    I really wanted this to work, but this build caused major problems on my system. After installing it, Windows started throwing missing DLL errors, my date/time disappeared, SFC couldn’t fix the corruption, and DISM couldn’t repair anything. I eventually had to do a full Windows repair install just to get my PC stable again. Maybe it works on older builds, but on current Windows 11 versions it caused more damage than it solved. Definitely test this in a VM before installing on your main machine. Updated note: It’s also possible that part of the issue was my specific audio setup. I run a Presonus Revelator interface with its own custom drivers, plus multiple VB‑Audio virtual drivers (Voicemeeter, VB‑Cable, Hi‑Fi Cable). My system relies heavily on APO routing, virtual devices, and low‑latency audio paths, so it’s possible this build conflicted with one of those components. Still, the fact that it caused missing DLL errors, broken Windows services, and unrecoverable SFC/DISM corruption suggests the installer is doing something deeper than just failing to load a plugin. If you use a similar audio stack, definitely test in a VM or secondary machine first.
    Reply from EqAPO64_with_VST3_support
    Posted 2026-05-29
    OMG! I'm so sorry! I’ll definitely take your comment into account and post a warning both here and on GitHub. If I’d had even the slightest problem, there’s no way I’d share it with the community. I guess every Windows build is a different story... I also have Windows 11 (specifically 24H2 build 26100.4652) There may be issues with more recent builds...
  • Previous
  • You're on page 1
  • Next