Freezing tracks with Kontakt does not reduce RAM use

[edit_machine]

Hello, this is an Ableton Live and Kontakt question.

When I freeze tracks that have Kontakt on them there is no reduction in system usage (RAM). Any other device I use on a track and then freeze the track, there is a measurable reduction in system usage (basing this on the os x activity moniter). The only solution I have found is to flatten the tracks, and then the system usage goes down for each track. I'm getting constant crashes with many of my higher end sample libraries if I use more than a few at a time.

I'm running Kontakt 4.2.3 in ableton 8.2.2 on mac os x 10.6.8 on a macbook pro 2.8 gig dual core with 4 GB of ram. Also having the same issue on desktop mac with a 2 x 2.6 quad core intel xenon with 16 gb ram.

[tw1nstates]

Are you talking about RAM usage? Flatten them but first drag the track tio the browser to save it for editing later.

It might be due to the extra processing cycles required to playback the 32 bit audio (which is what live freezes to...)

Unfortunately the way live deals with all of this isn't great, freeze takes for ever and the lack of 64 bit support means that you are stuck using less than 2.5 gigs of ram per project...

[edit_machine]

Hi, and thanks for the response. Yes I do mean RAM. I am flattening them and saving versions of the project that are not flattened so I can change them later. What I don't get is why Freezing them doesn't reduce RAM usage, but Flattening them does. Don't both processes effectively turn off the virtual instrument and create an audio file that plays back in it's place?

[halcyonideals]

flatten/Drag the generator to the side is awesome as long as you stay organized.

I pretty much leave my Kontakt instruments in though since the amazing Purge sample feature, I freeze/Stem down and then Purge/deactivate/deactivate all FX and sometimes freeze again for good measure(which is that really necessary or fills up ram more lol?). Reloading projects is much faster too.

I then group every pair together. This is really awesome too because sometimes I'm yanking and using percussive samples in ways I wouldn't have before or other parts. It's just a great way of seeing it like seeing healthy dynamics.

Only VST's that don't have purge and when I'm near maxing out my 16gb do I store organized generators on the side.

The key would be keeping an eye before crashing the project.

My project is around 220 tracks right now(with paired generators) and I can keep going as long as I watch the RAM and keep purging/ purge after flatten or sidelining things without that feature.

I keep skirting around a free 2gb of RAM and sometimes it goes down to 556 mb but so far never am I incapable of finding a way to keep going with these features.

good luck. (it would be nice if freeze or deactivate did clear RAM, it definitely doesn't seem that way.)

I'm loving orchestral and feeling limitless on this budget Ryzen 5(new now) laptop!
I'm definitely going to snag another 16gb in the future. No way I want to even spend the time to pull apart my machine too busy writing.

It took me TOO LONG to find out about the Purge feature on Kontakt/VST's in general and to not work with a sample based flow from these flattens. I love it.