I used to do one per song. Now I do the whole project in one. once all the songs are roughed in, I resave each song under a different name, so I essentially have them split back up. Seems to work the fastest.
I used to do one per song. Now I do the whole project in one. once all the songs are roughed in, I resave each song under a different name, so I essentially have them split back up. Seems to work the fastest.
You know what, you both hit a very good point here. I do notice that on every shift to the next song I have to re-do the improvements dialed in on the previous. This could have a nice bump on the flow of things, not to mention I really like to 'mix during tracking. That alone is huge. Hmm.grooveboxTony said:Hello everyone. Glad to part of your forum.
I have been doing one session (to start) for years now and it works good. As long as everything was tracked with the same setup, you can get a good rough mix for every song.
The problem with "one session per project," though, is that if you're talking about a 3 song demo it may work pretty well, but a 74-minute 15 song project with, on average, 30 tracks a "song" is going to be a HUGE resource drain. Maybe it's harder for me since my computer is a couple years out of date, but it'd be a nightmare to try to add additional tracks, past a certain point.
And we're meaning the same set of tracks 'serial here right (not new tracks in the same time slots? Other wise I don't see why there'd be increased resources?but a 74-minute 15 song project with, on average, 30 tracks a "song" is going to be a HUGE resource drain.
Maybe this is just a knowledge gap on my part, but I always assumed that most DAW's pre-loaded all project files in RAM, and that accordingly a 74-minute track was more demanding on system resources than a 5 minute one?
If I'm dead wrong, let me know because, well, that's the sort of thing that's generally nice to know, lol.