This has happened several times previously but today it’s absolutely ridiculous. I think it has something to do with saving, perhaps? Not really sure whats going on but I’ve lost quite a bit of progress even though I saved.
It usually occurs when I render-in-place but there have been a few times today where it will crash and lose data, and it doesn’t have a backup file prior to the recent crashes for whatever reason (presumably because it doesn’t save during playback and I’m basically constantly playing something.
Regarding my thoughts on the matter: as mentioned this usually occurs when I render in place, but I think it may be related to a Save command. I generally will save before or after I issue a render-in-place command and I’m thinking perhaps the program fails as I’m attempting to make more edits while it’s in the middle of saving or something? When I open the project back up, it’s reverted back to the previous save, and not any around the time of the crash.
Please find a resolution to this ASAP, and let me know if there is anything I can do to assist in resolving the issue (provide log files, etc.). This has been a frequent issue with Cubase 14 that never occurred in 13.
Windows 11 x64
i7-12700K
64gb RAM
(RTX 3070 in case GPU drivers are related)
Also before anyone asks, the crash occurred at 5:42pm, these were the latest backups at the time. The save it reverted to was about 10mins after that backup, so the backup was useless but I lost about 10 minutes of work (which at the current stage of the project is MASSIVE).
Which OS are you on?
Does it happen in other projects as well?
You are referring to the auto save function, right? How often does Cubase save your project? There are no valid backups in your auto save folder (*bak files) at all?
Why don’t you do a save and wait a few seconds until it is done. Then check whether or not it has correctly saved the previous changes (just a tiny detail would do for a test). Maybe it has nothing to do with Render. I would try to rule out these possibilities first if you think they might have to do something with the issue.
Shoot sorry, I forgot to mention OS, I’ll update OP but Windows 11 x64. I’ve only been working on the one project lately so I’m not sure if it happens elsewhere.
The autosave is set to 15mins, I just adjusted it to 5mins with 200 backup files now as this is becoming really troublesome. But it is known that Cubase does not autosave during playback. I’m not sure if it pauses the autosave timer while audio is playing back either, which is really stupid.
There are no valid backups in your auto save folder (*bak files) at all?
Not anything recent, see the screenshot of when they are actually taking place. It’s only saved 3 backup files today (I started at around 2pm).
Why don’t you do a save and wait a few seconds until it is done
I’m not sure what you are suggesting here, are you saying to just do a test? Because doing it once or twice wont cause the problem to happen. I’ve been working for 4-5 hours today and it’s only occurred twice (within 30 minutes, losing about half an hour of work).
It generally happens every day at least once, though, and about 90% of the time it’s when I execute a Render-In-Place command.
Edit:
9:04pm happened again while executing Render-In-Place. Last save was at 8:54, don’t recall if I saved again before the render (likely did as it’s generally a habit for me to press ctrl+s). Latest backup was 8:59. Can someone at Steinberg confirm whether autosave occurs during playback? As that could have crashed during an autosave?
Thanks for the feedback and sorry for your inconvinience! The Auto Save interval stops for 10 seconds if you are in playback mode and then tries again every 10 seconds. I will discuss internally if we could set this down to 1 or 2 seconds. We just don’t want to use performance while you are working on big projects.
I cannot say anything about your crashes by now, but I hope we can help you soon.
Thanks much. My projects do tend to be kinda large, if that has anything to do with it (current one is 130 in use tracks with 70-80 disabled “hidden” tracks). This one is smaller than some I’ve worked on in Cubase 13, however, which surprisingly never crashed on me.
If that autosave option can be customized I think that might be ideal.
Also I noticed there was another user complaining about a similar issue.
Let me know if there’s anything else I can provide~
Three of the crashes happened in the internal Cubase plugins, one in the module that creates the images for the audio files.
Really weird, never saw any crashes there over the last few years.
Well, let’s hope Alex has some more insight.
In the meantime it might be an idea to do a clean install of Cubase. Ie. uninstall Cubase first, then install again.
I would also run a thorough virus check on the computer over night. Probably not necessary but just in case.
In other words, resetting all my configurations and what not as well? Or can I keep my appdata folder?
Edit: I reinstalled Cubase and cleared the appdata but copied over the key configs, presets folder and a couple other files in from there as having to completely re-set cubase would take me far longer than just dealing with the crashes.
Can’t really help you there as I have no idea what is the root cause for the crashes. My thinking was to rule out any corruption of the files that caused the crashes, which you posted.
Let us know if there is any improvement.
Same as before: one crash in internal plugins, the other in the image generator.
Cubase’s internal plugins are all stored together in one big file. For me it is impossible to identify which individual plugin was last used when the crashes occured.
I hope Alex can get these reports to the attention of the apropriate people.
Until then you might be better off using Cubase 13 if you have this still installed. Yours is a most exceptional case.
Everything else I use is either 3rd party (most often) or channel strip (very rarely). I suspect it to be FX modulator as it seems to be the most finicky. However the other 4 I only started using since the Cubase 14 upgrade. Though you mentioned the “image generator” which also makes me think it might be related to FX Mod.
I’ll try replacing the above (one at a time) with 3rd party ones as well and see if that helps reduce or resolve crash frequency.
Also, is there a way for us users to open up these dump files? Might help in the future identify an issue before posting.
Hi,
if you want to read your crash files yourself
you can download WinDbg from Microsoft. It is a free tool and easy to use. There are a couple of threads on how to use it here in this forum if you should get stuck.
Good luck with your problem, seems to be a tricky one!
I’m just about done on the track I was working on so I’ve not had to do much R-I-P lately, but I haven’t had any crashes since removing FX Modulator from my project entirely. Seems my suspicions, may have been correct. I only removed that Cubase plugin from my project and no others.
I’ll update this topic again when I’m working on a new project, without using FX Mod at all.
Wanted to update this. I’m on a new project, I am completely avoiding use of the Steinberg plugins mentioned previously in this post.
I am still unfortunately getting crashes - though not as frequently as when I created this post, it is still a regular occurrence and is generally always happening after a Render-In-Place operation.
I’ve attached the last two crashes, I imagine the results are the same?
I don’t think I’m using any Cubase 14 exclusive features in this project so far, so I will try switching back to 13 and see if I have the same issues. I will update this post at a later date with my results.
Ok sounds like there’s still something remaining that I’m using, meaning it must be SuperVision, as that’s the last stock Cubase plugin I am using besides the PingPong Delay. I’ll try removing that, however if it is the cause - a fix would be very much desirable as I updated to Cubase 14 specifically for the the macro knob and SuperVision updates.
Seeing as previously you mentioned:
one in the module that creates the images for the audio files
I wonder if that means it’s the drawing of the wave files for SuperVision? Either that or it’s literally just the images for the newly rendered (R-I-P) audio file?
In any case, I’ll try removing the rest of these stock plugins and see if anything changes. Then move to Cubase 13 with everything back and see if there’s a difference (which I don’t recall crashing at all back in 13).
Two things come to my mind. One is Studio Delay was not particularly well optimised, high CPU usage for many,
But the second and most important is I have seen issues with Modulators and render in place for myself and other users. I think the Modulator system has a few flaws that need to be ironed out. If I were you I would use the regular render out box and import, maybe a touch slower but more stable until a fix.
As for your track count, sounds huge ! Curious about your mega projects
But the second and most important is I have seen issues with Modulators and render in place for myself and other users.
I haven’t used any modulators in this particular project, so it’s unlikely do be that
One is Studio Delay was not particularly well optimised, high CPU usage for many,
That would be interesting (and preferable) if this was the problem. I didn’t try removing just studio delay, so I’ll go ahead and do that before removing SuperVision as I absolutely need SuperVision
Curious about your mega projects
I make mixed-genre electronic hardcore/speedcore. Compared to people who are much better than me at the style, my track count is pretty insignificant heh. Also, Cubase counts groups and folder tracks in the track count so subtract maybe 10-20% from my numbers
