I upgraded from Equalizer APO v1.3 to v1.4.2.
When I enable VST (Pro-Q3) then I get complete silence. I kinda need to update some state so silence seems to disappear when I toggle any other filter. The same happened to me once when I reconnected my bluetooth headphones with wire (Idk if this is related problem).
Basically, I have to tick-untick any other option to enable VST. Disabling VST also removes silence so it's definitely a problem with VST loading (or something).
Does this also happen on your speakers (as perhaps being related to Bluetooth)?
I've seen this issue pop up on this forum a few times. Unfortunately I can't remember if it was resolved and how.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hm, I don't have speakers. I have 1 BT, 1 wired and 1 BT/Wired headphone sets. I re-checked and it seems that it just happens on any device change. If I had VST enabled in config then I get silence until I re-tick any other option.
Indeed very weird. Knowing Fabfilter plugins it might be some incompatibility with the VST support of Equalizer APO. I don't know what you can do about it other than trying another EQ plugin. But first try if the wired headphones set has the same issue. It might be related to Bluetooth.
Btw. In your video I don't see a device selection command in 'bt - ugreen hp206.txt' causing the VST plugins and other commands being performed on all devices, input and output. Is this on purpose or is the device selection command for the Ugreen located in config.txt? Note that the right top device dropdown box doesn't select your device. It's only for drawing the graph.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ensured that it behaves the same on all devices I have.
And yeah, I select required devices as the first step in config. That top-right dropdown seems to work incorrectly for me: when "Default Device" is selected then some configs show nothing in analyzer at the bottom so I selected Ugreen headphones to see working config result
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Isn't this a sign of the typical "fabfilter stopped working" stuff? Maybe the 30 days passed by at the point of upgrading to 1.4.2
I would check if everything works without using fabfilter plugins.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's very strange. I definitely used fabfilter much more than 30 days and didn't have any problem with EqualizerAPO 1.3. I saw your topic but didn't think anything about it because it's already 7 months since I installed and actively used Pro-Q3 here and it suddenly broke after upgrading to latest EqualizerAPO version. Rolling back to v1.3 does not help - it's completely broken now.
Tried to load ReaPlugs equalizer and it just works (but I don't like it).
Very very strange... Seems the only workaroud is really to delete registry keys.
Last edit: Rustam 2026-08-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I upgraded from Equalizer APO v1.3 to v1.4.2.
When I enable VST (Pro-Q3) then I get complete silence. I kinda need to update some state so silence seems to disappear when I toggle any other filter. The same happened to me once when I reconnected my bluetooth headphones with wire (Idk if this is related problem).
Basically, I have to tick-untick any other option to enable VST. Disabling VST also removes silence so it's definitely a problem with VST loading (or something).
EDIT: after all checks it seems that deleting all reg keys for Fabfilter temporarily fixes the issue: https://sourceforge.net/p/equalizerapo/discussion/general/thread/3acd12f8d2/#2553
Last edit: Rustam 2026-08-16
Does this also happen on your speakers (as perhaps being related to Bluetooth)?
I've seen this issue pop up on this forum a few times. Unfortunately I can't remember if it was resolved and how.
Hm, I don't have speakers. I have 1 BT, 1 wired and 1 BT/Wired headphone sets. I re-checked and it seems that it just happens on any device change. If I had VST enabled in config then I get silence until I re-tick any other option.
Last edit: Rustam 2026-08-16
Indeed very weird. Knowing Fabfilter plugins it might be some incompatibility with the VST support of Equalizer APO. I don't know what you can do about it other than trying another EQ plugin. But first try if the wired headphones set has the same issue. It might be related to Bluetooth.
Btw. In your video I don't see a device selection command in 'bt - ugreen hp206.txt' causing the VST plugins and other commands being performed on all devices, input and output. Is this on purpose or is the device selection command for the Ugreen located in config.txt? Note that the right top device dropdown box doesn't select your device. It's only for drawing the graph.
I ensured that it behaves the same on all devices I have.
And yeah, I select required devices as the first step in config. That top-right dropdown seems to work incorrectly for me: when "Default Device" is selected then some configs show nothing in analyzer at the bottom so I selected Ugreen headphones to see working config result
So that's alright then. Nicely done.
The analyzer always needs the device selected. For starters it needs the device sample rate.
Isn't this a sign of the typical "fabfilter stopped working" stuff? Maybe the 30 days passed by at the point of upgrading to 1.4.2
I would check if everything works without using fabfilter plugins.
It's very strange. I definitely used fabfilter much more than 30 days and didn't have any problem with EqualizerAPO 1.3. I saw your topic but didn't think anything about it because it's already 7 months since I installed and actively used Pro-Q3 here and it suddenly broke after upgrading to latest EqualizerAPO version. Rolling back to v1.3 does not help - it's completely broken now.
Tried to load ReaPlugs equalizer and it just works (but I don't like it).
Very very strange... Seems the only workaroud is really to delete registry keys.
Last edit: Rustam 2026-08-16
It sure can be. If so it's the issue of the plugin not able to get to its license. The registry keys deletion is a nice bypass.
Last edit: Peter Verbeek 2026-08-16