Freezing tracks is a useful feature, but often I only want to use it for freeing up resources that virtual instruments takes up.
What would be ideal, is if options were given to what gets frozen, including VSTi, plug ins, channel strip etc. I typically only want to freeze the instrument, but then still have access to the channel strip (volume, pan, inserts etc).
At the moment I have to bounce down the VSTi as a dry track, then import onto a seperate track, which is tedious
More Freeze track options
-
Robert Henke
- Posts: 1193
- Joined: Fri Jun 04, 2004 10:38 am
- Location: Berlin
Hi Robert (studies for thunder live should have been astonishing! my best compliments!).Robert Henke wrote:Freeze will be improved in futurer releases. All suggestions / ideas / wishes are welcome.
Robert Henke
Ableton
It would be useful to find a smart way to freeze tracks used by midi clips playing the same instrument. I often use multitimbral instruments and freezing is a pain! I have to resample the tracks!
Oh, by the way it would be useful a 'clip render' option instead of freeze... I almost constantly need to change volume or other envelopes in freezed tracks! Or, at least, try to make that possible in freezed tracks! I think it's strange to have them almost completely "freezed" when it's a common need to adjust them after having revised other tracks. And I think freeze has exactly been implemented to answer that need: "I have to continue mixing/working but I have not enough cpu power..."
I would love to see a feature called "print effects" or something like that. It would be somewhat in between a render-in-place and a freeze feature. Selecting "print effects" on a track would render the whole track in place as a new audio file and delete all of the plugins from the track. What would make it very interesting and powerful is if the track's past history was saved and easily accessible to go back in time and edit.
So for example, you could create a track, put 10 plugins on it and then "print" it. Then you could edit the new audio file, reverse segments of it, add new effects, etc. and print that. Each time you "print" it saves a new history state which is accessible through a menu or through numbered buttons or something. Then you can choose to jump back to history state "1" which is the original track with 10 plugins, make changes to various effects settings, and then jump back to history state 3 or wherever you're at and have all of those changes reflected.
This would kind of be like working with nested comps in a program like After Effects for anyone who is familiar with that paradigm. A feature like this could add an incredibly powerful new dimension to live while also taking care of the more common tasks of render-in-place or freezing plugins to free up cpu usage.
So for example, you could create a track, put 10 plugins on it and then "print" it. Then you could edit the new audio file, reverse segments of it, add new effects, etc. and print that. Each time you "print" it saves a new history state which is accessible through a menu or through numbered buttons or something. Then you can choose to jump back to history state "1" which is the original track with 10 plugins, make changes to various effects settings, and then jump back to history state 3 or wherever you're at and have all of those changes reflected.
This would kind of be like working with nested comps in a program like After Effects for anyone who is familiar with that paradigm. A feature like this could add an incredibly powerful new dimension to live while also taking care of the more common tasks of render-in-place or freezing plugins to free up cpu usage.