This How to save RAM from 1GB To 1MB Inside Your Kontakt Libraries

(1) As you see brass ensemble Load almost 1 GB Of RAM
(2) So there's a way to load This Patch With Less Than 10 MB
(3) To use this patch with less RAM Click On "Update Sample Pool"

See The First Picture Below



(4) As you see brass ensemble Now Load almost 7.32 MB Or Less
(5) So Now The Amount Of RAM is related Now With The Keys you play On The Keyboard Instead
(6) When It turns yellow it means that it will load only the samples
you played without the need to load all samples

See The Second Picture Below



NOTE
This post is for people who are new to this method
Have a good day everyone ​

 

Last edited: Jun 16, 2016

What are the benefits for doing this? Less CPU spikes?

 

Hey, ty. Seems a weird way NI decided to have Kontakt behave, but I'll do that now.

@signalflow I think it's more about not "running out of whatever" in the DAW, like I used to get in PT running too many VSTi's (well their version of them). You never got that message: FU, computer can't do any more, ty come again? From your DAW?

 

@Mr_Amine Thanks for the tip my brotha!

@signalflow wait till you have a project with 8 instances of Kontakt plus X number of Vst's and you'll be begging for more ram so you can work in realtime.

 

Cool so this should help with some cpu intensive libraries. Is there a benefit to batch compressing a large library? I wanted to do it (back up the library first of course) but wanted to see if there was any real benefit before I spend the time. I've batched resaved which helped with load times.

 

OBVIOUSLY you will save RAM of your Machine ;
lets imagine you will use 12 or 15 kontakt libraries
each library will take around 1 GB or more
and then you will end up using More Than 16 GB Of RAM
While you can use the same 15 libraries with less amount of 16 GB RAM could be 8 GB or 6 GB

For example : brass ensemble take 1 GB RAM to load all samples
And when you only need to play from (F5 > F#5 > B5) = Around 7 MB
SO 7 MB is way better than 1 GB

 

Last edited: Jun 16, 2016

Werd. CPU is with more than gold imo

 

Is there anyway to set this up as a global setting so everyone Kontakt is open the sample pool is already updated?

 

best way is to use update sample pool
everytime you use kontakt and save that nki as (name of the patch) + update sample pool.nki
or you can name the nki file as Brass Ensemble USP.nki
i have Co-workers in my studio they used NYRV SYSTEMS AGENT for plugins include kontakt

 

@Mr_Amine thanks much for the tip.. kontakt illiterate here...


I get lots of pops sometimes when i am playing say
The Grandeur.. hope this will help !...

Do we need a "simple" kontakt tips thread? so we can collect the best of ?

I like @Introninja 's but it gets a bit deep for me sometimes.. then i ;tldr

 

WTFFFFF wow, thank you for this so much

 

So what's the purge all samples do?

 

Last edited: Jun 16, 2016

@signalflow and anyone new to the DFD concept in Kontakt:
It's not about CPU usage, but it's about memory consumption due to Kontakt pre-loading the initial portions of samples. With today's gigabyte-size libraries and direct-from-disk streaming, any sampler has to do this.
It's a compromise:
Loading all samples into RAM in full length would eat up your RAM much too fast, but only streaming all samples from disk would always lead to (longer or shorter) dropouts because it always takes some time between hitting a MIDI key, loading the sample and playing it back. SSDs will be much faster than conventional HDDs because access times are significantly lower, but there will be a tiny dropout anyway until the sample(s) can be played back, especially when playing multiple notes at the same time.
In the Kontakt memory options, you can change the sample preload size to tell Kontakt how large a portion of the initial sample attack Kontakt should load into RAM, so it can play back *any* sample you play without delay. The length of this pre-load buffer depends on how much time your HDD needs to deliver the data in the worst case.
This is not too useful if you play Kontakt live, but if you use it in a composition in your DAW, you can let Kontakt "learn" what notes you played and only pre-load the specific samples at certain velocity levels that you actually need, to avoid drop-outs, like Mr_Amine has shown.
"Purge all samples" will remove the pre-loaded samples in RAM that have not been played since loading the Kontakt instrument.
This can make quite a difference in RAM consumption, especially when using multiple Kontakt instruments simultaneously. Obviously you should do this only *after* playing your tracks.

 

Last edited: Jun 16, 2016

was just typing exactly that, But Great option nonetheless!

Thnx Mr_anime!

 

THANXAMILLION! In all my tweaking and geeking- and freaking-out over Kontakt's RAM-hogging, THIS is what I'd been seeking!

 

Great tip @Mr_Amine . Very useful but I got a question, how does this differ from using "Purge" instead??? Curious

 

Last edited: Jun 16, 2016

I was using "Purge all samples"
then only keys i play were loaded in ram like u said in step 5

 

Wow! I've been using Kontakt for quite awhile and I had never heard about this method. Your advice is going to be extremely helpful to me. Thank you so very much.

 

Purge All Samples & Update sample Pool , if you notice they both unload & Load all samples but there's difference between both
when you play in real time you'll notice that in purge all samples there's delay in ms
but update sample pool loading of samples is faster
that's why most of people since kontakt 2 & 3 they always use
purge all samples to unload all samples & update sample pool to load samples

 

Last edited: Jun 17, 2016

Like cache mode in superior drummer¿