Why not?

yes why not :-)
 
these days you can route a bus to an aux track. record the aux track and then mute/archive the sources ... not the same but at least a work around

I suppose one issue would be any new sources being routed there after you freeze the bus. When you bounce and choose busses you pretty much do get the final bus version as a wav, which I do standardly for backups etc.

LJB
I suppose one issue would be any new sources being routed there after you freeze the bus. When you bounce and choose busses you pretty much do get the final bus version as a wav, which I do standardly for backups etc.

well, same applies to tracks. when frozen no changes possible so that doesn't break any concept.
 
coming to think of it all required functionality would actually be there since you can bounce any bus faster than real-time e.g. when you export. so it would be a matter of temporarily loading a bounced file and route everything that goes into the bus into nirvana.
 
but what's the benefit ... because muting/archiving tracks which feed the bus (as I said above) is actually not a good idea as it one tracks often feeds many buses (reverb, parallel compression, headphone mix, ...) and thus would totally change the way the song is played back ... and not being able to archive the tracks that feed the bus there is no benefit from freezing a bus, is there?
 
so are we back to a batch-freeze of tracks (parallel, not sequential)??? this would be the option that quickly frees up resources (as the summation at the bus is rarely very intense, is it?)
 

In a bus freeze scenario where would the resulting audio clip exist?    Buses don't handle clips in any way AFAICT.    And if buses were changed to handle audio clips, wouldn't they in effect be aux tracks?

stevec
In a bus freeze scenario where would the resulting audio clip exist?    Buses don't handle clips in any way AFAICT.    And if buses were changed to handle audio clips, wouldn't they in effect be aux tracks?

That will be just one "clip" (may be in optimized format to skip silence). Effectively bounced/exported bus.
Instrument tracks also do not have audio clips till they are "frozen".
 
But I also not do not think performance win is worse the nightmare in conceptual implementation. The only logical solution is to freeze everything on that bus input, including everything with sends to it and side-chains. But wait... that is going to be everything and so Sonar can be replaced by media player

But instruments do include "audio" tracks in disguise, so I assume that's why freeze works (it sure can't be the MIDI portion!).   But perhaps more important, you can't drag any clip into the bus pane so they'd have to change the way that pane works. 
 
Not dissing the idea because I think it could be a convenient means to generate stems.   I'm just wondering how practical it would be as-is.    Now, if there were a "Freeze Bus to Track" command....
 

stevec
Now, if there were a "Freeze Bus to Track" command....

you can record a bus to an aux track but only in real time. if you could do super fast aux track recording (like when exporting stems/tracks where all tracks are bounced at whatever speed your CPU can do) this would solve this issue as well as the batch-freeze for tracks.

Rob[atSound-Rehab]

stevec
Now, if there were a "Freeze Bus to Track" command....

you can record a bus to an aux track but only in real time. if you could do super fast aux track recording (like when exporting stems/tracks where all tracks are bounced at whatever speed your CPU can do) this would solve this issue as well as the batch-freeze for tracks.

^^^^^^^^^^^^^^
 

What ever became of the discussion for Global Freeze? I still like that idea.