Cubase 15.06 crash every time after i had close a cpr and want to start a new from template or another song.
I had to reboot only close!
But when i close cubase before and start it again a new cpr start without problem.
It seems that cubase do not unload correctly. Sometimes an error message plop of that some uad plugins couldn’t load (less dsp power, but there is only 10% in use).
So it must be a bug in the unload process.
Please fix it! This behaviour was not expected in Cubase 14
Win10 lastet version, Uad apollo twin driver and soft all latest version.
this is the message that appears when Cubase freeze. No chance after closing with taskmanager to start Cubase again. I had to reboot then it works until i will load a next new project after the first one after start.
Okay, it seems unpossible to update only the wave shell. I had to update all waveplugs but i do‘nt wanna pay a of euros because until every thing works fine exept in Cubase 15.06
In the folder there 5 different wave shell version.
If i delete one of them the Plugins are not found in cubase.
Irritated that it works flawlessly in the first opened project and not in the second one that causes the freeze exept i close cubase and start it again so it seems for me the problem is cubase with its unloading process.
So you have one project already open and try to load a second on top?
There is nothing to unload if Cubase stays open, all components stay in memory. It is probably an issue in the WaveShell process that is already loaded, not being able to handle the second program instance.
When you shutdown Cubase, start it again and it works it is definitely not the unload.
I’ve had a problem lately with some plugins (I suppose waves) freezing Cubase so that I need to restart the daw. Very irritating. Hasn’t happened in Cubase 14 I don’t think.
Interesting, I had a look at the header data in the dump and it also says Windows 10 22H2, but then there is the build number 19041 mentioned. Indeed that makes no sense, so the combination here is supported.
In that case the problem seems to be the release of WaveShell. Version 9.92 is obviously pretty old, the latest release is V16.
No idea how complicated the update is (I don’t use Waves), but that is something you should do.
WinDbg can be a bit misleading when it comes to identifying the build. The surest way to find out is to type ‘vertarget’ in the WinDbg command line. This will show you the correct information for any given dump.
