1. Didja accidentally blow through the whole, "We're using our real names" thing on registration? No problem, just send me (Mike) a Conversation message and I'll get you sorted, by which I mean hammered-into-obedient-line because I'm SO about having a lot of individuality-destroying, oppressive shit all over my forum.
    Dismiss Notice
  2. You're only as good as the harshest criticism you're willing to hear.
    Dismiss Notice

Berlin WW - RAM Hog

Discussion in 'Tips, Tricks & Talk' started by Cody Ortz, Jun 27, 2018.

  1. I'm working on building a large template in Cubase with my new Berlin WW library. I have one instance of Kontakt per instrument and doing custom keyswitches (instead of different tracks per articulation). I'm using Instrument tracks instead of MIDI tracks routed to a VST instrument. 3 flutes, 2 oboe, e horn, 2 clarinets, 2 bassoon and I'm hitting 16GB of RAM used.

    I've tried purging all of the samples, but it's not doing a whole lot--which surprised me. It's only taking it down to 14GB.

    Do you guys have any suggestions on how to cut down on RAM here? Is there a way to cut down on the RAM kontakt is using over all? Am I missing something with purging the samples--maybe an extra step?

    I haven't even gotten to any of the other sections, or routing, or FX. It'd be nice to cut down wherever I can.

    Or just buy 128GB of RAM :)
     
  2. I don't own BWWs, so I'm not sure how much memory it takes up (although I hear it's quite a lot). But if you purged all samples, I think the problem is that the Kontakt scripting takes up memory for each instrument, and it does not matter if you do it with one instance for all or an instrument per instance. The more complex the scripting, the more memory it takes. And the scripting can't be purged from memory.

    I'm not a Cubase user (I use Reaper) but what I do is disable the tracks completely, with all of the FX offline (I purge the samples, too). The instruments are available, routed and set up, but not taking up any memory. I have a custom action (a custom set of commands done one after the other, like a macro) that disables or enables the track completely. When I enable a track, Kontakt comes online and everything is as normal. This allows me to have a large template (although compared to some other folks I don't yet because I don't own too many libraries). But in theory, I could have as many tracks as I want with little to no impact on RAM, other than the hit it takes from Reaper creating a track, which is like 15Mbs or something like that.

    My situation is a little different, though, so I'm sure someone here that uses both BWWs and Cubase can provide a better solution. But I'd look into the possibility of disabling tracks, if that's available for Cubase. It is the only thing that allowed me to have a template without kicking my computer in the balls everytime I open my DAW.
     
  3. That's a great idea! I didn't think about that. Cubase lets you freeze tracks, which does unload them from RAM and disable it. Gonna be a pain balancing, but that may be a good way to go.
     
  4. One instance of Kontakt uses ~60 MB of RAM. If you can squeeze it all inside one Kontakt (I have it like that), you can save 550 MB.

    But it definitely shouldn't be using that much. Mine use 5GB when everything is loaded up (non-purged) with the Mixed mic. What is your preload buffer size in Kontakt? Head to settings (the gear icon) the Memory and read out the buffer size. Lower value will use less RAM but will utilize the CPU/disk streaming more and vice-versa.

    OT samples don't really purge that well in my experience (they also use a lot of persistent variables in their scripts (source: ED) and that's why the project size bloats up whenever a lot of OT instruments are used).
     
  5. Someone on a different forum suggested that I clear the database and turn off the automatic addition of new libraries. I'm going to give that a try when I get back home in a few days.

    Whenever you purge samples in Kontakt, do you have to click "reset markers" and/or "update sample pool" to clear it from RAM?
     
  6. No, you just purge it. Resetting markers will delete all the markers, so if you were to play your piece after the fact, it would "mark" all the samples used, and if you then hit "Update sample pool" it would purge all except the marked ones.

    "Purge all" always does what it says: it purges all.
     
  7. Another thing that might help, to an extent, is to lower the polyphony for each instrument in Kontakt -- voices use RAM and CPU cycles. Usually these libraries come with an excessive number in there.

    But when lowering the polyphony, play a fast phrase to test whether it still sounds all right.
     
    Jake Schale likes this.

Share This Page