Project v Song Workflow Question

Question

Does this sound right?
I'm recording an album. Should each song be saved as its own project? Seems logical to save one song as a project to create the folder structure, then save the rest of the songs as songs in that project.
Also, I noticed that the channel strip settings get saved in the user library on the machine. Is there an option to save them with the project so they can travel with the project when it is moved?
Please let me know what do you recommend?
My workflow:
1) I create a song from a template and save it as a project. Then I record a session into that song file, and sometimes into a 2nd or third depending on Logic's recording time/beat limit
2) I do a "save-as-song" for each song in that session, then delete all the unwanted session material/regions for that song. I save this song into the previously created project folder along side the other songs.
Any help would be greatly appreciated. Thank!
MacBook Pro 2.33 GHz Duo, 3GB Mac OS X (10.4.9)

Answer 1

I'm recording an album. Should each song be saved as
its own project? Seems logical to save one song as a
project to create the folder structure, then save the
rest of the songs as songs in that project.
It makes most sense to have one project per song for recording. Each song will likely have different tempos, maybe different time signatures, MIDI data, different audio elements (vocals, instruments) each with unique processing and levels, different virtual instruments and different DSP. Also you are limited by the number of bars in one project although there is a work-around with that limitation.
While it is possible to accomadate all of those different elements above into one project, it would be mayhem to manage it.
This is true for any DAW. Usually one session or project is created per song.
Also, I noticed that the channel strip settings get
saved in the user library on the machine. Is there
an option to save them with the project so they can
travel with the project when it is moved?
When you start up a new song it is good to chose the make project option in the template window. If you've started a song and didn't do this, it is easily done by chosing to make song into project from the pull down menu. This is in the manual - both the book and within Logic's help menu.
I create a song from a template and save it
as a project.
Perfect. This will suit your needs as above. When you get to the mixing stage you may want to save a number of versions - each under a different project name to have options/choices.
2) I do a "save-as-song" for each song in that
session, then delete all the unwanted session
material/regions for that song.
Save as song updates your project file(s) if you created a project for the song. I am a bit confused as to what you mean by session. Some people call each project a session. Again ... I would go with one song per project.
You can assemble your songs later when mastering. This will likely not be done in Logic. Maybe it will .. .either way ... one song per project.
It's a good idea to get rid of unwanted elements as you go - if you are sure you do not need them. This is good to do as you go as you may well end up with tons of projects and have to revisit them much later on to make room on your drive.
My two cents. Hope it helps/.
Dee