Why New Project Folder Doubles?

[sjoens]

For each project I create folders within folders so each one has their own Audio Folder.

Project path: E:\My1stsong\My1stsong1
                                                              \My1stsong2
                                                              \My1stsong3, etc.

When I create a new folder for My1stsong4, Cakewalk wants to create 2 folders instead of one:  E:\My1stsong\My1stsong4\My1stsong4  and I have to delete the 2nd entry.

Is there a way to avoid this?

[David Baay]

Either don't create a new folder for each version or create the top-level folder outside of Sonar using Windows Explorer before you save the first version and navigate up that folder level when saving a new version. I generally take the first appraoch and just Save As new versions with a new file name. That way, the different versions can share some audio files that are common to all versions and also reference newly recorded/bounced files that are unique to a particular version, but all saved in a common Audio folder.

But I do have higher level folders that  contain, for example, all projects recorded with a particular audio-MIDI interface setup or all Improvisations started in 2025, all Bug Demo projects, all Test projects, etc.

Edited March 17 by David Baay

[sjoens]

I save-as to subfolders because sometimes I end up with 20 or more versions and it can get messy otherwise.  Someday I'll clear out the abandoned ones. 

[David Baay]

The downside if that approach is that you can end up with lots of redundant copies of .wav files that are carried forward with each version. To me, that's messier than having 20 .CWP files (that can be easily sorted by Last Modified date) in a common project folder, referencing a common audio folder. 

[sjoens]

It's a tradeoff.  Space isn't a concern for me and audio changes with each new version so locating a specific wav can be tedious when there's a hundred wavs to weed thru.

And redundant versions are eventually deleted.