Does Cubase 15 allow using "Backup project" before first save?

So I’m on 14 and they still haven’t fixed so you can do “backup project” without first saving your project and that’s.. I don’t understand it.

I have for a decade or more (I think) started working on a sketch and if its worth saving I do a “backup project” to where I want to save so all files and future recorded files end up where I want them. Now I have to save twice and also while in the middle of doing a job I’m not confident I can clear out the first save location and just delete because you know - safety first.

STEINBERG - FIX. And if it’s working as it used to in 15, I’ll upgrade immediately.

3 Likes

Hi,

No, it’s still not possible in Cubase 15.

Well.. that’s a shame. I honestly don’t understand why they changed that function. Nothing is added functionality-wise, all they’ve done is “grey out” the option until the file is saved. So strange.

This is really a thing for me too.

Glad someone posted here.

1 Like

As it currently stands, Backup Project is just a variation of Save As… that only works on saved projects and copies the contents of the project instead of just creating a new file linked to the files of the old file. It’s up there with the other Save As… option: Save New Version.

The difference to (Prepare Archive +) Save As is that the new project will also have a new project folder. That is quite a significant difference.

1 Like

How is that different than saving the project with a new name on a different folder, then copying the content over?

If you make an audio recording, where will the file end up?

Probably in the Audio folder where you first started the project. The problem here is the fact Backup requires saving a project prior created duplicated content. You now have the project you were forced to save and clean and the backed up project. Sure, you could create a new folder for each project, but then the folder the project sits in won’t be renamed when you save the project. And if it did, that also defeats the purpose of Backup Project.

Plus you can’t prepare archive without saving either.

…which will become a mess pretty fast as some of your files are in one location but your recordings are in a different location.
And there you have the difference between manually changing things and using Backup Project. Which was your question, wasn’t it?

1 Like

And that’s not much different than the amount of duplicates you end up with because Backup Project requires a saved file to exist before it can work if you use one single folder for everything. If you use a single folder for every project, then you end with multiple Untitled folders you have to clean up afterwards.

@evilace I totally agree with you on this subject. I have voiced similar concerns:

I still don’t understand what is so hard about saving a project before backing up. Let alone backing up a project that only exists in RAM.

That it was ever possible was a bug that got fixed. A rep from Steinberg has said as much on this forum. So far as Steinberg is concerned there is nothing to fix, in this regard.

I think we all go through this process and want it to be as smooth as possible.

But I don’t understand what is being proposed that would improve the process. Two things need to be specified: The name of the project and the location of the project files. I do the first with a Save and the second with a Backup Project.

What exactly is being proposed that would improve on that?

What I understand is,

You start a new project by selecting default location with nothing in mind particularly and start creating.

You like what you do and now you want to save it with all data to a new location, so you do not pollute the dafult location. SInce Backup Project does not work without saving first, you need to save it to default location and than you can select a new location by Backup Project, and afterwards you need to clean up the default location. So it is an issue if you are using the default location.

For example in Logic, if you start a new project it automatically uses default location (temporarily). At first save, it asks you where and what to include and after you save you continue from the new location and all temp data at default location is erased.

1 Like

Thanks. Is that’s what’s being proposed here? To have Cubase treat the first save the same way as Logic?

That is what I understand. Have the back up option before save, so a location can be selected, the project data is updated with the new location and the default location stays intact by auto removing all the temp files.

I see. Personally, I prefer saving before backup. That way I can save it to work on it later before committing to putting it somewhere more permanent.

Is automatically removing the temporary project important? That seems a little OCD :grinning_face: .

The one advantage IMHO to the way Logic works is that I don’t have to remove the temporary project from the recent files list like I do in Cubase (with a right click in the Hub).

Half the time I use Backup Project, what I actually want to do is relocate my project.
A simple “Move Project” function would be very welcome.

4 Likes

Backing up a project that only exists in RAM? I have no idea what you’re talking about, if you like the way it works - all power to you.