Waveform shows wrong version number for updated plugins

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I recently spent some time trying to understand why the installer for an updated version of my plugins wasn't installing the new version only to realise that Waveform wasn't picking up the new version number.

Consider this: Plugin Alliance released a bunch of updates to its plugins. I installed the updates to the vst3 plugins I had, and for some reason I also installed the vst2 versions, which I didn't have.

So now Waveform shows this:
Image

Notice how the vst plugins are at a higher version number than the vst3 ones? That's not true, though, as I've installed the new versions of the vst3 ones as well. In fact, if I run the validate tool on one of them, it shows the right version number:
Image

I've tried removing one of the vst3 plugins from the list, deleting the relevant file, restarting waveform and reinstalling the plugin: in this case when waveform picks up the updated plugin it shows the right version. I don't know if there's a faster way to selectively update one of those plugins without rescanning the whole list of plugins (and then again I'm not sure that would fix it).

Post

did you rescan plugins?

Post

Kott wrote: Mon Apr 05, 2021 10:54 pm did you rescan plugins?
Well, waveform did the rescan at startup when it found the updated plugins.

That aside, just forcing a rescan of the vst3s doesn't solve the issue: one has to remove them from the list first and then rescan (I tried and it works).

I believe this is a bug: Waveform detects that the plugins have changed so it should also update the version number it shows.

Post Reply

Return to “Tracktion”