Hello! I am on Windows 10 on a new powerful computer. Been using Waves plugs for years without problems. So - yeah… this is my first post.
Recently I have problems with my Waves 9.2 plugins. All of them are VST3 - so that should work. However - recently some plugins - especially L3 (which is the one mostly use) - also got the Gold collection and some other stuff.
I have tried several workarounds, including repair of the installs. The strange thing is that - sometimes they work just fine. The freeze appears when the plugins GUI are shown. From there it*s nothing to do other than diving into the task manager and end Cubase. Now - if - lets say it’s working one day - and I save it - the plugin will work when I return to it. BUT! That is only if I made sure the GUI doesn’t appear on reopening the project. And then - if I want to make an adjustment and open the damn plug… Cubase will freeze.
EDIT: I just did a new test. All my Waves plugins (the ones I tested) seemed to work just fine - but the L3 Multimaximizer is deffo the culprit. The L3 Ultramaximizer seemed to work just fine.
Also… I think the automaking of links in this forum (if you mention a product) is a tad odd… I got several messages that I could not put more than two links in a post… but I had not made one single link myself.
Hi @eivind,
Welcome to the Waves Forum.
Waves V9 is outdated and not supported with Cubase 14, even if it might have worked or still do partially, V9 was not tested or qualified to work properly on Cubase 14.
If you still having issues I’d suggest verifying your licenses are supported with your current setup OS and DAW, and Contact Technical Support who will gladly help out as long as your on supported setup.
I also tested with Cubase 10 which I also have on my computer - same problem.
The trouble is the V9 plugins aren’t getting maintained any more. That version was over 10 years ago. Most devs only support up to 5 years of maintenance.
So if it’s a problem you really need fixed you need to update at least that one plugin you are having problems with. The trouble is, your OS/DAW might not support it either. That’s the catch 22 many of us face time to time, sadly.
It’s also why many of us try to keep our computers and DAWs up to date to avoid facing that issue. Doing so can get quite expensive, which isn’t an option for a lot of users.
It comes down to keeping your old system, but freezing it in time and not doing any updates while everything is still working. Versus, buying a new computer every 4-5 years. It’s tough, but its a decision we all need to make unfortunately.
I have now updated to the latest versions of my Waves plugins.
Hi! I am (currently) on Windows 10 running Cubase 14 (Pro) on a new computer. 128gb RAM, expensive intel i9 processor, Nvidia-graphics, M.2’s, ordinary SSD’s and a couple of old fashioned HDs… got heaps of terrabytes available… (my main suspicions at the moment: Faulty default XML-file (that would be Cubase) or - something crashing in the graphics… thing is - if I get the L3 to work (it happens occasionally) and save the project - that project will open just fine and use the plug to what hears to be what I dialed in… now - if I then open the plug… Cubase will freeze and only show a black standard VST-plugin frame.
It’s not all bad though - normally I would use a tad of L3 when doing a mixdown export. No need to save the project (it adds heaps of latency as one probably know). In some other thread at this forum I found a workaround that so far seems to work: Start Cubase - do not open any project, but jump straight into the mixer and load L3. THEN (!) - open the project I have in mind for L3. L3 will load into that like it always used to and I can export my audio with a bit of L3-magic added.
I have written this in another (old) thread. Recon it’s best to keep it here.
Oh right… Oops!! I’ll just copy what I posted there instead…
This is the problem with Windows systems sadly, with the extra freedom you get for upgrade possibilities you get “harder to maintain” in the end.
So what I’m wondering now is whether it’s the graphics driver, whether than needs to be updated OR downgraded to an earlier version. It could also have something to do with distributable frameworks, I forget which ones.
I think at this point it is definitely better to have a chat with someone from Support. They’re generally very helpful and quick to respond.
1 Like