Why is renaming a project still such a headache?

I’m struggling with how Cubase handles (or doesn’t handle) renaming projects.

From what I can tell, you can’t simply rename a project file and its folder in Finder/Explorer without basically “breaking” the project because Cubase loses the path to the audio files. It’s a massive pain because, honestly, I usually don’t know what a song is called until I’m halfway through the session.

In Logic, you can name the session whenever you want or rename it later without everything falling apart. In Cubase, I’m stuck with a folder full of “Untitled” projects.

The only “safe” way to do it right now is using “Back up Project,” but why should I have to duplicate my entire project and all the media just to change the name? It feels like a waste of time and disk space.

I’m honestly surprised there isn’t a function for this in the MediaBay or the Pool by now. Does anyone have a better workaround for this, or are we really stuck with the “Backup” method?

Hi,

just use File / Save As

Nonetheless, if you keep on starting all new projects in the same folder the occasional Backup Project is a good idea to tidy up the mess. This way you will have a clean new folder that only contains files which actually belong to the particular project… :wink:

3 Likes

When I start a project, I name the folder by the month and year. Then once I finish the project and decide on a name, I use Backup Project to properly archive and then delete the original folder.

Maybe I do it this way because I have had issues in the past renaming folders. But to be honest I have done it this way for so long I can’t even recall why I do it. It’s just part of my workflow.

1 Like

In the Hub of C15, you can right-click the project in the Recent section and rename it:

Cubase will rename the project file accordingly, but not the folder name.

C15 can also handle renaming project files and folders in Explorer/Finder quite well. At worst (but usually not), you might get prompts about missing files.

However, the most elegant and safest is still the Backup Project method, as suggested by @reco29. :slightly_smiling_face:

1 Like

Best thing to do, as least I have found it to be, is to configure Cubase to prompt you for a folder when you start a new project!
That way, you do this early on and out of the way, and as soon as the new project loads up, save the project (File > Save) immediately, give it a title then auto-save kicks in.
The actual project file, you can rename in the file explorer easily, and open it from there and it’ll work fine (audio path links remain), but the actual project folder, you’d need to use the Backup options as you say, so yes, Steinberg should offer this option to easily rename the project folder without going through the backup process.

1 Like

I’m obviously doing something wrong because I’ve never, in decades, had this kind of issue.
The only vaguely similar issue I have is when I move audio files around. That’s the only time Cubase cannot “find it’s files”.
I keep my projects on two different physical drives, one to store and one to work with. (Plus an external backup.) Audio files are on yet another drive. I’m constantly shifting projects from one to the other, without issues, AND renaming them if I make any significant changes.
Never used Backup. Never used Archive. I mean, never.
I must be blessed.

4 Likes

I agree with OP on this feature request. I would like to see Steinberg implement a simple “Project Manager” feature in Cubase where you easily can rename, move and copy entire projects.

3 Likes

I have cubase automatically make a new folder when I make a new project.

I had no idea you can rename the .cpr like that, thanks for sharing!

About the folder, if you rename your folder from “untitled 01” to let’s say “song 01”, and then later on you make a new project that cubase automatically names the new folder to “untitled 01”, next time you open “song 01” cubase will add your project data to “untitled 01” thinking that the project directory is intact and never ask you to update the path.

Sorry if what I’m saying is over convoluted.

That’s exactly what I just did, and when I opened the untitled 01 project in the (renamed) song 01 folder, Cubase asks me:

Of course I answer with New (1), because I want to continue working on the project in the song 01 folder.

Now I exit Cubase, and check the folders: The changes (like additional audio files etc.) were correctly made in song 01.

Now I start Cubase again and select the untitled 01 project (the one in the song 01 folder) from the Recent section of the hub. The project opens without further query and works in the correct folder. :slightly_smiling_face:

As others mentioned as their workflows…..1 song in one folder, including its audio files and all the various “save as”…..which certainly makes renaming projects easy every moment via a new file save/as.

As with other people, my “save as” name always ends with typed date/time….makes things way easier for me than simply looking at datestamp of files.

Can’t remember the last time I used/needed backup as my entire folders are copied to redundant safety nvme drives for easy moving to my other computers.

“archive files” is a button I routinely click….in my head, the button label is misleading…..what it should say is …..

…“click here and I’ll let you know all is ok in the sense that no essential files I need are missing because I know you wouldn’t like that much” :slight_smile:

No, it’s not just you. Never had an issue and I’ve been using Cubase or Nuendo for at least 10 years. Don’t remember ever having an issue like this unless something died or got corrupted with a drive. But I’m a windows user.

FWIW. When I start a new song/project I use my existing project file called New Song. I fiddle around in that project till I figure out what to call the song and it’s an idea that I want explore further. At that point I create the new project in afolder with the new title, and copy over the audio and midi clips that I created to the new project. It seems to be working for me. For songs that I don’t pursue, the audio/midi clips just stay in the New Song project or I just delete them.

Backup project is your friend

2 Likes

This is an interesting thread, it got me thinking beacuse it’s not something that’s ever bothered me.

My workflow (I’m on windows) if I’m starting a new song from scratch is to create it in its own folder inside my main ‘sketches’ folder. The folder could be called just a date or a random name whatever comes to mind in that creative moment. The project is created inside that folder and I save the project with the same name.

I’ll work on that project until it gets abandoned (I try not to ever abandon a project but….it happens) or crystallises into an actual song further down the road. Once I know it’s a keeper and I have a name for it I use backup project to save it into my main projects folder, this time inside a folder with the correct name and correct name for the project. Untick ‘keep original project active’. Delete the original folder and contents from sketches and from then on I’m working on the new project with the right name etc.

This process is so simple and takes pretty much zero time. I can see it might be nice to be able to rename a project completely in the odd circumstance but generally that would probably just confuse my workflow so I think I would rarely use it. I normally want to move a project at the same time as renaming it so backup project does both of those in one go. Occasionally I will use ‘save as’ but mostly I find that more confusing because then I end up with a folder that has a different name to the project. I like to keep things organised.

If you have a different workflow though I can see why renaming an existing project completely might be useful.

2 Likes

I just rename the folder or project file in file explorer…but I’m on Windows and I have everything in the project folder, no outside files.

1 Like

Very similar experience here. When I start a new project I dont have a name yet, so it likely gets named by the date. After working on it for awhile and getting an arrangement going, I just change the name of the folder and the project file. Cubase has had no trouble opening it and finding what it needs. I’m guessing that if I ever start messing with the stuff in the Audio folder, then it will have an issue, but simply renaming the project file and folder, as long as the structure is intact, Cubase has never given me grief for doing this and just keeps working.

Where is this keep original project active?

I do the same as you do, and never over the years, have I had any issues with renaming. I write and produce 5 days a week except when out of town.

I keep 3 general folders, with lots of song projects in each folder:

  1. Ideas (hooks, beats, 4-bar measure, cool unique synth patch in the 4 bars, bass sequence etc.)

If the idea hasn’t been developed or opened within a year, I purposely re-open it and reassess. A few stay. Some get shelved. Many get deleted. It’s a total judgment thing. And since my genre is older pop, it’s certainly style/dated.

The titles are always working titles. They will probably be re-named later.

2.Developing.

Folder is moved from Ideas when I decide it’s worth completing a composition. That means full song but just the basic tracks. For myself it’s still 75% in midi realm. Only guest players, scratch vocals, or unique 1-shots are typically .wav. Major and most effects added, EQ, compression, etc. Again, if they sit here for a year, I reassess. Shelve, keep, and maybe 10% deleted. That 10% can be difficult considering you spent some time and somehow decided you were just polishing a turd with quick plugs. Maybe it should be shelved instead? But once every 5 years going through the shelved folder does it still sound like polishing a turd?

All midi, bad audio etc was kept and disabled in a Cubase track folder in the track list at the bottom of the Cubase project called Archives. Then I hide the Archives folder. This way, I can recall anything I need when I mess up. I’m going to screw up. It’s just when and how. At this stage, I also make use of Track Presets and Effect Chain Presets simply to have quick back-ups of everything.

Also, EVERYTHING is kept organized, and with exception of .vstpresets, most presets are kept inside the 3 folders stated here, and maybe additional sub-folders for further organization. That can be a struggle. For example NI Kontakt wants to force you to store the multi at their default location. If you store it in your song project file, the next time you go to store a multi with Kontakt, it reverts back to the default folder instead of where YOU want to store it. Mario says this is because of NIs presets browser which suggests NI is more focused on promoting their own features than user flexibility. To me it’s “dumbed down.” It’s not just NI. Other developers make it difficult to store stuff where you deisre, it’s just that Kontakt is so common.

I save both the developer Plug-in preset and Steinbergs .vstpresets. While .vstpresets are not stored with my project, I keep a folder for each song inside the documents folders organized. With developer updated plug-ins, and not using proper IDs, the .vstpresets system can fail down the road. Thus, 2 different methods.

Very rarely do I come up with a title. It’s still a working title. But if it’s worthy, it moves to Finalizing.

  1. Finalizing.

Folder is moved from Developing to Finalizing. Finalizing is everything that comes after Developing but before Mastering. Adjust effects, eq, compression, most everything is now .wav. A good part of the tools here are “mastering” tools, but I prefer to think of them as finalizing tools. I don’t self-master because I feel having a good set of objective experienced ears in a better listening environment is worth it. Plus, when you hear your own material hundreds of times, your hearing become adjusted to errors, and to someone else it might be very obvious.

I also add that with finalizing tools, you can go farther than many people think. Think in stages such as final (in no order) limiting/compression, tone, and imaging. Get this down, and your mastering engineer can elevate this is ways you think are not possible. Serban, while it’s somewhat a mystery, spends a lot of time with tone and imaging before sending it out.

I usually come up with a title, so therefore another re-name, but that depends on if I’m sending the demo out for further development.

With Cubase, it seems everyone works so different, so while I often rename, maybe others organize their files differently. But as @JezD says, for me it’s simple and takes very little time.

If I were new with Cubase, or cross-grading from another DAW I would probably do it the same as the OP, because it seems that is sort of the default method withing really thinking about how you are going to work. I think I get both sides. And the Cubase way is different.

Its in the window that opens up when you “Save As” IIRC.. You can either save it as a new project and keep working on the existing one, or it will save the new one, close the current one and open the newly saved version..

Explorer or Mac system?