As a hint: try to find the newly installed locations of Waves VST3 DLLs.

VST2 can reside anywhere on your disks. So it must be inside the search paths of your DAW.
WAVES installs x64 Plugins into c:\Program Files\VSTPlugIns\ so you must include this location in your DAWs VST search path.

For VST3 its easier because all x64 plugins must be in only one location: c:\Program Files\Common Files\VST3\ (the same is true for VST3 x32 plugins as they always go to c:\Program Files (x86)\Common Files\VST3 only).

For Cubase (x64) I would delete all references to x32 plugin locations in the plugin manager's paths so they won't be scanned/blacklisted by Cubase again.
In a second step I would make sure that all locations where x64 plugins reside are defined in the Cubase plugin manager.

For VST3 you don't need to define a path in the plugin manager because they always (should) reside in the standard locations.

BUT as always, not all vendors copy VST3 plugins to the standard location. In this case just move them to the standard location otherwise they won't be found. (Search for VST3 plugins with explorer by using *.VST3 search phrase).

And therefore it is easier for you to use only the VST3 versions of the Waves plugins. Because you can easily find them on your hard drive this way: They always end in .VST3 (and not .DLL, like VST2 plugins).

 

Last edited: Aug 1, 2021

I tried copying the “V12 Plugins” folder and rescanned and still nothing, plus the way they are set up, data in different locations, don’t know if that will even work if they are found.
Going to reinstall the last working R2R version and see where that puts things I think.

 

Re-setting the Cubase plug-ins cache manually Print
https://acusticaudio.freshdesk.com/...re-setting-the-cubase-plug-ins-cache-manually

 

Thank you for the tip, will try that too!

 

So, yeah, somehow I ballsed up a simple install, for some reason one of the files to be removed wasn’t removed by the VR patch. Removed it, and back to enjoying all manner of Waves-y goodness. What a prize tit I am!

 

Waves kioharts izotope not working in Cubase 11 .41 pro Win 10 1904 full update
included the VST3 folder also Plug manager black listed them NOT VALID PLUGIN
whats a thief to do when you steal software then complain it does work thats me

 

Re-setting the Cubase plug-ins cache manually Print
https://acusticaudio.freshdesk.com/...re-setting-the-cubase-plug-ins-cache-manually

 

yep did that already no change they are in the plug in list as loaded but dont show in the meue but if i do a refresh instal of cubase no fixes
B23 they install so now im running B23 again on my legal ver of Cubase 11 pro 11.40 even tried JBridge as a work around

 

Humor only (do not consider this reply, and my "vote" as serious)... Second degré in French...
- Uninstall Q-Base, or,
- Uninstall Waves, or,
- Uninstall both!

Seriously: hope you'll fix this issue, I can't help you (sorry) because I don't use Cubase (I'm using REAPER 6 or Live 11 Lite - enough for my usage), and I've banned Waves company definitively!

 

Last edited: Oct 16, 2021

On Windows systems, what about the Registry key who defines path to (all common) VSTs/VSTis? (VST specification 2.4).

This key was recommended by Steinberg (on website), in case you're using another than C:\Program Files\VSTPlugIns

For 64-bit VST2, the Registry key is defined like this:

HKEY_LOCAL_MACHINE\SOFTWARE\VST
REG_SZ (string) value: VSTPluginsPath contains the full path to your custom path, for example D:\VST64

But unfortunately many installers (even 64-bit installer) doesn't care about this (useful) Registry entry.
Some DAWs (REAPER, Ableton Live) recognize it, however. Is Cubase is able to use this key? and Waves installer?

 

In reality, the normal mortal user has nothing to do with the registry.
He shouldn't change something there either, because he often causes more harm than good.

Steinberg is a separate company with its own operating system and is only liable for its own products.
Waves is an independent company and is only liable for its own products.

Steinberg invented the interface and it belongs to her, but any company can use the interface free of charge.
She can also only give recommendations.

Every manufacturer is free to design and program his products as they see fit.
With all the advantages and all the disadvantages.

 

There is something going on I even tried old er waves and older Cubase 11.30 when it last work now no waves work in cubase
im fully updated in win10 could it be a combination of thing even turned of network when install old waves central so it would not update
it worked for awhile the when i rebooted whoooose gone so imn back to my Cubase 11.40 without Waves for now