Waves Plugins Not Loading

[Donat Ruel]

Itested a little further. It seems like this behavior only happens the first time you load up a specific plugin during playback in a new session. When you load up the same plugin again in the same session it works like before.

One other possibility could be, if it is the first plugin load of a specific plugin in a bootup session, and your plugins are on hard disk (like mine), and the first load is slow but the second load of that specific plugin is fast, the difference between having the plugin cached in memory versus having to be read off hard disk.

I really hope that someone from Steinberg will look into this. At this time Cubase 11 is so much more stable than 12 on my system. Actually Cubase 12 is the most unstable version I had so far since 10 years.

And actually it happens for all plugins of those vendors in each session. I have to load up one instance of each plugin with the 20 sec loading time before I am able to open further instances with the normal loading time.

Yes, I also have the hangs/freezes on exit. Around 90 % I need to kill Cubase 12 with the task manager or even if it seems that it has terminated correctly, I get the crash report/save start menu when opening it the next time. I think I already send more than 100 crash dumps to Steinberg. Hopefully they end up somewhere and they fix this mess. At least I still can use Cubase 11 if I need a somewhat stable system.

I did some further testing and on my system the problem only occurs when being ONLINE. As soon as I deactivate my network card, all waves and plugin alliance plugins load as expected. So it has to have something to with phoning home for either license checkup or update check etc. besides the fact that I have both, waves and plugin alliance, licences stored locally on a flash drive.

I actually had a network drive which was not mapped when being online, because the system it was detached to was not running. As soon as I have deleted the network drive from the main system the problem was gone. Seems that Waves and PA are scanning all drives somehow when loading a plugin the first time.

In my case, there does not seem to be a difference whether I am connected to the internet or not. For example, I just tried putting my system into airplane mode, and timed a first-time Waves plugin load somewhere around 90 seconds.

I run Studio One 5.x with 100+ plugins on Windows 10. Mainly use Waves, SoundToys, Plugin Alliance, and Fab Filter EQ. Everything was working great and then one day it all stops. Loading projects that normally took seconds to load started taking 20+ minutes always getting stuck at loading the plugins. Each plugin took minutes. Waves plugins seemed to be the worst but Plugin Alliance was also slow.

Simplified explanation: Waves and other plugin manufactures use your hardware configuration to build a unique key for your computer to keep track of the license. Every time you use the plugin they take a hardware inventory to makes sure the license is on the right computer. My guess is this SD card reader issue was causing that hardware inventory process to fail. This is not an issue with the DAW so this issue/solution is not unique to Studio One and should work on other DAWs.

I should also note that if you are having the slow loading plugins issue, because of the hardware inventory process, it could be another piece of USB or other hardware and if it is not the SD reader you should systematically remove/add other hardware to see if that is the issue.

I am having the same problems with Waves plugins and multiple DAWs. I am not using an SD card. I have the latest version of Studio One and Reason and Pro Tools. FOr example RVERB took over 21 seconds to load. Waves please help us with this.

Thats a good tip that tends to help with some issues that are related to upgraded plugins trying to read older data. Additionally, a cache delete & rebuild is sometimes handy in the case of AudioUnit issues.

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.

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 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!!

Premiere loads up to the home screen just fine. When I load a project with Waves R-Compressor on a couple of tracks Premiere Pro freezes at about 75% of the load. I think it has something to do with dvaaudiofilterscan and Catalina's Privacy and Security settings.

Also, if I remove the Waves plug ins from the "Audio Plug-In manager" in Premiere Pro Preferences before loading the project with Waves plug ins, it will load with the Waves plug ins indicated as "Offline (filter...)"

Search 'dvaaudiofilterscan' using the search tool at the top of this forum and see if any of the previous conversations reveal anything useful to your situation ... also I'd start with clearing your caches, and then importing your existing project into a new Premiere Pro project.

Hi there. Just chiming in here. Running 15.4.1. on a windows machine. I run a Focusrite Scarlett 8i6 audio interface.

I've experienced this problem over and over again. I'm not sure if the problem lies in a particular Waves plugin(s) or not. Waves are specific on their website that some of their plugins are not confirmed compatible with newer versions of Premiere (yet?). I'm starting to believe that could be a blanket Waves issue.

I've tested a few plugins on footage to see if I could "break" my session file. It seems like the larger the session file, the more prone to error it will be. But a few things seem to smarten it up.

1) Shut down Premiere, go to Waves Central, head to settings, and perform the "repair" function.

2) While that's happening, open Premiere, clear your cache. Then head to preferences and double check your plugins in the Audio ---> Audio Plug-in Manager. I had a pile of UAD plugins still installed that I don't use that were still active. Might not be rooted to the problem, but cutting the fat seemed like a fine idea.

3) Now try to boot up the problematic session file. If it still doesn't open, restart Premiere, build new session file, import "corrupt" session file into the new one. Select all of the clips that have the Waves plugins on them, and perform the mass "remove attibutes" function to only the audio plugins. Save and close your session file. Restart Premiere. Now try to open the new session file.

Good luck.

Good luck!

3a8082e126