Waves Plugins License Problem
Thomas Merino
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.
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 had this problem,The issue is caused (for me anyway) with a Waves plugin in the C:\Program Files\Common Files\VST3 folder. If you have Waves installed there should be around 5 x plugins. Rename the WaveShell1-VST3 10.0_x64.vst to .bak or delete it completely.
It turned out the issue was the Waves driver detection part locked up Cubase on loading when it tried to generate the licence key. I had the licence installed on a studio laptop I sometimes use and transferring it over to my main PC sorted the problem completely - Cubase would run even with the .vst file present and rebuild the V10.0 file without causing the lockout.
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.
one of my collabs is on logic 10.7.4, and says she's having no issues running waves v13. obvious question, but have you rebooted? you could move the AU cache file to the desktop, reopen logic, rebuild the cache, see if that helps...
Well folks.... after loading 10.6.3 and going through the process of rescanning my plugins, I came to the realization that the problem all along was that I had not properly activated the trial plugin licenses.
Are you still running things in 32-bit?? As support for that was deprecated a little while back by both Apple and most major developers including Waves. The other thing to look out for is moving their plugins from the default install locations as that can break interdependencies, leading to buggy behaviour or plugins not working at all.
Another thing you can do is try the AUReg app inside the Waves plugins folder within Applications. Some times Logic won't see then until you run that.Inside Waves Central's Settings tab there are a few options you may want to have a look at too, including Fix Permissions and Ownership. Dodgy permissions can also cause behaviour like this. Just make sure you have the latest version of C
I just recently started using the waves plugins in the audition software. My system requirements are adequate for both the host and the plugins as well as all components being up to date. When I begin to apply the effects in the effects rack it only takes two/three effects to slow down and virtually stifle playback (jittery, clipping, sloowwww, etc.). If I delete the effects, everything simply regenerates itself and playback is fine again. If I render the mixdown, playback is fine so it seems like a processing/soundcard issue when trying to process my effects racks?? Doesn't make sense that I usually show 10 GB of RAM available for audition and the file size is a nominal 350 kb, even with waves effects applied. When using the built in Audition effect, I don't run into any playback issues. So I'm hoping that there is some setting tinkering I can finagle through Audition.
My audio hardware preferences have three different device classes MME, ASIO, WASAPI. I typically use MME but have had occasional success tinkering with the ASIO settings, but before long any additional effect continue to bog down playback. Not really sure of the differences/benefits of any of these settings as I'm a novice with digital recording + mixing.
If I render the mixdown, playback is fine so it seems like a processing/soundcard issue when trying to process my effects racks?? Doesn't make sense that I usually show 10 GB of RAM available for audition and the file size is a nominal 350 kb, even with waves effects applied. When using the built in Audition effect, I don't run into any playback issues. So I'm hoping that there is some setting tinkering I can finagle through Audition.
Well, you've answered your own question here; this is exactly the reason that rendering is there. Many plugins are far less economical when it comes to processing efficiency than Audition's effects are (although you are likely to run into similar issues with Full Reverb), and it doesn't take many instances of them to slow everything down a lot.
This has nothing to do with your sound device, although having latency set that low is going to increase the chances of stuttering playback, as this makes the disk buffer the smallest it can be. Playback of tracks is direct from your HD into Audition, and if you have a lot of external effects, then Audition has to act as a 'clearing house' for them, which is why the processing slows down quite a bit. Audition's effects are certainly reasonably efficient, but many people have observed that with too many of them applied, the same thing can happen. There is no problem with rendering tracks - if you want to change anything, you just un-render them, change it and re-apply it. All it's doing is pre-processing what you've applied so that it doesn't use any processing power concurrently with playback, giving everything else a fighting chance.
Just as information there is a difference in Audition between 'render' as in doing a Mixdown of the session and Pre-render that can be done as a temporary render of a Track's contents with the effects applied. So try Pre-rendering the difficult tracks using the little lightening icon at the top right of the Effects Rack in each Track's header.
4a15465005