spankenstein
New member
So I've done both ways: One song per project or one big ole project.
I like the one big project because I generally do quick demo type stuff and the bands want a uniform sound throughout so I get the basic setup during mixdown and just do the small tweaks from there. Problem I run into is the projects get huge and slow to load and I can't make bundle files (gives an out of space error even though there is plenty of space).
The song per project is obviously going to load faster and I can easily back up with bundle files but it's a pain to mix one song, save all the effects presets, write down the levels, open the next one, insert everythign, set the levels, etc....
What do you all do or am I missing something that makes the song per project work better like "take all of these settings and put them on this one" Not in the sense of a template, after that point.
I like the one big project because I generally do quick demo type stuff and the bands want a uniform sound throughout so I get the basic setup during mixdown and just do the small tweaks from there. Problem I run into is the projects get huge and slow to load and I can't make bundle files (gives an out of space error even though there is plenty of space).
The song per project is obviously going to load faster and I can easily back up with bundle files but it's a pain to mix one song, save all the effects presets, write down the levels, open the next one, insert everythign, set the levels, etc....
What do you all do or am I missing something that makes the song per project work better like "take all of these settings and put them on this one" Not in the sense of a template, after that point.