Waves plugins were fine until recently, not sure what changed but now as soon as I load any Waves plugin, Cubase 15.0.21 freezes. I’m on the canary edition of Windows and so I can’t just load a previous version of Windows unfortunately. I contacted Waves and they just said that Windows on Arm wasn’t listed as supported so nothing they could do. I’ve had them working for 18 months and now they don’t. I tried uninstalling everything Waves and reinstalling to no avail. Any help would be GREATLY appreciated!
Hi,
Attach the *.dmp file, so we can take a look, if the crash is in Cubase or in the plug-in.
- Win: %userprofile%/Documents/Steinberg/Crash Dumps
Here you go
Cubase 13.0.50 64bit 2024.11.17 16.49.42.620-freezedump.dmp (732.1 KB)
I am afraid that crash report is from 2024 and for Cubase 13.
Maybe you can find the current report?
Sorry about that, I deleted all my old crash dump files , but because Cubase just freezes and becomes unresponsive as soon as I load any waves plug-in, it never creates a Dump file
Right-click Cubase in Task Manager and create a memory dump.
Pete
Microsoft
Thanks Pete! The only problem
is it’s over 2 gb. What should I do with it?
Just to share my waves journey - after everything being nice and stable in my Cubase setup on Mac, I started getting random crashes daily for about 6 months and eventually traced it to a few waves plugins. If even one waves plugin is loaded, eventually Cubase will hang for me on Mac. This happens intermittently even if not doing anything in Cubase.
I really wanted to use those plugins but I’m afraid like many others have found, waves can be very unstable and unpredictable. I ended up spending some time trying to get a similar sound with a few stock plugins and now I’m crash free.
Thanks for this, I must say Waves plugins work fine for me on my Mac M5 (although I’ve only been using it for a month or so).
Hi,
Share it via Dropbox or similar service, please.
Cubase finally created it’s own…
Cubase 15.0.21 64bit2026.4.26 8.29.53.343.dmp (3.4 MB)
I am not saying it is Wave Shell… but it is Wave Shell.
IP_IN_PAGED_CODE:
WaveShell1_VST3_13_0_x64+10b5e4
00007ffa`adfab5e4 48018b48 ???
SYMBOL_NAME: WaveShell1_VST3_13_0_x64+10b5e4
MODULE_NAME: WaveShell1_VST3_13_0_x64
IMAGE_NAME: WaveShell1-VST3 13.0_x64.vst3
I know it’s the Waves plugins causing the crash (all other plugins are fine), I’m just wondering why so I can try and fix it.
You could send the crash report to the Waves customer service. Maybe their development team can see and fix what’s wrong.
Again, they just say “we don’t officially support WOA” and go no further.
Which is unsupported and can be unstable, and you’re using Waves plugins which Waves themselves have said are not supported on WoA, so I think the fact that they’ve worked at all so far has largely been relying on a wing and a prayer.
I guess you’re probably right, however, I’ve mixed several tunes on this snapdragon laptop and it’s amazing. It’s surprising.how many plug-ins actually do work on it. And as I said, waves were fine for several months.
I’m just wondering if anyone reading this has had any success with waves plugins on windows on arm? Of course, Cubase is and is working very well.
Hi,
Are the plug-ins officially compatible with Windows on Arm?
Send the *.DMP files to the Waves support.
No, most of them don’t have that description in their compatibility. However, they work very well.