I have all the latest updates installed. This is my second pc running Windows 10 Pro 22H2. See screenshot. I can keep pressing OK over and over for hours and yet nothing happens. I have reinstalled Waves. Deleted the cache folder. Reinstalled Wavelab Pro 12. Nothing makes any difference! They all come up in Cubase 14 Pro but not Wavelab Pro 12! Even older Waves plugins like X-Crackle don’t show in Wavelab! The WaveShell wrapper may be the problem but how do you get round this?
In the end I have no choice other than to Skip and therefore not all plugins show up.
On my Windows computer when I am trying to install a new plugin this comes up every 10 seconds. I am busily trying to type in the serial number to authorize the plugin and it keeps interrupting me. Is there a way to either turn it off OR extend the time to 30 to 60 seconds???
The wait time is already 30 seconds and cannot be changed.
I did and it wiped out the rest of my Waves plugins
Lots of Waves plugins if they show up at all in WaveLab Pro just don’t load - the Abbey Road plugins for starters and the One Knob Series. I would like to blame my second, older pc but the thing is they work in Cubase Pro 14 so I just don’t get it!
Loads fine in Cubase Pro 14 on the same PC. Could it be that Wavelab Pro 12 is not fully compatible with Waves 15.5?
Are you using the VST-3 version of the Waves plugin?
Are you using the mono/stereo version of their plugin on a mono/stereo file/tracks?
When WaveLab show a message such as “A serious error has occurred inside the plug-in REDD37-51”, this is another name to say that a crash has occurs inside the plugin (and not in WaveLab).
It crashes whether I use mono or stereo versions of the plug in
Could you use a previous version of the Waves plugins with WaveLab?
Are you using the plugins in the montage or the Master Section?
@Tech-dance it must be something with your system as some of the ones you mentioned work perfectly well in my system.
I can’t try all that you mentioned because i don’t have them all but X-Crackle and the Abbey Road reverbs do work here.
Wavelab 12.0.51 + Waves VST3 Waveshells 15.0 and 15.5
Windows 10
No problems at all while scanning either.
1 Like
I’m actually giving it a go. I’ve uninstalled all the Waves plugins and am installing v14 from an offline installer. Master section at this point PG
I have no doubt as there is no problem on my main PC. I’m just trying to understand what the issue is as they work fine in Cubase Pro 14. The Waves v14 plugins are having an issue in Wavelab Pro 12 now
Try running Wavelab as Administrator and rescan all plugins.
Preferably remove (or move to another folder} the plugin related file in Wavelab’s settings folder and then do a fresh scan while running as Admin.
Just an idea. Fingers crossed.
- Are you using the VST-3 version of the Waves plugin?
- Could you use a previous version of the Waves plugins with WaveLab?
All my Waves V15 plugins also work in Reason 13 on the same 2nd pc. Seems to be a Wavelab Pro 12 issue with Waves v15. I’m sorry but as it looks they load in Cubase and Reason on the same old PC but not Wavelab so what else is there to assume?.
- Are you using the VST-3 version of the Waves plugin?
- Could you use a previous version of the Waves plugins with WaveLab?
- Yes
- I could but some of them are v15 only. Do you want me to go back to v13. v14 offline installer didn’t make any difference. Wavelab Pro 12 seems very picky when it comes to Waves