That is my recollection from the times when this has happened to me (e.g. after a Cubase session crash where I’ve been working on a project for a long time without saving). Mind you, this is relatively rare for me – both on the occurrence of Cubase crashes and that I work for a long time without saving (and keep in mind my autosave interval is set to 15 minutes).
My recollection here is that it gives you the choice – i.e. whether to open the CPR file or open the newest autosave, in which case it will do that with a new version number.
Is that even possible? I’ve never tried it. I was thinking you had to have a CPR file to open it directly. I have occasionally renamed a .BAK file to .CPR when I knew that a newer CPR file had some issues and wanted to revert to the most recent (but older) autosave file.
At least in my experience, this is something you’d do at the File Manager (or Finder, in your case) level, not in Cubase. So you have complete control over what you choose on this front.
Does Cubase really crash that often on your system? The last CrashDump file I have on mine is from May 20th, so over four weeks ago. Also, just looking at my current project directory, for a project I’ve been working on since May 16th, I have 194 CPR files. With a very few exceptions, they all have meaningful names. For example, the earliest with a meaningful name is “Cheyenne-03, set up Structure.cpr” – the 3 CPR files earlier than that were from different version saves, possibly related to some sort of issue where Cubase forced me to save a new version due to that issue. In general, my files for this project will have the name “Cheyenne-VersionNumber, MilestoneDescription.cpr”, with the exception of cases where I just take a copy of the project at a breaking point where there is no milestone and mix generations, where I’ll have something more like, “Cheyenne, Work Mix N.cpr” for work mixes (I’m not up to rough mixes, no less final mix candidates, for this project as yet – but maybe later tonight…). I have no problem with having loads of CPR files in my project directory. I sort the directory in descending date order in File Manager, so it’s always easy to see what is the latest version, and the meaningful names mean that, if I decide I need to import something or other from an older version, I can get a good idea of which CPR file I need to import from based on the description. But, if you’re just using generic names, like the ones you mention, I can see why they’d be useless and confusing.
Well, I do the equivalent, too – starting with work mixes, then rough mixes, then potential final mix candidates. All the other in-between names are meaningful with respect to whatever milestone made me decide to back that instance up (and I don’t need a crash to do that – it is just part of my standard workflow, owing to plenty of times where I’ve wanted to backtrack on decisions I’ve made along the way, especially with regards to things like vocal tuning where I may have introduced artifacts that can only be repaired by going back a long way in the project history, maybe even to the raw takes prior to comping).
Well, I think it does, but I’d personally advocate for using meaningful file/version names, not just numbers that won’t mean anything to you a bit down the road. Most of my song recordings take on the order of a month, so having meaningful names is critical to me for cases where I need to rescue something or other from an older instance of a project. That doesn’t happen on every project, but it does happen occasionally, and, in those cases, there is no substitute for being able to review project history to home in on where the ingredients needed to rescue a track are likely to be.