File saving/organizing strategies

[Soundhound]

I'm wondering what criteria people use for when to do a Save As and save a new version of a project inside the existing folder, and when do you create a completely new project folder?

 

In my endless ignorance, I've been always creating new project folders whenever I do a substantial revision, eating up tons of hd space. I label these Name, then Name.1, Name.2 etc etc.

 

So, when do you create a new project folder, and when do you just create a new project file inside the existing folder?

[Scott Jackson]

when do you create a new project folder?

 

When I start a new project.

 

when do you just create a new project file inside the existing folder?

 

When I've made major changes to my project and want to back it up to that point and/or be able to revert back to that point.

[Soundhound]

Boy do I feel like a dope! (And why should this day be any different from any other? )

 

Another amazingly dumb question, if I could. If you save a new version of a project within the same folder, and you remove lots of audio files from that new project file, so that when opening it it won't take up so much ram. Are those files still available for the other versions of the project within that folder? Does the Clean Up project command remove files totally from the project folder, or just take them out of that file specifically?

[Soundhound]

oookay, let's try this dumb question

 

Is there any downside to changing the name of a Logic Project file? Now that I'm saving versions of a project within the same folder, there are times when I might want to designate what's different about it after I've been working on it. For example when I originally save a new file, it might be TitleCue.3, but when I finish I might want to make it easy to see something else particaularly distingushing about it, like TitleCue with new horn arrangement.

 

Any downside to changing project names after the fact? Or maybe there's another way to get this info easily obtainable, while keeping the name simple, with just a revision # to distinguish it?

[ski]

You can always save the new version under a new name without assets within the same project folder. That way you're only saving a new project file without also re-saving all of the associated audio files or other assets.

 

Version numbers/letters are OK, but using a descriptive filename is always better IMO.

[Soundhound]

thanks ski. hadnt thought about whether im resaving all the audio etc with every revision. I thought since it's in the same folder, it's using the same audio files, no?

 

You can always save the new version under a new name without assets within the same project folder. That way you're only saving a new project file without also re-saving all of the associated audio files or other assets.

 

Version numbers/letters are OK, but using a descriptive filename is always better IMO.

[Soundhound]

Also the other thing I'm wondering is, is it okay to just rename the file in the Finder, or do you have to do a Save As from within Logic?

[ski]

Yes, it's the same audio files if you save within the same project folder. If you save into a new project folder then bingo, you start creating multiple copies of the same audio files and you have a organizational mess on your hands.

 

Here's what I do...

 

I'll create a new project and, if I plan on recording live audio, I'll save it in a project folder with ONLY the "Include Assets" checkbox checked and no others. That creates an Audio Files folder within the project folder, which is nice. But if I don't plan to record audio, I save the project file with the Include Assets checkbox unchecked.

 

Either way, from that point on, I save my projects with Include Assets checkbox unchecked for the remainder of the project. I never, ever save EXS instruments, samples, IR responses, movies, or any other "asset" in that project folder. Those things already live on my system, so there's no need to duplicate any of that stuff in the project folder itself. What I will save in there, however, are different versions of my project, using various different names as I make progress on the cue/song/production. When I need to bounce, I click the Bounce button, manually create a "Bounces" folder, and then start the bounce.

 

This is, for me, the cleanest, simplest way to approach saving files. No duplicated files of any kind, all project files in one folder.

 

The only time I'll ever save a project with assets (such as EXS instruments, etc.) is if I have to make my project portable (i.e., take it to another studio to work on). Otherwise, I use the procedure above.

[Soundhound]

Thanks Ski, that sounds great, keeps things very organized and under control. If I could ask, do you know if it's okay to change a project file's (not project folder) name in the browser, after it's been created, or does that cause some confusion within Logic?

[ski]

I've done that, but only on Logic projects that aren't the one I'm currently working on.

 

There is a Rename function in one of the menus (I don't have Logic open right now, a rare moment for me LOL). But that aside, yes, you can rename projects in the Finder, per the above.

[Soundhound]

Perfect. Thanks again Ski, much appreciated!

[theupgrade]

With regards to organizing folders. I have recently started with hashtagging my folders. E.g

 

RockSong #Mellow #KingsofLeon #Pianosolo

 

I just put whatever comes naturally to mind. I try to keep it to max 3 #. The main purpose is to get a better overview.

 

Any feedback?