Waves All Plugins Bundle V9 R15 Windows Setup Free
Harcourt Ordonez
After delete the Waves server and restart my PC, i have the same problem. The plugins from waves load for so much time. Some times it will be good and sometimes it load and load and load.
I work with Sequoia 15 and Cubase 11 - the same problem.
Started with the Diamond bundle on an XP system.
Worked great for 7 years.
I did not keep a current WUP, we decided that the benefits were minimal.
PC blew up had to rebuild with Win-7.
Which meant we had to upgrade Nuendo and all plugins.
We paid a minimal fee (a few hundred dollars) to get a current WUP
which allowed us to upgrade from Waves V5 to V9.
What's your guy's experience with waves plugins? My expectation is that I will be able to use these on multiple computers and multiple reinstalls of windows. (I've been known to reinstall windows when things get clunky)
Hi,
Thanks for the answer. I managed to solve the problem by uninstalling Waves Central and all plugins and then installing everything again. I then followed the procedure at -to-find-your-plugins-in-a-waves-host-application.
This procedure was suggested by the Waves support which actually does not support Ardour officially (unfortunately).
Franco
@mortytemps Sorry. Just saw this. Did you make sure that you uninstall the latest versions of the Waves plugins? I've noticed that after 9.6, they start exhibiting this behavior. That being said, some of waves newer plugins do not go back that far. So I have to uninstall everything, pick and choose all that I can from 9.6 like how described in the link below, and then install the newer versions of the plugins that are not that old and deal with the issues. :P It kind of sucks.
Yet I have a big problem scanning my VST. The scan hangs up while attempting to scan the MONO version of the STUDIORACK plugin. I think this is preventing me to register my DIAMOND bundle. (none of the plugins are avail as of now to my DAW)
Logical, in a way, but I am kind of surprised by this (not having the Diamond bundle avail as "native" to Sonar's media browser). Makes me wonder how to collaborate with a colleague that has a couple of waves plugin but is not SG ready yet... To investigate...
Waves bundles like Diamond and Mercury, etc are a great way to save money purchasing multiple plugins at once. Through the years the included bundle of plugins packages change. Some get dropped, others get added, and as long as you continue to pay for update support everything gets updated and improved to the current latest release version.
Well.. another update, now for no obvious reason all my waves plugins are now showing up in Sonar's browser... I'll obviously have to find which folder I am scanning that are causing theses duplicates... But at least I can see and use them.
I bought the Behringer X32 mixer during lockdown and treated myself to the Waves Audio card and waves software bundle and I find Komplete Kontrol HATES WAVES and hangs on numerous Waves plugins. I have to end task Komplete Kontrol and end task the Scanapp and remove the plugin bundle folder from program files x64\waves directory cos I need it to complete a plug in scan preferably sometime today not next week. It hasn't crashed it just hangs for hours and the Komplete app my vst2/3 folders are all on M2/SSD drives so speed it not an issue !!! After removing the waves plugin it hangs on waves shell obviously cos I removed the dll plug in folder as above??
A note on Waves. They are re-tards! Sure there are a few nice plugins but if I had my $1k to spend again I would not buy Waves personally. Their installer has a fixed install location at C:\Program Files\VSTPlugins so if you have a custom location you have to copy these to your actual path and every update you need to remember to recopy these. If you do not, this can cause issues every time you launch a program. Also, keep in mind with Waves they use a "WaveShell" container that the scan has to interrogate and pull all the plugins out of it. Depending on your bundle of plugins this can sometimes take up to 5+ minutes but should only need to be done initially.
Version 11 is the newest version of Waves plugins. By updating to V11, you can benefit from future-proofing your sessions, ensure continued compatibility with the latest DAWs and operating systems (including macOS 10.15 Catalina), enjoy plugin performance improvement and full technical support, receive new plugins added to premium bundles, and more.
Also included are newly designed versions of the classic Waves Renaissance bundle, featuring freshly-designed interfaces with 3 skin choices (Light, Dark, and Legacy), real-time frequency analyzer added to the Renaissance Equalizer and Renaissance Channel plugins, a complete rehaul of the Renaissance Channel user interface for more intuitive usage of the channel strip plugin, and 700+ new presets by leading artists. Furthermore, Waves V11 includes NKS support added to 43 Waves plugins, for compatibility with Native Instruments hardware.
A: my studio setup is more software then analog as of right now but in terms of completing my job that is no bother. I mix out of krk rokit 7 with krk subwoofer. interface is common but effective 18i20 third generation. my lap trop is the newest mack book pro with apple's new advanced m1 chip. I have almost every daw for file sharing purposes. I have all ua plugins, all waves plugins, Antares vocal plugins, and specialize in logic but can also mix in protools if necessary to the consumer
Using CW 2022.02. I've installed correctly, it would appear, the new plugin noise reduction plugin from Waves... Clarity Vx, but using the CW Plugin Scan, I was not seeing the Clarity Vx plugin loadingI get the Cakewalk VST Scan box crash with the message "Cakewalk VST Scan has stopped working correctly. Windows will close the program...". The Scanner stopped at the file "Clarity Vx MONO" which would be the plugin I'm looking to load in. This is a Vst3 plugin and is in the Waves v13 series. It's a 64bit plugin, and Waves loads these plugins into the Program Files (x86) folder. I've tried reloading using the Waves Central installer twice and even ordered a demo of another v13 product, whic loaded in CW successfully as part of the same install instance. I've done some troubleshooting and have filed a support ticket with Waves this weekend, so will update once I get a reply.
In the "Waves CR8 Sampler" thread from Feb 20 2002, several suggestions were made about other Vst3 files that CW had issues loading via the Plugin Scanner. Although I will wait a response from Waves before doing some of the suggested options which involve moving and deleting Waves files with users having mixed results, I'm posting this as an alert in case there is a problem with the Cakewalk Plugin Scanner/Loader which was suggested in that previous thread might be an issue since several other non-Waves products also encountered difficulties loading Vst3 plugins.
UPDATE: I received a reply from Waves Support. Some interesting info, although I'm not going to purchase ClarityVx because I have an AMD processor pre-Ryzen9 and they are only supporting ClarityVx on the Ryzen9 chip. Here's the text...
Thank you for contacting Waves Tech Support.
Please note that Waves plugins are not yet supported on Cakewalk 2022, since it not had been tested yet.
Also, the only AMD processor that's supported for Clarity VX is Rayzen 9 only.
In the matter of files and locations - Waves do not install plugins in the form of .vst3 or .vst, but .bundle files, with the naming scheme being [PluginName].bundle.
I.e. as you've seen, Clarity VX is installed in your Plug-Ins V13 folder as Clarity VX.bundle.
The file that the host application reads when scanning is the WaveShell1-VST3 13.x_x64.vst3 (in Cakewalk's case). That is installed in C:\Program File\Common File\VST3.
I'm able to load Clarity Vx without a problem. It's possible there might be something with your local Waves install that might need to be addressed, but in general there doesn't appear to be any issues with it on our end.
@Jonathan Sasor I posted the response I received from Waves in my original post. It appears that the reson I couldn't get the ClarityVX plugin to work was because Waves state that "the only AMD processor that's supported for Clarity VX is Rayzen 9 only." and I use an AMD chip that is a pre-Ryzen9 processor, so something in the the way Waves works their plugins (they don't use Vst or Vst3 labeled plugins) their process blocked the loading possibly because it identified an incompatible processor chip.
b37509886e