Qhat year is your macbook pro? 16"? Biggger?
Hi,
This is a known issue.
Set the Preferences > General > Open Projects in Last Used View to Always, please.
Ok, will do
Thanks for your amazing and quick response, Martin, I’m loving 13!
Cheers
Julian
1 Like
I have posted a support ticket, over a week ago now, for a similar (though not, I believe, identical) situation in Nuendo 13.
Mark
running Cubase 11 and 13 here … 13 crashes quite a bit for me too
Hi,
Please attach the *.ips/dmp file(s).
I’m also getting lots of shut donws (especially closing edit window or new eq popup window on mixer) but it changes… 
Here Im uploading some of hte crash reports
Mac osx sonoma, mac studio m1 ultra
Cubase 13-2023-12-09-220326.ips (487.3 KB)
Cubase 13-2023-12-09-191718.ips (519.9 KB)
Cubase 13-2023-12-05-225424.ips (481.3 KB)
Cubase 13-2023-12-05-151159.ips (411.4 KB)
Hi,
Reported to Steinberg.
What do you mean by Edit Window, please?
I had today 3 crashs.
sometimes it happens during change of a VST instrument in the rack.
And I had 2 crashs, where obviously access to the filesystem of the computer happened. One time during loading a single sample in NI Battery, and today during closing of the Stradivari violin in NI Kontakt.
I am using a complete new machine with an i7-14700K processor.
Hi,
Please attach the *.ips/dmp file(s).
pls see private message.
Today I have created official support request.
Hi,
If you want to get a quick feedback, it’s faster to post the crash files here.
But an official support ticket is also good, of course.
Hi,
You can prevent some crashes by the Preferences setting: General > Open Projects in Last Used View to Always.
2 Likes
Mine crashes too! Every second time I’m exporting audio. And it hangs while recording. And Groove Agent 5 is messed up: the preset list is FUBAR, and just now the sound disappeared! My pianotrack works (Halion), but I can barely hear the drums.
Hi,
Make sure, you have the latest 13.0.20 installed, please. And attach the *.ips/dmp file(s), please.
You’re approving it far too early, Martin. Full stop: Cubase 13 is simply not ready. It’s not a finished piece of software. I have had so many sudden freezes, crashes where the software just literally disappears suddenly with no warning and no crash dump created, and random CPU spikes when literally nothing is happening that I can’t continue to use it. My computer is quite high end and recent, too.
This should’ve never made it out of beta and those responsible for greenlighting it should be updating their LinkedIn.
3 Likes
Hi,
I’m sorry for your bad experience. But this kind of message doesn’t help to improve Cubase.
Obviously, this is not the case for all users. There must be something specific at your system. To be able to investigate, we would need more useful informations.
1 Like
hey there
Cubase 13 has just died on me. Up until now i’ve been producing fine on it - with a lot of different, sizeable projects. None of those projects work anymore - they will load, and play, but 10-15 seconds after loading, my speakers make a long stuttery noise (the sound of the audio, being paused and looped very fast) and it shuts down, without an error message.
I do not even need to play a project, cubase will just crash.
I can’t get into any of my projects. I’ve tried a system restore to 2 days ago - i’ve not installed any other plugins, nothing has changed. It looks like Cubase did autoupdate and I also installed the new download assistant / taped vibes - but thats gone now. Either way, it could be since that, I do not know
I have just fully uninstalled it and trying a reinstall.
DMP files are 200 mb each, i’m putting them up onto We transfer. Event logs show:
Faulting application name: Cubase13.exe, version: 13.0.10.123, time stamp: 0x65253e3a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process ID: 0x0x1548
Faulting application start time: 0x0x1DA3473EA0160D5
Faulting application path: C:\Program Files\Steinberg\Cubase 13\Cubase13.exe
Faulting module path: unknown
Report ID: 17dc7cb7-1f54-40ab-9305-609616e94fc5
Faulting package full name:
Faulting package-relative application ID:
HELP!!!
DMP - https : // we. tl/t-2gIFd7Pfpz
1 Like
Martin - I respectfully disagree. This has gone on long enough and you all need to get the message that we are fed up. I have been dutifully sending Steinberg every crash dump it offers to send. I’ve lost count, and that’s not even counting the ones where Cubase just disappears and creates no crash dump.
You all need to seriously reconsider your CI/CD system and your testing/QA methodology. Period.
We’re in this continual cycle of major releases that just stall out after several maintenance updates that never address important bugs only to be greeted with a NEW major release that’s absolutely chock full of them, and then the vicious cycle repeats.
You need to insulate Cubase from third party plugins’ ability to take the whole system down. This should have been a focus long ago.
You need to come up with ways to ensure that the system it’s running on cannot run any routine at higher priority than Cubase’s audio engine, even if that means lobbying PC software and hardware companies as part of an industry-wide consortium that e.g. Yamaha helps drive.
It’s just getting too damned frustrating to try and make music with a lot of these DAWs now. Ableton seems to be the least trouble recently, but it’s not nearly as robust as Cubase. I’d be sad to leave. But I’m going to have to if this pattern continues, and I’m sure many others are feeling much the same way.
Look in the mirror, all of you, and consider what your quality bar really is and has been. Come up with ways to improve it, because it’s clearly not enough or we wouldn’t be having these discussions again and again and all the damage control you have to do as a result of them. If leadership is pushing you to get a major release out the door that has an unreasonable amount of major changes to be rock solid, band together and push back.
Let my griping and that of many, many others on here serve as corroboration to them that you’ve really got a problem you need to address as a company.
I just can’t justify spending money on a product this expensive that has this many issues. It causes so much more stress than it’s worth, and I have other options. Loyalty can’t last forever.
11 Likes
Hi,
That’s great, thank you for that. In this case, Steinberg knows about your crashes, and the developers can fix it (if the crash is in Cubase).
Unfortunately, you don’t get any feedback. So if the crash is in a 3rd party plug-in (or component), you don’t get the information, so you cannot act (to notify the 3rd party). If you would share the crash dump files here, we can help you with this.
I’m here to help you, I don’t force you to do anything. It’s up to you.