Some thoughts on Freezing tracks
Posted: Mon May 17, 2010 4:39 pm
When freezing a track, an audio file is generated in order to free up the processor power used by that particular track.
The frozen track will automaticly be "unfrozen" as soon as a parameter is changed in a plugin.
This feature is very nice to have as it allows one to seemlessly go back and change things.
One issue with this is that when a track is frozen, all the plugins on that track is still loaded.
In some chases where there is a heavy use of samples (symphonic orchestra, chiors, drumkit etc), all the
samples will still be loaded into memory even though the track is frozen.
Of course this allows one to go back quickly and change things with the plugins, but sometimes you
really need that extra memory to work on other tracks.
One solution would be to flatten the frozen track, but once the track is flattened there is no turning back.
My suggestion:
Add a second freeze feature which will also unload the plugins.
I could be called "Freeze and Unload" or "Hibernate track", or something like that.
This feature would unload all plugins, with samples and all, in order to both free up memory and CPU power.
Once a parameter is changed, all the plugins and samples needs to be reloaded.
Therefor there should be a confirmation box saying something like: "This action will revert this frozen track and reload all plugins, yes/no".
Another thing that would be nice is to be able to freeze group tracks, instead of going in to the group and freezing every single track.
This would not only be more time efficient to the user, but it would also require less space on the disk for the frozen audio files.
And btw, Thanks for an awesome program!
The frozen track will automaticly be "unfrozen" as soon as a parameter is changed in a plugin.
This feature is very nice to have as it allows one to seemlessly go back and change things.
One issue with this is that when a track is frozen, all the plugins on that track is still loaded.
In some chases where there is a heavy use of samples (symphonic orchestra, chiors, drumkit etc), all the
samples will still be loaded into memory even though the track is frozen.
Of course this allows one to go back quickly and change things with the plugins, but sometimes you
really need that extra memory to work on other tracks.
One solution would be to flatten the frozen track, but once the track is flattened there is no turning back.
My suggestion:
Add a second freeze feature which will also unload the plugins.
I could be called "Freeze and Unload" or "Hibernate track", or something like that.
This feature would unload all plugins, with samples and all, in order to both free up memory and CPU power.
Once a parameter is changed, all the plugins and samples needs to be reloaded.
Therefor there should be a confirmation box saying something like: "This action will revert this frozen track and reload all plugins, yes/no".
Another thing that would be nice is to be able to freeze group tracks, instead of going in to the group and freezing every single track.
This would not only be more time efficient to the user, but it would also require less space on the disk for the frozen audio files.
And btw, Thanks for an awesome program!