I suppose that the Freeze function that speaks Sardaukar must be a transparent process for the user, no need for some new bounce track in the hierarchy, just the background creation of a file that is played INSTEAD OF what is seen on the selected track(s).
There will be no visual change in the arrangement other than a different aspect of the track and the fact that it is locked.
When the Freeze button is unpressed, the hidden file is destroyed and the track can be edited etc.
Is this what you mean ?
If yes, I think that this feature would correspond to a different usage than the Bounce, and will be a good complement.
What I like with the bounce is that it makes a new file that I can eventually edit and copy to another arrangement.
What would be nice with a transparent Freeze feature is to help the CPU during editing before the final bounce, without having to create and see new tracks which are only duplications of others and take some space on the arrangement for nothing.
.
