With Cubase 13, I could start a new project by choosing “create empty” with “prompt from project location” and always the same directory for creating a new project.
Then, once the project had been created, when I wanted to save it, I would select “back up project”, create a directory and the .cpr file and audio files would all be copied into this directory.
And from time to time I deleted all the audio files in the “creation directory” to make room.
With Cubase 14, the “back up project” option is greyed out when a new project is created, which breaks my entire workflow.
Thanks Martin for answering but again no , in Cubase 13 !
With cubase 13 , it was possible to “back up project” before saving, thus creating (before any saving) a folder containing the .cpr file and the project’s audio files.
here’s why I’m asking the question here
I don’t have 13, but what the OP describes is the case with 12, and isn’t with 14.
I presume what @Martin.Jirsak has said seems the logical way to do things, so the devs have “fixed” it.
So since they “fixed” the fact that you can “back up project” before saving, it’s no longer possible to save and collect all the audio samples in a single folder (the actual project folder) ?
It is possible to “back up project” but it will be in another folder than the original one (so for the backup)…
I’m really annoyed because what I described in my first post was really important in my workflow
I am a tadbit surprised. I use the same workflow as you, yet I am not as unhappy as you are with the new limitation.
I have one folder, where I always start any project that falls in the “let’s see where this is going to take me” category. I then create a project file in that folder.
Once I am convinced that I am going to work a bit more on it I use the Backup functionality, thus creating a new, dedicated folder for the project and all its audio files.
I’m going to try this method and clean up this folder from time to time as I used to do before by deleting the audio files and I’ll do the same with the .cpr file.
Hi everyone,
Sorry for answering so late. For this maintenance-update we took a closer look on existing problems regarding the backup-project-function. We identified, that there are some ways that user can lose quite a lot of work, so we fixed this. While we fixed this bug, we noticed that backing up an unsaved project left us with problems we couldn’t circumvent with our current design of how the project is structured and recognized by Cubase.
As the first step of keeping work would be to save your project, we now enforced this, by disabling the backup-before-save all together.
This could be a case, where a lot of people built their workflow around a feature, that was never meant to be used like this. So if this is a major hinderence, we will take a look at alternative solutions. I am sorry, if this is a problem for your workflow. We only had the stability and safety of the project in mind.
This is a major hinderance, because when I go to save a file, it does not make the audio folder with it, they are now in separate places, therefore you have all created more and more steps to save a simple file. I have been using this workflow for years, made a YouTube video on it, have taught my students and now it’s all rendered useless. To bad you couldn’t have saved the function for those of us creating projects almost daily. So now, not only do I need more steps to backup a project, but I have to go in and delete any older files that were created - or… I’m all wrong (I’ve been proved wrong more times than right). Interesting that Dom Sigales and the rest of the YouTubers didn’t mention this. I may revert back to 13
Hey Virgil!
Sorry for your inconvenience. Could you clarify what you mean by “So now, not only do I need more steps to backup a project, but I have to go in and delete any older files that were created”?
The only change you have to make in your workflow is to save the project → backup project.
Technically, there should be no difference to what you did before, other than that. Even in the old version, there should be files created in your default folder. (No Projectfile maybe, but all audio-files are there anyway) On backing up, you only copy them to a new location and connecting the audio files to a new project file. You still have to delete all old files, if you don’t need them.
I see the usecase of “trying around and seeing what sticks” and then using backup-project to extract this project to another location, but the only difference in the old workflow is, that you need to save the project first. You can always use the Preparing Archive feature, as @Carvin_Man mentioned.
I will check back, if there are ressources to change this. I must say, that this change was no decision of design or user-guidance but safety and durability.
Youtubers might not have mentioned this change because, from a feature-standpoint, this is a rather small and only bug-related change. It was not meant to be kept secret in any way.
I’m also miffed that this workflow “feature” has been removed. But perhaps an even better solution is to implement a way that lets us move a project, with all its associated files, to a new folder location. I have a feeling this is what many users was after in the first place but as no such function existed, Backup Project was (mis)used as an only alternative.
Hey I was trying the new method for a bit now. I was using a temp folder to save a project before using the backup to save the project to the new folder ie backup..
The only problem now is that I get a lot of extra project names in the recent Cubase projects (as well as recently used documents in Windows 10/11).
I can delete the temp folder files easily enough, but those extra project names don’t go away..
