FWIW, at least on Mac, in these cases I’ve had good luck deleting the plugin-registry.txt file in the WaveLab Preferences folder.
In the case of updating existing plugins, I’ve found that this clears up certain issues better than forcing a rescan within WaveLab.
Deleting that file will of course prompt a new plug-in scan so if you do it, be prepared to wait for that but if I were in your position this is what I’d do.
Thanks for the suggestion Justin. I’ve tried this many times and am no further forward! I’m now downloading the offline installer of Waves v13 just to see if it makes any difference
No problem. So you’ve tried manually deleting that file using the Windows Explorer?
I’m on Mac and I don’t use a ton of Waves plugins but the few I use are working with WaveLab 12 and Waves v15:
When the plug in scanner had finished reading the v13 plugins I was no better off than I was when I had the v15 plugins so I’ve reverted back to the v15 ones again. They are the latest version of the plugins after all
Thanks for the tip, Justin - This resolved the issue for me.
