Klevgrand Brusfri VST Help Needed
A system-wide equalizer for Windows 7 / 8 / 8.1 / 10 / 11
Brought to you by:
jthedering
Menu
▾
▴
#302 Klevgrand Brusfri VST Help Needed
Hello,
I stumbled across a VST from Klevgrand called Brusfri which is a really good noise removal VST of which I'd love to use with EqualizerAPO but it fails to recognize the input.
Is this something that can be looked at and why it doesn't identify the input?
I asked them and they said they have no experience with Equalizer APO and wouldn't know how to make something like this work and to reach out to you.
Thanks.
Is it a VST 2 plugin? I think Equalizer APO can't handle VST 3 plugins.
Yes, it's a VST 2. It works, loads up, interface launches, it just doesn't recognize the microphone input when trying to process it. It works fine when adding it into OBS, or Streamlabs, etc, but will not work with EqualizerAPO.
Although I'm not sure if VST plugins can be used on mics, I think it's possible so did you insert a mic device selection command above this VST?
Yeah, correct. This is what it looks like. I have another VST from the same company working on the microphone just fine, so I'm sure it's possible, just not sure why it can't detect an input for this specific one.
As you I'm guessing it's about this Brusfri plugin. There 2 other matters I can think of. The first one, the plugin is 32 bit instead of 64 bit, well assuming you're on 64 bit Windows (10 or 11). The second is license related. This can be complicated to explain and also to solve. So here's how things work in Equalizer APO. It's audio manipulating engine (equalizerapo.dll) runs its own instance of the plugin. The plugin you interface with isn't the one that's actually doing the audio manipulation. So it may look and work fine but the instance in the audio engine may have an issue running as it can't get to the license of the plugin.
To solve the above, the first thing to do and try is to copy the plugin to c:\program files\equalizerapo\VSTPlugins. The plugin may get to the license by doing this. Unfortunately sometimes it doesn't. This is because any APO (audio process object, say sound enhancement) runs in the Windows audio service (audiodg.exe). This service has (and have to have) limited access to your computer. But this means it may not have access to the license too. More details on APO rights by Etienne Dechamps. And here are his fixes in the same chapter. Another fix is by Wealstarr on the forum of this website. He simply copied the license files to C:\Windows\ServiceProfiles\LocalService\AppData
Weirdly is that it may be better to use free VST plugins (without licenses and not in some demo mode) as this works.
I'll try these out, but I think Etienne's answer below is why it doesn't work.
What do you mean exactly by "it can't detect an input"?
If you are saying it doesn't see any audio passing through when you run it in the Editor, that's normal. The VST Instance running in the Editor doesn't actually process any signal. Another instance of the VST runs in the actual APO itself and that one will process the actual audio.
This might be the answer. It's a noise reduction VST, so it listens and evaluates and removes background noise that is registered while holding in the button and works really well, but it may not register since it's not running directly on the APO maybe?
So, I can't simply open the configurator, hold the button in and let it register since it's not actually doing anything in the configurator.
That's right. The VST running in the Editor is not actually doing anything, it's the one running in the APO that counts. Sadly, there is no way to interact with the VST instance running inside the APO - it's a "set and forget" kind of thing.