Ableton Forum

Howdy,


Just starting to really appreciate the usefulness of the option in SX3/Nuendo3 to "unload from memory" when using Freeze on VSTi's or Audio Tracks ....

It's a shame with Live5 Frozen plugins still consume resources (RAM and sometimes it would appear also CPU).

Also Live 5.03 sessions with lots Frozen, CPU-heavy plugins seem to take as long to open as sessions where the same Session View tracks are not Frozen. This leads me to believe the Live 5.03 projects with Frozen tracks in some capacity still load/launch the plugins of Frozen tracks.

Considering tracks have Freeze files why does L503 still waste time attempting to relaunch these plugins ?

IMHO L503 should only actually open the plugins of Frozen tracks at the point where one UnFreezes the tracks for tweaking/editing.

Any comments ?
(I was debating with myself if this should really be a feature suggestion however really this is an expectation of any Freeze function).,


Cheers and Beers !

jasefos wrote:(I was debating with myself if this should really be a feature suggestion however really this is an expectation of any Freeze function).,

technically this is a feature request, but glad you posted it in here because it might get more attention

the main performance problems with Live right now - unusable arrange grid for many people, bad audio glitching at low-mid loads .... if they are not caused by memory issues are definitely made much much worse the more RAM is used

this is borne out by test after test trying to find out a fix. the "smart disable" that unloads the VST from memory is a huge part of making Live as streamlined and efficient as possible and fixing these problems

,.

bump

Yes - this definitely needs to be addressed.

I think that Ableton should take a look at how Sonar handles freeze. It releases memory back to the system and frees up your resources all around. There is also a quick freeze/unfreeze option. And Sonar allows you to edit/manipulate the track just like any other track in Sonar. (The only downfall here is if you unfreeze your track, it's not going to reflect any changes you made on the frozen track because you were working with the new audio file.)

So, Sonar has incorporated freeze almost like an automatic bounce - automatically rendering the track to disk, muting the original track and removing the original track components from memory. To me this is how it should work (with maybe the exception of the confusion it can create when editing the frozen track, then unfreezing and finding out the changes you made are not reflected).

I was a Sonar user before starting to use Live - and this is something I definitely miss from Sonar.

Here's a little bit more information about Sonar's freeze function (from Cakewalk's web site) for compare:

Break through the limits of your effect and synth use with SONAR 4. SONAR 4's superior freeze implementation for tracks, effects, and synths allows you to optimize your system resources with a new level of flexibility.

• Render your tracks to reduce CPU load in one easy step
  SONAR will automatically unload plug-ins, releasing memory back to the system (especially helpful when using large sampler banks)
  SONAR 4 efficiently freezes only when data is present, conserving disk space
  Quick Unfreeze/Freeze retains frozen data when unfreezing, for quick toggling/auditioning of tracks. This allows you to experiment with settings of Frozen tracks, and you can revert back instantly if you decide not to make the change.
  Edit and arrange frozen tracks

A distinguishing feature of SONAR 4's Freeze implementation is the ability to move and edit frozen data—you can even convert loops of frozen data into groove clips.