Hi there people…
I wonder what happens when a project gets “corrupt”?
Does it start to take money on the side? LOL
Just had it happen here now and had to go back several versions of the song to get it working again.
That was NOT fun to say the least.
It does not happen often; maybe once in 6 months but it should NEVER happen IMO
After all it is called Cubase PRO
Sometimes one can almost “see it in advance” when the project get more and more sluggish even though you have not overloaded your cpu.
Other times you record and mix happily just to get “can not save - the project is corrupt” when you try to save.
Clearly there must be some combination of plugins, vsti’s and automation+++ causing this (and don’t look at me with an evil eye, my rig only uses legit plugins and VSTi’s)
Which brings me to my point:
In the next Cubase version I want a warning when you do something that might corrupt the project.
Something like: “you are trying to load a plugin/vsti that we know might cause the project to become unstable do you want to proceed?” or some such
Just lost hours of work and it is really irritating.
Anybody else who has encountered this?
Could this be something that Steiny should look into?
All the best, Kim