Waveform vs VST3 plugins

[pough]

I get the feeling that this only happens for me, but I wanted to ask just in case. I'm running Waveform Pro 13.5 on Windows.

WF seems to lose VST3 plugins from time to time. Not all of them, but one or two will stop working. They show up in the plugins list. They might even validate. But when you try to add them to a track you get the dreaded yellow exclamation on the plugin icon.

Here is a recent example. I just updated OB-Xf by Surge Synth Team. It was already in the plugins list because I've been using it for a few months now. But when I tried to add it to a track, it refused to load. I tried to validate it and it validated without any problems at all. So I ran a plugin scan, which added a second entry for the same plugin. The new entry could be added to a track, but the old one still failed to load.

Even though they are the same thing. There is just the one plugin file installed on my computer.

Inspecting the knownPluginList64.settings file showed two entries for this plugin. Nothing relevant looked different to me. I inspected the Waveform.settings file and found three entries for this plugin.

I manually deleted all the extra entries in both files and now there are no problems, but this problem is a strange one. Does anyone else have similar issues?

By the way, sometimes Waveform seems to be trying to load the plugin's containing folder instead of the plugin. For some reason, the VST3 standard seems to call for the plugin and data to be in a folder with the exact same name as the plugin, including the extension. I found this out by using the "show folder containing plugin" right-click menu option in the plugins list.

[Watchful]

I once had some vanish at random... they italicize in the plugin list as if deleted, but rescanning fixed that. Haven't encountered the problem you're describing.

[edrickblade]

I get the feeling that this only happens for me, but I wanted to ask just in case. I'm running Waveform Pro 13.5 on Windows.

WF seems to lose VST3 plugins from time to time. Not all of them, but one or two will stop working. They show up in the plugins list. They might even validate. But when you try to add them to a track you get the dreaded yellow exclamation on the plugin icon.

Here is a recent example. I just updated OB-Xf by Surge Synth Team. It was already in the plugins list because I've been using it for a few months now. But when I tried to add it to a track, it refused to load. I tried to validate it and it validated without any problems at all. So I ran a plugin scan, which added a second entry for the same plugin. The new entry could be added to a track, but the old one still failed to load.

Even though they are the same thing. There is just the one plugin file installed on my computer.

Inspecting the knownPluginList64.settings file showed two entries for this plugin. Nothing relevant looked different to me. I inspected the Waveform.settings file and found three entries for this plugin.

I manually deleted all the extra entries in both files and now there are no problems, but this problem is a strange one. Does anyone else have similar issues?

By the way, sometimes Waveform seems to be trying to load the plugin's containing folder instead of the plugin. For some reason, the VST3 standard seems to call for the plugin and data to be in a folder with the exact same name as the plugin, including the extension. I found this out by using the "show folder containing plugin" right-click menu option in the plugins list.

Hi pough, make sure "Automatically check for newly added plugins" is checked in Settings > Plugins.

[XorXisT]

I think your issue is explained here:

viewtopic.php?p=9193170#p9193170

[pough]

Hi pough, make sure "Automatically check for newly added plugins" is checked in Settings > Plugins.

I appreciate the suggestion, but I should mention for anyone else coming here that this is not a solution.

I think your issue is explained here:

<span class="skimlinks-unlinked">viewtopic.php?p=9193170#p9193170</span>

I think you might be right in this case. WF also seems to get confused when a plugin developer moves their plugin from the VST3 root to the strange "pluginname.vst3\Contents\x86_64-win\" folder structure.

I'm still surprised that nobody else is experiencing this, especially since it seems to happen to me every few months or so for a few years now.