VEPRO Uses all RAM, then deloads

[erichall]

I don't know if this is a Kontakt question or a VEPRO question, but figure I'd post here.

I have an orchestral template. I am using mostly Kontakt, some Opus, and Sine. K7 and Opus has EVERYTHING purged. However, on loadup, it utilizes 63.x GB RAM out of my 64GB available. But the longer (after loading my template) that VEPRO sits - or even if it connects to a Cubase project - the memory usage gradually goes DOWN. Usually drops down to a more reasonable 30-40GB ram.

Sometimes it doesn't deload and crashes. But this isn't the norm.

Does anyone know what the mechanism of this is? If all of my Kontakt instances (and Opus) are supposed to be "loaded" in a purged state, why is nearly everything being loaded into RAM, and then gradually de-loading on its own? 

[iftekharulanam]

@erichall said in [VEPRO Uses all RAM, then deloads](/post/317377):

I don't know if this is a Kontakt question or a VEPRO question, but figure I'd post here.

I have an orchestral template. I am using mostly Kontakt, some Opus, and Sine. K7 and Opus has EVERYTHING purged. However, on loadup, it utilizes 63.x GB RAM out of my 64GB available. But the longer (after loading my template) that VEPRO sits - or even if it connects to a Cubase project - the memory usage gradually goes DOWN. Usually drops down to a more reasonable 30-40GB ram.

Sometimes it doesn't deload and crashes. But this isn't the norm.

Does anyone know what the mechanism of this is? If all of my Kontakt instances (and Opus) are supposed to be "loaded" in a purged state, why is nearly everything being loaded into RAM, and then gradually de-loading on its own? 

 Same here for me. It usually takes around 15-20 minutes to unload back to around 50%. I am also looking for a solution to this. I also have 64 gigabytes of RAM.