I have various VST3s in the usual Windows folder. When I install any new VST3s, they are detected automatically. I installed three new plugins by the same vendor (exponential audio). Two of them work fine. One will not appear, even if I re-scan VST3s or remove all VST3s and rescan. The .dll is there. I re-installed the plugin. Nothing.... No solution.
That particular plugin (Phoenix Verb) shows up fine in two other DAWs in the same machine.
Why just that one plugin? Let me know if you know a solution.
W11.5 Pro bug: Does not register a particular plugin
-
- KVRist
- 447 posts since 17 Dec, 2004 from Istanbul
Windows 11/Linux Manjaro KDE + Waveform 11.
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
Normally first time a new plugin is scanned, it will either show up as scanned or failed as it APPEARED to be a valid file but failed compatability testing?
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRian
- 766 posts since 25 Jul, 2010 from Northern Ireland
I had a similar situation yesterday, tho I'm on Waveform-12 and I haven't reported it yet as I was unsure what caused it.
I'm running on Linux but it could effect all OS.
My trouble was with tracktion's F'em vst3/i , It was picked up on opening Waveform but failed the scan, so I did the usual delete from the list and manually rescan and still no dice.
Whether my next steps were coincidence or not they worked and the VST3 version is now working happily.
(1) Delete the plugin from the list .
(2) Now drag the actual vst3 file directly onto the plugin list ( nothing seemed to happen at this point )
(3) Now scan ONLY the VST3 plugins.
If you are lucky it will be working ......
I'm running on Linux but it could effect all OS.
My trouble was with tracktion's F'em vst3/i , It was picked up on opening Waveform but failed the scan, so I did the usual delete from the list and manually rescan and still no dice.
Whether my next steps were coincidence or not they worked and the VST3 version is now working happily.
(1) Delete the plugin from the list .
(2) Now drag the actual vst3 file directly onto the plugin list ( nothing seemed to happen at this point )
(3) Now scan ONLY the VST3 plugins.
If you are lucky it will be working ......
-
- KVRist
- Topic Starter
- 447 posts since 17 Dec, 2004 from Istanbul
Yes, I've been using this DAW since T2 and it's always been like you said, but for this case, it does not show as failed either. It behaves as if the .dll is not even there.Peter Widdicombe wrote: Sat Apr 02, 2022 6:22 pm Normally first time a new plugin is scanned, it will either show up as scanned or failed as it APPEARED to be a valid file but failed compatability testing?
Windows 11/Linux Manjaro KDE + Waveform 11.
-
- KVRist
- 401 posts since 10 Dec, 2002
I can see PhoenixVerb in W12. Even its VST3 version!!! 
Have you tried to "Remove any plugins whose files no longer exist" under the Settings -> Plugins -> Scanning for Plugins? And then perform the scan again. I have to do this from time to time when I upgrade certain plugins for example.
Have you tried to "Remove any plugins whose files no longer exist" under the Settings -> Plugins -> Scanning for Plugins? And then perform the scan again. I have to do this from time to time when I upgrade certain plugins for example.Waveform 12 Pro, Cubase Pro 13, Windows 11, i7-13700H
-
- KVRist
- 46 posts since 30 Jul, 2018 from USA
TBProAudio's ISOL8 gave me trouble a few days ago, with the VST2 version not appearing. Turns out the plugin was disabled in the Waveform.settings file (found in Tracktion/Waveform appdata folder). Changing the disabled="1" to disabled="0" made the plugin appear, and function, however in Waveform 11.5 the multi-outs weren't correct. Win some, lose some I guess.