

Then, I move the old folder into the new folder, into an archive folder within a folder called "Resources" because then I know that this older file and other content (lyrics, digital recorder files, presets, Reason files, etc.) can all be easily found in that Resources folder. What I do is when saving a file such as this-a major name change or a re-orienting of the file's purpose or content-I create a new folder with the "save as" command and store that new song project parallel to the old one I'm working on.

But now such changes become a sub-activity of the file you're working on. After that, I think the file system is designed not to get overly complicated with different names attached to different generations of that file within the same folder.Īgain, just my own speculation. Perhaps a developer could chime in here įrom my own experience, I think you can rename the song file and folder only while working on the original file.
