YellowDwarf
Dismember
I think this is the correct sub-forum for a question on mixing "large" songs
Hi all,
I have a couple of projects on the go in Sonar X3, pretty good DAW with an i5 and 16 gigs under Windows 10. I'm wondering how to approach an issue that I run into from time to time. This never happens with a 3 minute, simple rock song with a few audio tracks.
By the way, I've been around the block, and have read about and done all the system optimizing possible. I could move to an i7, but don't have the $$.
These are a couple of long running, complicated mixes with alot of VSTi's and effects. I'm still recording as I mix and I think that is the main problem. But I need to do so to keep the creative juices flowing, so to speak.
What happens to me in this kind of situation is that as I mix and add/edit tracks, the CPU usage grows (I have enough memory) to the point where the song ends up clicking and crackling because the CPU is overpowered by all the virtual stuff. So I bounce tracks to audio and "archive" or disable synths to get the CPU back down to <50%. It becomes a constant back and forth and screws up my creative time.
I guess I have 2 options:
1 - record and complete the song before mixing
2 - keep doing what I do now with fewer VSTs
Anybody will to share their techniques for when you get a project that's bigger than your DAW chew?
Thanks,
Timbo
Hi all,
I have a couple of projects on the go in Sonar X3, pretty good DAW with an i5 and 16 gigs under Windows 10. I'm wondering how to approach an issue that I run into from time to time. This never happens with a 3 minute, simple rock song with a few audio tracks.
By the way, I've been around the block, and have read about and done all the system optimizing possible. I could move to an i7, but don't have the $$.
These are a couple of long running, complicated mixes with alot of VSTi's and effects. I'm still recording as I mix and I think that is the main problem. But I need to do so to keep the creative juices flowing, so to speak.
What happens to me in this kind of situation is that as I mix and add/edit tracks, the CPU usage grows (I have enough memory) to the point where the song ends up clicking and crackling because the CPU is overpowered by all the virtual stuff. So I bounce tracks to audio and "archive" or disable synths to get the CPU back down to <50%. It becomes a constant back and forth and screws up my creative time.
I guess I have 2 options:
1 - record and complete the song before mixing
2 - keep doing what I do now with fewer VSTs
Anybody will to share their techniques for when you get a project that's bigger than your DAW chew?
Thanks,
Timbo