Hello,
I have a big problem.
Since yesterday, all my Waves plugin are acting weird.
When I insert, for example, a Kramer Pie Compressor, the knobs and plug’s GUI start blinking randomly, sounds is ok, but eventually, when I dismiss the plugin, Cubase crashes and closes. I don’t get any error message.
If I don’t touch anything on the plugin, it crashes later during the session.
But nothing happens when I use other plugins than Waves. (which is a problem, since I’m using only Waves plugins :)…)
I use Cubase LE AI Elements 8 on Windows 10. Everything is legit, no crack at all.
Never had a bug before.
Now, the ONLY change that I made on my configuration before this problem is that I installed Ableton Live Trial on the PC.
Tested it for a few hours. Since then, Waves plugins make Cubase crash…
Tried to uninstall Ableton but it didn’t solve the problem.
PS : this computer has no internet connexion, no viruses, I don’t use it to browse the internet, etc. it gets connected only when I have to install a plugin, then disconnected.
Can someone help me with that please ?
Thank you very much.
Hi @julienbrasart,
some Installers overwrite/update shared DLLs in common windows directories.
So the first thing I would try is to re-install the Waves plugins.
Regards
Thanks! And I did - without any success. THEN!!! at some cost I upgraded my version 9.2 to the current one - and the L3 did work for a moment or so. After a total shutdown and restart of the computer the problem was back.
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.
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.
It sounds like graphics drivers, you might need to use the NVIDIA control panel to adjust performance settings for Cubase (which will also apply to any plugins that have been loaded, and the Waves plugins all use OpenGL and so depend on these settings).
The most critical one I’ve found is that if vsync is enabled the plugins can get very upset - they don’t like being frozen while they wait for the next screen update. Forcing it to be disabled helped me a lot (not with Cubase specifically, but I doubt that makes a huge difference unless Cubase is specifically trying to control the graphics).
But you’ll find plenty of other settings in the NVIDIA control panel for Cubase, so if you haven’t heard from tech support yet then try making changes and seeing if it helps.
