I see.
I have never come across a PC that was too hot. If that’s the case, something is up with the machine.
Just had the exact same thing happen!
Yeah, it’s a terrible thing to happen…
Save regularly, like, every time you feel you are making good progress, I’m serious.
Also, Save as ‘Save new version’.
This is a major issue and if you don’t have a backup file you may be in trouble…
5 posts were split to a new topic: Project file corruption in a project testing Softube plugins
So I am having the same here.
I still can open a 2 days old version but I soon as I save this one to a new version, the new version can’t be opened and the “Invalid Project Files” message appear…
Open a backup file or importing track from project, doesn’t work neither.
One odd thing I have noticed is that the last version of my song, I mean the .cpr file that can be open is ±1.9Go, but I soon as I “save as” this same version with just another name, the new created .cpr file (that cannot be open) is now ± 6.9Go. What the hell !?
It seems that I am in a dead end, what can I do??
Oh man, I am really sorry you are going through this,
This situation nearly gave me a coronary, was working on a film score, under contract when that happened!!!
I am afraid that I didn’t manage to solve the issue, I opened older files (backup) and worked my way up slowly and methodically. I lost one cue but thankfully it was easy to recreate…
This bug is disgraceful IMO…no other program does this…
What Cubase version are you on?
Could this be a hardware issue?
Yes, really it is a pitty…
The worst thing is that apparently it’s not a recent bug but it’s the first time it’s happened to me. I was not aware of this until today.
I agree 100% with you, no other program does this…
After all these years, I’m thinking more and more seriously about switching to Ableton Live. At that time, I gave it a try but I didn’t liked the design and Cubase was still looking like the best choice. For more reasons than this stupid bug and with all due respect for every single person that is working behind Cubase, this is not what I believe today… And honestly, today, I could deal with design if it would be for better stability.
Off course I am pissed off right now and I might be not very objective but I feel that I would lost less time learning again with another daw than waiting for a real stability improvements. And I haven’t spoke about those endless starting/shuting down time that I have never seen with any other daws…
And I know that for some other people Cubase runs like a charm everyday but that not my case… Me and some more…
I am working with version 12.0.60 and Windows 10
I hear you, and you are not alone in this…I hear the same point of view from many users, I am on the same train of thought, but, I can’t quit Cubase.
It is imperative for my work and other DAWs are just too alien to me…
Yeah man, I feel you, I lost my $*** when I got my cues destroyed due to this bug…
Same here, my old system would have me looking at a screen forever on shutdowns and restarts.
Thankfully, I have a very powerful system now, and shutting down/restarting takes seconds, if that.
In my experience, the more I use Cubase, the more buggy it becomes, sometimes downright unusable.
I have cloned freshly installed Windows with Cubase and everything, and when things become near unbearable from bugs, I wipe my main drive and use clone/copy the installed OS on said drive. problems solved…why? No idea…
So they say…so they say…
I’m on W10 but all the complaints have put the fear of God in me and haven’t upgraded, still on 11 and so far I am working with very minimal problems.
I also feel that I am a bit stuck with Cubase because I don’t really want to start over with a new daw.
somecomposer
I have cloned freshly installed Windows with Cubase and everything, and when things become near unbearable from bugs, I wipe my main drive and use clone/copy the installed OS on said drive. problems solved…why? No idea…
That’s smart but lets be honest, you should not have to do this…
somecomposer
I’m on W10 but all the complaints have put the fear of God in me and haven’t upgraded, still on 11 and so far I am working with very minimal problems.
This is also the only DAW I know where you fear to upgrade when a new version when it’s out.
1 Like
I hear you…
It’s painless though and quite a fast process. But I do agree, it shouldn’t come to this…
I also suddenly got this error! working on a big deal project and then this happens… I am on mac os 14 and cubase 12, guess it was stupid to upgrade my os so sooon? not sure if i should use a back up (and lose 20 min work), or import tracks into new project or something else. also cubase is hanging quite a lot, which it shouldnt with a 12 core 32gb ram mac!
So sorry to hear that…
As you said, try everything first, import tracks from project. Anything you can think of.
Cubase has bugs that when an error takes hold, it corrupts your Cubase session files,.
There is no going back once an error has taken place and you clicked ‘OK’, then saved the session and moved on, it’s downhill from there.
If this didn’t happen, there is still a possibility some CB bug screwed up your session.
There is also a possibility that there is a hardware/hard disc error.
Check your disc for errors first, and perhaps your computer for anything you can think it could go wrong.
If all is good with your computer and cannot import tracks from project (or anything else other fellow users have suggested here), you may have to go through your back up, perhaps as you said, lose 20 minutes of work, which sounds painful, but, it’s a serious problem.
I don’t know much about Macs, but I would suggest reinstalling your OS from scratch. I know it sounds too much, but the only way to get my Cubase to run normally was to do just that.
My issue was so severe that I never managed to recover the sessions, but I had back-up files and managed to trace my steps, bar one session that I had to start from scratch.
I now, religiously, save as ‘Save as new’. It’s the only way to be sure.
I hope you recover your files.
Thanks so much! Yes, I tried the .baks but they were all corrupted too, so I hade to go to an older backup… Now in a new project that I made out of an older backup I get new notifications that project file is invalit. Seriously I wonder if I shoud switch daw, but I have been using Cubase for so long… It is a brand new mac so disk should be okay, and I have already also reinstalled the os and tried many things. Hopefully customer support can help! so sorry you lost your work, it is so so so painful! Composing is the hardest and most wonderful thing, and technology can be a blessing when it works and a curse when it lets you down…
1 Like
I also wrote more here and suggested Steinberg add a file with midis: sonoma, cubase 12 (and midi)
1 Like
Actually, yes, some of my back up files were also corrupted. I remember now, total nightmare…
Yeah, the older back-up is corrupted. That’s why the new project is also invalid.
I understand, your disc should be fine, I don’t think faulty RAM should cause this, only a faulty hard disc, in that, when Cubase saves a project, if a disc is faulty, it will not be correctly saved, as such , it will become an invalid project.
Changing DAW is simply not an option for me. Cubase for film scoring is just ideal, and the functions are imperative to me, plus I have been working with the program forever.
I tried Studio One and it was so alien to me, I had to abandon my efforts to see if it would be any good for what I needed to do. IDK, maybe switching might work for you, but it was not an option for me.
Thanks so much my friend, I was working on a film, under contract when that happened, I had no idea how I didn’t have a coronary, to be honest…
I doubt customer support will help you with this, I don’t think they know themselves what causes this, to be honest.
I hope things will get resolved.
1 Like
Thanks for this. I guess one thing that made it worse is that I also use Native Instruments plugins and they dont support mac os 14 yet either. So it could still be a bug but also the incompatibility doesnt help! i am testing very slowly now, trying to not provoke the system. So do you usually back up and continue in that backup, or continue in the same file and keep backup on the side? Or is save as enough? thanks again
1 Like
I hope your efforts will resolve the issue. I hear you, incompatibilities can cause all sorts of nightmares.
What you can so is save as ‘Save New Version’.
In effect, if you have a file titled ‘My Song’, the program will save it as a completely new version of the session, then the next save will be titled ‘My Song - 2’, on the next save as ‘My Song - 3’, etc. so that if anything goes wrong, you can always go back to previews versions and open a file that was hopefully saved 10 minutes ago, so that you will not loose too much of your hard work.
When you save as described above, you don’t have to close the session and then re-open it.
Also Save as New, doesn’t create .bak files the function creates a “new” Cubase project file that is a completely independent save from the ones before it.
Cubase renames the session as it is saved as a new version, and you can carry on as normal, as though as you saved the session as you normally used to do with the ‘Save’ function.
Hope this makes sense.
thanks! This i can live with (for some time!) 
1 Like
No worries, happy to help if I can. 
1 Like
Have we heard anything from anybody at steinberg about this issue ? It’s just started for me… I found 2 cprs so far that are fine on my colleagues machines but invalid on mine.