I don’t want to sow despair but even the pan setting for each audio channel is a VST stock plugin. So unless you use Cubase as only a MIDI sequencer like in the early 90’s you can’t escape the stock plugins.
Hi @chaosbringer,
Many thanks for the 4 crash dump files.
Two of those crashes are directly related to SuperVision’s PhaseScope module that you are using in Envelope mode. It is not quite clear what is in the origin of the crash on your machine but some improvements should make their way in the next Cubase update and this should hopefully make things better.
Regarding the two other crash log, it is a bit more unclear to me what triggered them; out of curiosity, are your graphic drivers up-to-date ? (Both Intel and nVidia)
Thanks again for your time and sorry for the inconvenience…
1 Like
Hi JB !
I hope the much anticipated update fixes the arranger window issue of not giving priority to the right of the locator, as I highlighted in this post :
Merci !
Can’t wait for the update 
@jbrolland thanks for confirming, I had a feeling it had something to do with that due to other times the application would crash (switching between Workspace layouts which contained SuperVision would cause crashing occasionally). Nice to know that it may just be one component of it (PhaseScope). It’s not a super relevant one for me so I can just get rid of that module.
My drivers are definitely up to date. If the above doesn’t work, I’ll try forcing intel drivers/GPU in the mean time, see if that changes anything.
And thanks for informing me of the update fixes, looking forward to it!
Hi @chaosbringer,
I have identified that one of the two remaing crash is due to the Wavescope. In order to understand better your use case, would it be possible for you to tell me what is the typical value for the “Duration” parameter on the Wavescope and also what project sample rate are you using? Thanks in advance!
1 Like
@jbrolland
Here are my settings for Wavescope. I may occasionally drop the duration lower to “zoom” in on the wave as needed, but it’s generally always set to these settings.
My project sample rate is 48,000.
Thank you for taking the time to look into this.
Reading over this thread and I get this really sinking feeling… can’t explain it. The caveat that Cubase doesn’t autosave during playback… is that real? If so, it explains a lot.
I’ll not go off on another tear, but Steinberg: you all really need to get it together. You’re slipping. Big time. Stop worrying so much about new features and start worrying about stabilizing your program, about QUALITY, and keep it in an always shippable state: don’t deviate from the new quality bar once you’ve achieved it. This is really getting out-of-hand and it has forced me to switch DAWs.
I cannot take it anymore. Many seem to be in the same boat. You really need to do something, and soon.
I bought Cubase 14 as a whim. I used to be a Nuendo/Cubase user from the earliest VST and until about 15 years ago when I stopped mostly with music. Easing back into music, I have been using Logic for a while, but missed some of the “feel” of Cubase and dived into it again with Cubase 14… without really testing it a lot.
I was fully prepared that it would be some lerning curve after all these years, but unfortunately I can just report that my experience so far is that it crashes before I get to really do anything with it.
I AM on MacOS, Mac Studio M2MAx and most other applications I use for audio, like Fairligt (Mixing) and logic are stable.
I do have a bunch of AU and VST plugins, but I don’t see a pattern of even that.
In my last attempt at doing something, I went for pure midi to external audio sources, still crashing within 10 minutes.
So I am a bit baffled…
WHat to do.
I used to love Cubase and Nuendo and the way to work in them… But…
Gunleik
@gunleik
First of all, hi and welcome to the forum!
I get your frustration. However, if you are willing to accept help you found the right place in this forum.
Please, open a new thread and describe what exactly happens, upload crash files and don’t forget to mention the specs. There’s friendly expertise in buckets just around the corner 
More often than not problems get sorted out!
Yes, lets stay constructive here as we are making good progress thanks to the help of Steinberg’s developers/support.
An update on my esting so far: removal of the PhaseScope has seemingly eliminated crashing when R-I-P is performed, at least I have yet to see a crash.
I am having a new issue, however:
My audio performance will go from being great to suddenly the ASIO-Guard randomly peaks and does not drop until I reload the project. Definitely a step up from crashing since I can at least save and reload in this case. However it is quite annoying.
I’m running a MOTU M2 interface, 48,000 samples @ 512 buffer rate in this current project. Bumping the buffer rate up to 4096 helps and allows me to continue to work without having to reload the project (at least so far in my testing). I don’t think there are any downsides for me running the larger buffer as I don’t really do any live-recording (I can always turn it down when needed).
However, I wanted to point this out as well, just in case it’s related to the SuperVision problems (the reason I think it may be is that SuperVision will begin to have graphical slow-downs around when the issue occurs. Possibly before it happens, but definitely after).
I can try temporarily removing SuperVision, however removing it after the issue occurs does not resolve the issue.
If it’s not related, I can open up another topic for it at another time.
Hi,
maybe just skip Supervision for now. I guess the next update will be out any week now.
Are you still using Studio Delay or for that matter Shimmer? It has been reported that both are quite CPU consuming at times and can cause such issues.
I don’t believe so, but I’ll double check.
I’ll go ahead and pull SuperVision for now as well.
FWIW: it seems this issue might be some sort of “processing leak” problem (like a memory leak, perhaps, where usage just gets worse over time, even if no changes are made). My processor is also only running at 15% (it’s an Intel 13700k).
And let me know if any additional files may be needed. I can provide settings, etc. if it helps.
I believe I resolved this dropout issue mentioned above. It was entirely unrelated to the other problems in this thread so please disregard.
For context: it was caused by third-party plugins by AmpleSound (specifically their metal collection). Issue only started to occur when I upgraded to Cubase 14, but disabling the tracks prevents the problem so not gonna bother looking further into it right now.
I’m also going to mark jbrolland’s response regarding the PhaseScope as the solution to this thread. The removal of that seems to have stopped the super majority of issue’s I was having (as in, I haven’t had any crashes since I stopped using it, even though I am still using the rest of my SuperVision configuration).
Thanks again for the support.
1 Like