Just lost a bunch of work. Latest Cubase 15. Mac. Autosave interval set to 3 minutes, 100 saves. NOTHING THERE!!
Steinberg: there are very, very few things more upsetting than a sudden, poof-style crash and NO AUTOSAVES FOR THE LAST THREE DAYS for unknown reasons.
If you implement a feature like this, you’d better make damn sure it works RELIABLY.
The frustration is absolutely crushing with this program. It really is.
Oh, so come to find out, autosave doesn’t do ANYTHING if the transport is running! Well, that’s how I do most of my work! It’s electronic music and I want to stay in the groove! This is ridiculous. Absolutely absurd.
This needs to be changed, or at the very least we need to have an option to override this horrid design choice. I spent so much time carefully tweaking, zoning out into a groove. I load Unfiltered Byome and start changing presets, and POOF! There goes all my work from this morning. Very careful, painstaking compression work, mostly.
Thanks a lot, Steinberg.
So hitting ctrl-s is not a habit of yours? With all your past experience running the transport full time and not auto saving. Well live and learn.
It normally is a habit, yes. But about 30 minutes into making careful tweaks and just being pulled more and more into what I was doing, I didn’t think to.
You’re not helping, Steve.
I am trying to make the point that this is a very, very questionable design choice given there’s no option to override this behavior. There’s nothing in the Settings menu that WARNS US ABOUT THIS BEHAVIOR. It suddenly clears a lot of things up I’ve been noticing over the years, about how autosaving just feels unreliable–sometimes, but not others. I felt like I was having a good run for a while, didn’t suspect anything was going to be wrong, till it suddenly was.
This is among the things that drive me crazy about this product, beyond the general instability I’ve noted time and again on here, the performance problems, etc.
I still can’t believe changing presets on a single VST3 plugin can cause the whole DAW to instantly crash like this. Steinberg owns the framework, they should own the resilience issues, too.
There has GOT to be a way to sandbox these plugins such that they are incapable of crashing anything other than themselves.
Frustrated doesn’t even begin to describe my present state.
If you’re thinking of rubbing salt in the wound like dear Steve here, just do me a favor and kindly save it.
you need to send the crash dump to Steinberg.
I think that the audio engine would have to be rebuilt from scratch to make it a gapless audio engine, something that has been asked for many times over the years.
Experience is the name everyone gives to their mistakes.
"There has GOT to be a way to sandbox these plugins such that they are incapable of crashing anything other than themselves."
This would be great like the teleportation.
I already did, I do so reflexively. Nothing ever really seems to come of it.
The files uploaded from the safe start dialog are anonymous.
If you’re on Windows you can inspect the .dmp file yourself with WinDbg; or upload it here and someone can tell you at least what VSTi crashed the program, if the crash was indeed caused by a plugin.