How to save a ton of RAM in Kontakt

I’ve just applied DJH’s guide to saving ram in Kontact and am amazed at the results. When I loaded the gig file with the ram savings (predictive turned off), one instance of Kontact dropped from .6gig ram to 5.5megs ram, and the loading time dropped from 6:31 to 2:52. Impressive! And the instruments still sound fine.
Just wondering though, when using the DJH method, is it still a good thing to do a batch resave or will that just undo the purge method? Cheers, and thank DJH for the great tip!!

1 Like

and where would i find that tip please ? link ?

Well, I did a search within GP and it never showed up. Strangely enough, I typed into Google “How to save a ton of ram in Kontact” and it lead me back to GP! Hopefully, DJH will respond with the link in GP for you.

1 Like

Here’s the link to the article I wrote

@bigalminal FYI — my initials are DHJ, not DJH :slight_smile:

2 Likes

Well, that’s not strange, that’s called SEO :slight_smile:
Hopefully, many people will stumble upon Gig Performer on Google.

You don’t need to google “5 days straight” any more :slight_smile:

1 Like

My apologies.

1 Like

Thanks @dhj

I see, the tip works only for stage / specific song uses.
So there´s no shortcut for my uses. It would have been too nice :wink:

Is that correct? As the article mentions, the purged version is saved in another place outside of Kontact. For the process to work a second time, all you have to do is load it from where it was saved. Or have I misunderstood your comment?

Well, Gig Performer is saving the state of the plugin and if Kontakt includes the list of samples to be loaded, then they’ll get loaded.

So perform the purging on a specific instance and then save that instance as a preset or as a favorite.
Then you should be able to load that preset or favorite to use for other cases.

1 Like

yup :wink:
my comment came from a completly different point of view.
“specific songs” :, …i meant: you know upfront what you play.

ie. a given repetoir, and you´d allways play the same things/ same phrases.
For example just a bass line or some horns over two or three octaves “per instrument”

i was not refering to a “limited use” vs. GP. Hope i could clarifie.

thats an interesting possibility.
I´m again and again amazed how “real live proof” GP is !
in so so many aspects.

You need to know GP, then you see the doors it opens.

2 Likes

Re - “How to save a ton of ram if you are using Kontact.”

I have been applying this process lately to Chris Hein Harmonica. The Kontact file drops from over 280mb to just under 6mb. However, in the place where I save the purged file, Kontact still seems to load heaps of samples even though I input single notes with 127 velocity. The sample folder is way over 3gig and the file still takes many seconds to load even with predictive set to three. Have I missed a step in the process? Why does the samples folder still show over 3 gigs of sample content even though I purged as instructed?

In my experience some libraries do not support purge sample pool.
In this case I would resample Kontakt using Sample Robot or BLISS.

I’m very interested in this. Can you give me more info please?

Ok, BLISS is a piece of software which allows to host a plugin and sample that in an automatic way.
You decide how long each sample should be in ticks (16th) or absolute time in seconds.
You device how many velocity layers and the distance between each note.
You could sample each note or every 3rd for example.
You can decide if loops should made and their position - this works very well.
When sampling is finished you can export that in sound font format.
With Kontakt 5 you can import sound font format and save as an Kontakt Instrument.
And this saved Kontakt instrument you can also load in Kontakt 6.

But you could use also BLISS instead of Kontakt, no need to export as sound font.
BLISS can store the sample in the Gig File as plugin state - I would not do that - or
load it as a program from your drive.

When you build a. Rackspace with BLISS and set the option to use programs,
the samples are loaded when the Rackspace is initialized.
In former version of BLISS this was not working well, but with 2.1 it is working.

Similar you could do with Sample Robot - but I know nothing about that software.
Sample Robot also can sample Hardware, BLISS only resamples plugins.

BLISS is available as a plugin or as a standalone version-.
For Resampling I am using the Standalone Version.

2 Likes

Re - “How to save a ton of ram if you are using Kontact.”

Hmm, can I do this using the GP “saved state” instead of creating a new preset? Is creating a new preset necessary if you are not reusing the preset in other rackspaces?

So, I did the following:

1.Purged all samples in the particular instance of Kontakt
2.Played through the notes I use in the song (maybe several times with different velocities)
3.Updated the Sample Pool
4. Saved the Gig file

Will this work if I do not need to create a preset to use in a different rackspace?

If I later use this rackspace and (let’s say) play more notes in Kontakt and then save the gig file (without updating the sample pool), will this increase the ram loaded?

Or will it revert to the amount of ram loaded from the last time I updated the sample pool?

(I hope this question makes sense)

Thx.

1 Like

Sorry, but I am going to bump this. I “think” what I did above (without creating a preset) works because, when I open up the Gig file and look at the rackspace, it shows the (reduced) amount of ram after I updated the sample pool.

But, it does leave out part of the procedure DHJ lists in his blog post: saving it as a new Kontakt user preset, as I understand it.

I don’t understand - what is being left out?

So, I did the following:

1.Purged all samples in the particular instance of Kontakt
2.Played through the notes I use in the song (maybe several times with different velocities)
3.Updated the Sample Pool
4. Saved the Gig file

But I did not do steps 4/5 in your blog post.

I thought that would only be necessary if you wanted to save that Kontakt user preset (I think that is what it would be (?)) to use in a different rackspace.

Or in Kontakt standalone or in some other plugin host such as a DAW :wink:

That article is not specific to GP and doesn’t even mention Gig Performer in the body. The information is for anybody using Kontakt trying to save memory in Kontakt and of course once they come to our page, hopefully they will also look at GP.

Thx. Okay, what I did seems to work (without saving the change as a new Kontakt preset).:slight_smile: