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.
Hi, Just saw this. I am having trouble with waves plugins in Reaper with windows 11. I saw your fix but have a question. I saw on the waves website that you cannot install your plugins more than once a year, In fact I tried directly uninstalling the plugins through maintenance on the app and the option is not there. Am I correct in assuming if I follow your fix I can then re-install the plugins?
Thanks,
Rich
This should fix the problem, personally I skipped step 5, which still works but it takes longer because Reaper is still having to struggle with the previously installed problem plugins, but it seems to figure itself out once it sees the reverted versions. Hope this helps!
I fixed my problem! For my situation all I had to do was disconnect 2 mapped drives that were no longer valid. I had to do it through CMD as administrator, even File Explorer was crashing when I tried to get the right click dialog up on win10. Now my projects are loading with no problem. I am really thankful I found this thread.
So, in windows, I suspect it triggers access to those drives, but they are offline causing a timeout waiting for the network, which pauses it. And come to think of it now I had issues in some cases when just creating a new folder, it was a long pause so this would be why.
Very helpful, amazingly fast, for a little while I thought would need new machine to run them, even though everything else was fine. Could be where we have license on external USB and does a scan for disks on system which cause the freeze. A plug can load pretty much instant now but it was excessive minute.
Thanks to you and REV for this!!! I noticed my Pro Tools sessions started taking FOREVER to load after I opened waves central and it updated itself. Came here, found your solution (HD\Library\ApplicationSupport\Waves\WavesLocalServer -Delete Folder). I just put the folder in the trash, without emptying to be safe in case something terrible happened lol, and bam, sessions loading fast again.
I had this problem with v13 plugins, and got it to go away by doing a Waves cleanup in Waves Central. After installing v14, the problem came back. Deleting the WavesLocalServer folder fixed the problem.
This problem is super annoying and it cost me lots of time on a recent project just trying to open the sessions but having to waiting over 5 minutes for them to load. The same sessions now open in less than 30 seconds. I was very surprised to see the dates on this thread. This problem has been around for over a year.
Waves plugins already leveraged a common codebase in the past. This made them easier to maintain and update while keeping the disk footprint low. It seems to me that they nearly upgraded at least part of it to run like a server, my guess is to allow for interoperability between plugins and Cosmos and possibly StudioRack with their new VST support.
EDIT: Solved this as well.
I did this legacy install a month ago on this new Windows 11 Pro computer, having used another computer earlier.
Even the at 2018 last Waves Central did not quite work, could not login.
But all has been swell until the other day, when daw starting take 20s to load first Waves plugin, or add 20s to loading any project that usually took 3s or so.
I also have the problem and tried several reinstalls.
Probably I missed something in the manual uninstall process.
Can you please share what exactly you did during uninstalling?
Which folders etc. do I have to uninstall?
Did you have to delete registry entries?
At the moment all my waves plugins are useless.
If you are still struggling to get your Waves products to load please contact directly our Tech support team who will be able to solve any Waves-related issues and hopefully save you time and trouble.
Welcome to the Waves Forum.
I think Tech Support emails might be going to your spam box or junk mail. I can confirm a reply with all the relevant information to the issue you have raised was already sent some time ago(9 May).
Please check to see if you have such mail, I have also made sure support will try and reach you again to provide all information.
Do note that AMD Ryzen 9 5900x 12 core processor is not officially supported with Waves software. and it is also worth mentioning that Smaplitude X3 was only supported with Waves V10 so if you are trying to run V14 on this system it might explain the crashing issues you mention.
So, here is the thing, since almost all the recent high quality plugins are internally oversampling anyway to 192 kHz to handle well aliasing when heavily compressing, limiting and doing saturation, as well just run the session at 192 kHz. It turns out the benefit during processing are really nice.
I will say aliasing is just another type of distortion artefact that can also prove useful at times. I find it can add a nice bite to a sound when used in moderation, kind of like hard-clipping transistor distortion int a way, but not.
In 10 years time people will be wanting to recreate the sound of aliasing just as they have other types of distortion. As usual, once you eliminate something people will desire it more. Thats been the course of music history!!
The question is why do the samples not just download and install with the plugin? I have used waves central on my Windows machine for 3 or so years now, no such issues. Now i bought a new Mac Studio to transfer my Audio production work flows to, and waves central will only install the plugins without samples. WHY! Its a brand new MAC, brand new installations of everything. I deactivated licenses from Windows machine for transfer, no change.
So maybe a better option is to copy the Waveshell vst and the Waves plugin files to the USB drive, then dump the plugins to the standard Waves plugin files folder, and the WaveShell to the host vst folder. Then run Waves Central to get the licence.
I have done multiple uninstalls and reinstalls via Waves Manager, full restarts, and still I only see two plugins in Logic in my Waves folder when inserting a plugin on a track: The free CLA echo-reverb and the Kings Microphone lol. I have used the full Abbey Road collection on my 2013 MBP 15" Retina, no issues. Easy install and authorizing process.
We are working to qualify and update our software to work there, but this may take some time and I do not have an ETA.
In the meantime, I cannot offer any troubleshooting steps or help resolve this.
Do you still own a previous Mac with Intel processor where the plugins run properly?
Heya Simon. I worked out that I needed to migrate logic and waves plugs from the intel machine to the M1, then open logic in Rosetta and validate the plugs to the M1. All present and accounted for and running very well. That will hold me over nicely until I can go native when waves is rockin the M1.
My biggest wish from Waves is for them to integrate their plugins to Console 1.
That would mean the world to me, and I guess many others as well.
I hope this is doable and can be fitted into an already busy schedule.
All the best,
During the scan for the new plugs, I got: The following plug-in caused an error during load: WaveShetll1-VST3 12.7_x64 and WaveShetll1-VST 12.7_x64. Pop up suggested I disable them so the system doesn't become unstable. Did that.
Thank you! I removed Visual C++ version 2005, because I had been reading about issues it caused. Apparently, that screwed up a bunch of things. Right at that time, I started using Bandlab Cakewalk instead of my actual Sonar Platinum, because i wanted to see if there were more features. And that began a whole rabbit hole of problems with plugins working in Sonar but not in BL.
This seems to have fixed it! Thanks so much for posting this. My own fault, but I didn't make the connection until I read this.
With the release of OSX 10.15 Catalina, Apple dropped all support for 32-bit components. Due to this, Waves V9 plugins will not work properly and need to be updated by renewing the Waves Update Plan coverage and updating the license .
I use Waves Central in Cubase 12 and it loads ok. My issue is with Kontakt 7. It freezes for up to fifteen minutes, if I leave and come back it is loaded but this kind of messes up my creative process, Komplete Kontrol does the same.
He reinstalled the app with just a few plugins and studio rack worked. He then left me with the reinstalment of the rest of the plugins and we disconnected the call as we assumed the problem was fixed.
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.
7fc3f7cf58