Freeze Routing Folder & Contents

[Cayce]

I'm working on a fairly complex arrangement that has several routing folders with many member tracks, and occasionally another nested folder. I'm getting CPU overloads and would like to freeze some of these routing folders that aren't being worked on at the moment. What's the most efficient way to go about that? I know the routing folder is pretty much just an aux track, but is there a way to freeze that folder and all its members at once?

Another question would be, if I set the folder and all its contents to "inactive", does that exempt it from CPU drainage?

Thanks.

[albee1952]

Originally Posted by Cayce

Another question would be, if I set the folder and all its contents to "inactive", does that exempt it from CPU drainage?

Thanks.

Anything that is inactive(tracks, or plugins) will/should use zero system resources. Personally, I would lean more to freezing track, but leave the folder tracks alone. Having said that, I would also be careful with track freeze and keep things frozen ONLY as long as the files stay on your computer. If the session is to be opened on another system, unfreeze everything before the move. Just to be totally on the safe side, I would save a copy of the session(with media/audio files), just in case(you'll never regret doing this, but you might regret not doing it). My preference would be to commit whenever possible, over the freeze option

[s.d. finley]

I will also suggest Commit over Freeze. You can commit the bus that all the tracks are routed too. In the Commit dialogue box check hide and make inactive to the original tracks and bus. You can reactivate them later to edit if needed.

[Cayce]

Thanks to everyone for all of this. Great suggestions, and helped me avoid those pesky "CPU" alerts.

[Cayce]

Thanks, Albee... always good to get your input... I've put all these suggestions to use, running a lot more smoothly now... liking the "Commit" suggestion a lot.

[albee1952]

Cool! Curious as to what is more popular; Commit the entire track(with or without automation), or Commit Up To This Plugin. I tend to commit up to certain plugins(about 98% of the time) for mixing. Archiving can be a different animal