I can confirm WLE Patch V5 working flawlessy on Mojave, LPX, ProTools.
No need to use HW Keygen. Just do an uninstall of V10 from the lates Waves Central and install Abbey Road, SSL, Mercury and Piano Bundles to get every single plugin installed.

Just remember that if you're using SoundGrid you should avoid this update in order to continue using it until the new SuperRack will be released.

:::::
"Please note: V11 plugins are not supported in MultiRack, SoundGrid Studio and StudioRack. V11 plugins are fully supported in the upcoming SuperRack plugin rack and in eMotion LV1 V10"
:::::

 

Already.

 

... Win 7 and 8, according to dev specs.

 

There's this one thing I don't get with Waves plugins... like, I like the RenComp a lot. but it keeps using more CPU and generally behaving less snappy. So one has to ask oneself: is upgrading really worth it? I'm talking about 2 decades old Waves plugins, and Renaissance series has always been my favourite alongside SSL, V, and API series. These plugins have gone from using [say] 1% CPU to 3%, which is not negligible when you use dozens of them, especially when using the same computer.

So my advice is to stick to the oldest Waves bundle you can. I'm now using the latest v9 because x64 shit. V7 and V8 are only x86. V9 RenComp uses double the CPU than on my XP OS with V8, and that doesn't make me happy. V7 plugins work so much more efficient. V8 isn't bad, either.

The sound is the *same*, mind you. There are no improvements to the sound. Remember, upgrade or update is not always really an upgrade. But sometimes it's necessary.

 

Last edited: Oct 28, 2019

Its saying Win10 and above at Waves site. I'm hoping not...

 

Just to avoid confusion, my post should be read 'V11 plugins are not supported in... ... Win 7 and 8, according to dev specs'
So, we both mean the same thing.

 

Used the last v10 mac patch after using waves central online install all by selecting which ones, and waves 11 works fine so far. Same libs left in place for the sounds. Just simply deleted all the waves 10 stuff after the install.

 

Last edited: Oct 29, 2019

What in the hell is wrong with waves they released waves 11 and they still have not fixed Studio rack crash in Cubase 10 on Mac and when you call tech support they have the nerve to have an attitude and be mad because you're asking him where the hell is a fix for Studio rack it's going on a year that it has been crashing Cubase 10 since Cubase 10 has been released it doesn't crash on Windows but it's been crashing on Mac they can't fix one little plug-in I think their plugins are good as plugins but the company is be getting to be a piece of s***

 

@SineWave It really becomes a little sad when the best version of a plugin was one I had 7 years ago on old architecture

 

it was question of time

 

did someone try to make it work on Catalina ?
I'm trying to find a way to reinstall it on Catalina, nothing worked so far...

 

I think one problem with Waves plugins is that they use CPU for graphical interface instead of using GPU. That's why they are heavy on the CPU.
I hope they get some up-to-date developers to fix these

 

Last edited: Nov 4, 2019

please explain why did u update to catalina...

 

u sure with that ?

 

How did you achieve this I'm trying to install v11 on my mojave macbook pro and I can't install the v10 plugins through the new v11 waves central that I downloaded from their website. Just trying to upgrade to v11, I uninstalled all waves plugins and downloaded just the installers for v10 (mac/win) and v11 (win, cause I couldn't find it for mac) Can you shed some light please... thank you