Waves Plug-ins
Latisha Gervase
Hi, Ive just recently bought a new PC and had to reinstall all my VST plugins, none of them have had any problems except for my plugins from waves central. I cant find the in my DAW (Ableton 11 Suite).
If you made sure to deactivate the licenses from the old computer and have them properly activated and installed, I suggest performing the following steps to perform a hard rescan and ensure you have the correct folders pointed out for Ableton to rescan Waves.
Hello,
This is May 2024, I downgraded my sup to essential, and when I opened my daw a couple weeks later, no waves plugin present.
I installed the new essential, no.
I tried to use my owned plugins, no
nothing is there, nothing happenes.
Waves totally disappeared, I should keep it as ultimate all the time I guess.
I come across this kind of problem periodically online. Not necessarily a Studio One problem, but it almost always seems to be PC related, though. My guess is that it has to do with all the possible options you have out there for graphics cards, where a Mac is much more limited.
At the moment because of the upgrade from V11 to V12, I cannot use Abbey Road Saturation, Reverb Plates, Chambers, CLA compressors or Studiorack. Even under V11 some of these plugins do not display in Logic Pro 10.4.8.
In Central there is a View option towards the top right. Clicking on that will allow you to specifically set an older version of the plugin. namely V10 & V11. That should allow you to install an earlier version of your plugins.
Hi am glad to give a solution that worked for me, at first i Uninstalled my waves v11, then the problem was still there, until i updated the version of my DAW - studio one (current v. 6). Guess you can revert to an older version one too but the new one worked for me so, do u.
Though its a good place to start making sure you have the most up to date version Waves that is compatible with the most up to date version of the DAW you use that is compatible with the most up to date version of your OS.
Today I removed both the VST2 Waves shell and the VST3 Waves shell to see if Cubase would still show the Waves plugs. As expected, Cubase did not show any Waves plugs once booted. All Waves plugs are grayed out in the plug-in manager. So I can conclude they are not stored in a cache in Cubase.
Removing the VST2 Waves shell and keeping VST3 Waveshell in place did not make a difference other than the file classification in Wavelab plug-ins. I also tried removing VST3 and keeping VST2 with no luck.
Yes PG, there are 2 Waves entries in the cache list. One for VST2 and the path is C:\Program Files\VSTPlugins\WaveShell1-VST 9.92_x64.dll. Here, in alphabetical order, API through GTR Stomp plug-ins show up in the cache list, and this is exactly what shows up in Wavelab. No Waves plug-ins after the letter G show up. Again, this is EXACTLY a reflection of what is listed in the Wavelab Preferences>plug-ins>waves, and of course I can load these in the master section.
The other for VST3 is at: C:\Program Files\Common Files\VST3\WaveShell1-VST3 9.92_x64.vst3. Here, only API plug-ins show up, nothing else. I would think the Waves VST3 should be an exact reflection of the VST2, but the plugin cache only shows API plugs, and nothing else. (see attachment)
Honestly, the Waves guy was exasperated after the last solid 2 hour team viewer session, however I felt his conclusion was a bit rushed. And since his help, I have read a bit more about what might be causing this.
I see scanning Waveshells 1,3 and 6. Waveshell 6 is now the only one with plugins. But out of 26 there are only 3 detected. I see them while scanning.
Wavelab 9.5 is still unusable for me with this problem. Still working with WL8.
With all the vitriol Waves is currently receiving, regardless of right or wrong, IMO they have excellent support. I must have spent several hours over several days with Waves doing Team Viewer trying to detect my issue.
So, I finally managed to find the .dll files for my Waves plug-ins (C:\Program Files (x86)\Waves\Plug-Ins V10\H-Reverb.bundle\Contents\Win64) and copied the 64-bit versions to a folder where Vegas looks for VST plug-ins. But they are not showing up in the list in Vegas.
I have just installed Logic on a new 2020 MacBook Pro (with the M1 chip) and in transferring Waves plugins from my previous MacBook (Air) they are listed in the plug manager as validated (they all have up to date licenses) but do not load in Logic. I have tried everything I can without success. Help Please!!
The waves plugins (like a lot of other manufacturers) are having trouble with Rosetta 2 on the M1 Macs so the M1 based Macs are not translating the Intel based plugs properly which is why they don't work. Waves are working on M1 native code which makes sense. If a piece of code is not working on Rosetta 2 I suppose it makes more sense to spend the time writing native code than it does to try and tweak existing code. It might take a few months though.
We, unfortunately, have a triple issue here. When an OS makes a non incremental leap, you get a fair amount of breakage. When Logic makes a .0 leap (10.6.x) you get a fair amount of new bugs. When hardware architecture changes you get at least a 6 month re-coding period. Some software won't make the transition at all!!
I had to reinstall Cakewalk, in this turn updating it to the latest version (2020.09, Build 006, 64 Bit). Now suddenly all of my Waves Plugins are shown as being missing when opening a project in which they were used. Of course they are still installed. I tried to repair them, uninstall and reinstall them, delete the Cache in Waves Central, reinstall Waves Central - nothing helped. Strangely, when I delete them and restart Cakewalk it shows the notification of plugins having been deleted. When I reinstall them, new ones are added. So Cakewalk obviously scans and finds them. But I cannot see them in the list of plugins and they are not recognized by the projects.
I wondered, if it might help to reset the Scan Options in VST Settings. But the documentation says, it will "remove all scanning records and settings from all your VST plug-ins". Does this mean, all presets in all VST plugins or the settings I made in my projects will be deleted? I wouldn't want to risk that.
I'm having problems with Waves plugins, as well. In my case, I don't think its just a Cakewalk problem as I am having the same issue with every DAW program I own. My issue, started with the need to replace my motherboard and having to reinstall the Waves plugs.
A VST reset clears and rebuids the CbB VST plug-in inventory in the registry. Any plug-in property changes made in the properties page accessed in the plug-in manager and the VST2/3 drop down in the standard header above the plug-in UI will be undone lost (ex. Configure as Synth and Configure as tempo-based effect).
Waves' copy protection is notoriously fragile, a mousetrap with a hair trigger. Repaired your motherboard? Sorry, we assume that means you are a criminal. Replaced your network adapter? No RBass for you today!
What you have to do is re-authorize your Waves plugins using their tool. I've had to do that twice in the past, but neither time did I need to open a support ticket. Actually, back then I couldn't open a support ticket because at the time they denied support to anyone not enrolled in their protection racket (aka WUP). Since then, I've managed to avoid the problem, mainly by no longer using Waves plugins.
also, if you updated to v12 recently, you'll need to install them and authorize them. simply selecting update on the Waves site will not do it and it will move your licenses back on the license cloud...
Your Waves licenses are tied to your old hardware. If you had moved your licenses back into the license cloud prior to swapping hardware, you would be good to go now with just reactivating the licenses on your new hardware.
Hey I have never had this problem before with all earlier versions of Adobe Audition. I just bought CS5.5 and tried to load the Waves plug ins I always use and they do not all load into the program. Some do load in, but unfortunatly not the ones I use most often. Any Ideas?
Sorry, we'll also need version numbers of the Waves plug-ins (e.g. 5.0, 5.5, etc), because there are a number of versions of those plugs that are (for a lack of a better word) unstable. It may be easiest to give us a screenshot of the folder you're trying to scan as that can show the full names of the .dll files.
oh just ignore that tell em, I am asking this qustion for someone else in my band and I just copied and pasted what he said and didn't read it and realize he was expecting me to put it in my own words.
Don't put any plug-in in the Audition program folder (Program Files/Audition CS5.5/Plugins). If there are WavesShells DLL's in there delete them. Do not put anything in that folder that the Adobe installer didn't put there.
If that still doesn't work, uninstall all the Waves plug-ins (and delete any WaveShell DLL's that you have moved), and then reinstall all the Waves plug-ins from their original installers and let Audition scan the default folders again.
On my system I have in Program Files a directory called "Adobe". It contains sub-folders "Audition 3", "Audition CS5.5" and "Adobe Reader". I have all my non-Adobe VSTs and VSTis in dedicated folders within that "Adobe" folder but outside the Audition folders. With this arrangement all the VSTs are seen without problem by 3.0.1 and CS5.5, though I don't have any WAVES plugs. (Clearly, I do have to tell AA where to find those "extra" plug-ins).
c80f0f1006