Is Cubase deleting backup files without your permission?

[alexis]

Came across this today, apparently reproducible across users: https://www.steinberg.net/forums/viewtopic.php?f=230&t=93426 .

I know we have some very competent Cubase users/superusers on this forum ... I was wondering if any of you guys have seen that behavior?

Thanks much -

[The Elf]

I've never gone through that combination, so I haven't seen it. Nasty. That one is hopefully timed for an early fix.

[alexis]

...
Open a project file that has backup files. When you are prompted "Do you want to open a backup file", select "No", and then select "Keep".

Once the project is open, change it in some way that will force the "Do you want to save the project..." dialogue.

If you select "Don't Save", Cubase will then delete all your backup files for that project ...

I think I may do that sequence of steps not infrequently: open an old project looking to copy something to bring to the current one, look around, then close it down without saving so as to not save any inadvertent changes I may have made while rooting around.

I've not noticed files gone missing, but I'll pay more attention from here on in.

[John Reid]

I am of the opinion there's nothing to be fixed here as I can't see this as a fault. If you don't save the project it's logical to assume you don't want to keep any changes you made, so why would you want to keep intermediate backups?

[alexis]

I am of the opinion there's nothing to be fixed here as I can't see this as a fault. If you don't save the project it's logical to assume you don't want to keep any changes you made, so why would you want to keep intermediate backups?

It's asking if the user wants to save *changes* to the project, not whether she wants to discard the project completely.

Given that, one of what I would imagine are many possible answers to your question is the use case I described in the post immediately above yours.

[John Reid]

I must be missing something here.

You start a project, and at some point you save it.

At some later point you start to work on it again, and one or more automatic backups are created because that's what you've got set in Preferences. You then decide not to save the project (which in my mind indicates you don't want it).

Later still, you open the project (that you didn't save) and do some stuff, and then choose not to save it again.

How on earth can it be a fault if the intermediate automated backups created in a previous session are not retained? I would regard it as thoughtful on the part of the programmers that all that rubbish was not left lying around.

[alexis]

I must be missing something here.

You start a project, and at some point you save it.

At some later point you start to work on it again, and one or more automatic backups are created because that's what you've got set in Preferences. You then decide not to save the project (which in my mind indicates you don't want it).

Later still, you open the project (that you didn't save) and do some stuff, and then choose not to save it again.

How on earth can it be a fault if the intermediate automated backups created in a previous session are not retained? I would regard it as thoughtful on the part of the programmers that all that rubbish was not left lying around.

Sorry, I must be having a brain freeze, I can't explain it any better than I did in the post above.

[Dynamic Mike]

I always save incremental .cpr files. Each has it's own individual .bak files, so there's a limit to how much work you can lose & you can always return to the start of the session. I've done this since Cubase SX, not because I'm concerned about .bak files, but because I know the heartache of a corrupted .cpr file. I'd rather lose a session than an entire project.