Does anyone else have this problem - renaming project?

My song writing/composing work flow often involves winding up Sonar, coming up with a riff on guitar, bass, synth etc. Working out a structure and then writing lyrics etc. I often don't have a title for the song/tune until the later stages of the project. So when I create the project in the first place I give it a date stamp as a title e.g. 20170817. Usually, when I settle on a more descriptive name I will do a save as... with the new name. I then have to dig into my project drive and find the old date stamped project directory and delete it, but that's tricky due to the number of projects in there and it's unsafe as I could potentially get the dates mixed up and delete the wrong project!
 
Is there a better method of changing a project's name with the projects directory and file reflecting the new name? Or should this be a feature request e.g. File > Change project name?

35mm
My song writing/composing work flow often involves winding up Sonar, coming up with a riff on guitar, bass, synth etc. Working out a structure and then writing lyrics etc. I often don't have a title for the song/tune until the later stages of the project. So when I create the project in the first place I give it a date stamp as a title e.g. 20170817. Usually, when I settle on a more descriptive name I will do a save as... with the new name. I then have to dig into my project drive and find the old date stamped project directory and delete it, but that's tricky due to the number of projects in there and it's unsafe as I could potentially get the dates mixed up and delete the wrong project!
 
Is there a better method of changing a project's name with the projects directory and file reflecting the new name? Or should this be a feature request e.g. File > Change project name?

This is a real issue with me. it all has to do with how Sonar saves audio wavs in a project and saving a project then say deleting or changing track audio data in the new project but you are still in the file structure of the original project so if you delete a track in say project copy 2 you also delete the wav file for the original project copy 1
 
I always create a CWB file then open it and save it as a new project before modifying anything in 2nd generation of a project.

First. Before doing anything you should have a back up copy of everything. 
 
I often re name projects. 
Using Save as and renaming a project in place in the same folder uses almost nothing in hard drive storage. 
CWP files are small. 
It just gives you the option of having multiple versions of the same song easily retrieved. 
 
If you save as to a new location and check the copy audio box then there you go. why worry about the old version? Hard drives are huge and if it bothers you just move that folder to a back up drive. I don not ever, ever delete anything I do in Sonar. 

Cactus Music
First. Before doing anything you should have a back up copy of everything. 
 
I often re name projects. 
Using Save as and renaming a project in place in the same folder uses almost nothing in hard drive storage. 
CWP files are small. 
It just gives you the option of having multiple versions of the same song easily retrieved. 
 
If you save as to a new location and check the copy audio box then there you go. why worry about the old version? Hard drives are huge and if it bothers you just move that folder to a back up drive. I don not ever, ever delete anything I do in Sonar. 

I do have backups, but auto backups will remove stuff that's been removed from the source. I normally do save as for saving versions and like you save them in the same directory with a, b, c etc added to the file name. But when you do a save as can you change the name of the project directory and save into that? I imagine that would fail. I worry about getting rid of the old named version because when I am browsing through projects in various states of complesion, I don't want a whole load of duplicates and duplicate audio taking up space. Apart from backups, I have a single directory for each project with multiple versions of the project in that along with versioning, audio, mixes and everything else related to that project.

35mm
...when I create the project in the first place I give it a date stamp as a title e.g. 20170817...
...but that's tricky due to the number of projects in there and it's unsafe as I could potentially get the dates mixed up and delete the wrong project...

 
I would add a silly random word to end of the timestamp string. This will make it easier to recognise and identify each file.

Deleting a track or audio clip won't delete the associated wave file especially if another project in that folder uses it as well.
 
I create a song folder for each song. As I make major edits I "Save-As" the song name followed by a successive number:
 
[Folder] SongByMe -
  SongByMe01.cwp
  SongByMe02.cwp
  SongByMe03.cwp
 
When I mix one down to a stereo wave to analyze, I give it that version's name and number: SongByMe03.wav. As I compare wave files I can tell which cwp was better.
 
They all share the same Audio folder too so that can get a little stuffed over time as my biggest projects have over 50 saved cwp files in it.  I don't use cwb files cause they end up confusing my file structure.

35mm

Cactus Music
First. Before doing anything you should have a back up copy of everything. 
 
I often re name projects. 
Using Save as and renaming a project in place in the same folder uses almost nothing in hard drive storage. 
CWP files are small. 
It just gives you the option of having multiple versions of the same song easily retrieved. 
 
If you save as to a new location and check the copy audio box then there you go. why worry about the old version? Hard drives are huge and if it bothers you just move that folder to a back up drive. I don not ever, ever delete anything I do in Sonar. 

I do have backups, but auto backups will remove stuff that's been removed from the source. I normally do save as for saving versions and like you save them in the same directory with a, b, c etc added to the file name. But when you do a save as can you change the name of the project directory and save into that? I imagine that would fail. I worry about getting rid of the old named version because when I am browsing through projects in various states of completion, I don't want a whole load of duplicates and duplicate audio taking up space. Apart from backups, I have a single directory for each project with multiple versions of the project in that along with versioning, audio, mixes and everything else related to that project.

Yes!
Once you've done this you can safely delete all of your old versions with impunity.
But PLEASE make sure you've got "Copy Audio With Project" checked when you do the Save As

So here's my way of dealing with this, because I have the same situation as the OP.
 
When I create a project that has no defined name as yet, I type the date followed by a string of nonsense characters. So the file name might be something like 20170818dfdsfjhdsklfhdjsfdsjkdfsiop.
 
When the song takes shape, I Save As... with the proper name. Every now and then I go to my projects folder and sort by date, then delete anything with a long and stupid name that's older than a few months.

mudgel
For those who seem to create various versions of their cwp file; Have you tried Versioning?

Yes but there is no control over the version names with the automated process. When I create a new "version" I can give it a meaningful name. Automatic versioning still serves a purpose as a safety measure.

Kalle Rantaaho

11Dreams
 
This is a real issue with me. it all has to do with how Sonar saves audio wavs in a project and saving a project then say deleting or changing track audio data in the new project but you are still in the file structure of the original project so if you delete a track in say project copy 2 you also delete the wav file for the original project copy 1
 
I always create a CWB file then open it and save it as a new project before modifying anything in 2nd generation of a project.

I don't think so (?). AFAIK deleting a track never deletes the audio from from the Audio-folder. Or do I misunderstand your message?

Yup, your right. lol It must have been human a error of some sort that drives my work flow.. :)
 
Peace!