Any way to freeze a 'Buss track'?

If not this would be an awesome feature for CPU usage!

With my limping logics, if the freeze would just freeze the bus (= create an audio track containing all the audio pointed to that bus), it would not save a lot of CPU, if you don't archive the source tracks. So what you're actually asking, is the same as Batch Freeze, that would freeze the source tracks (still sending them to the bus) in one go (which may take a long time).

I just read that one of the forumites has developed a batch freeze function for SONAR. Now I don't remember the name, nor do I know how well it works.

Actually, a bus track does not contain any data, so it only uses the resources needed to run the VST:s in its bin.

Found the thread:
http://forum.cakewalk.com...21&mpage=1#2466548

Being able to freeze busses would be a godsend for me, with my underpowered computer. The heaviest plugins tend to be on busses. 

Other DAWs can do it, because they make no distinction between tracks and busses. Putting that feature into SONAR would probably require some pretty substantial changes to the basic architecture. (Followed by the inevitable rash of bugs that follows a major under-the-hood change. Worse, they might end up X1-ifying busses and actually make them less flexible.) 

You can kludge the equivalent to a frozen bus by bouncing to an intermediary track. It's not nearly as convenient, but if you've hit a roadblock because your computer has just run out of steam on a large project, it may be the only option.

Freeze the tracks, then go the effects bin on the bus and turn off or bypass the bin leaving the plug-ins intact. You'll have the frozen tracks with the fx and no CPU usage. When you're ready to mix, unfreeze the tracks and enable the fx again.

But how do other DAWs do it? Do they simply freeze the source tracks of the bus, and if so, wouldn't the batch freeze function do practically the same? Creating one new audio track and shutting of the bus FX doesn't sound like a lot CPU cycles saved.

Another option might be to simply export that single bus as a WAV and import it as a track, then freeze the original tracks and bypass the bus FX bin.
That would keep everything as you want to hear it (with all FX), but you'd still have the original pieces for when it comes time to do a final, perfect, mix.

Hey OP, not sure if you are still trying to figure this out... But what I do is add a send in the bus to an AUX track, record the playback and freeze it, then mute the bus and FX bin. The AUX track would have exactly recorded what you played through, and now you won't be eating up processing power during tracking or mixing or whatever the problem is. Hope this helps!

<p>Hey OP, not sure if you are still trying to figure this out... But what I do is add a send in the bus to an AUX track, record the playback and freeze it, then mute the bus and FX bin. The AUX track would have exactly recorded what you played through, and now you won't be eating up processing power during tracking or mixing or whatever the problem is. Hope this helps!</p>

There was no such thing as an Aux track when this thread was created 

This what we use "stems" for.  Bounce the BUS to a track or tracks and then archive the input tracks to that bus