Komplete and/or Kontakt 8 Memory Leak?

FilmCompos3r · 2024-10-02T06:53:53+00:00

There was an error rendering this rich post.

Using the latest version of Kontakt 8 / Komplete Kontrol 3 I'm finding that Cubase 13 will, upon being left alone, spike RAM usage all the way up to 125GB or so and then crash. This particular session only has about 50-60GB worth of samples loaded into it.

Anyone else seeing this?

Find more posts tagged with

Cubase

Komplete Kontrol

Kontakt 8

Comments

Ongey

Hi @FilmCompos3r & all. I did a test with four instruments, all non-Kontakt, all in Komplete Kontrol containers - two Spitfires, an Applied Acoustics instrument, and good old Arturia Pigments. None of them exhibited any memory leak issue / continual RAM increase after just opening and closing. So, the theory is that yes, maybe this is to do with Kontakt instruments in KK. To reiterate, no problem with using Kontakt 7.

I don't use Kontakt because I want to utilize my KK S61 MK3 keyboard - to be honest, I have some regrets about this quite expensive purchase. It's lovely, but the software has suffered with bugs all year (early in the year it was unusable with Studio One, but credit to NI's developers, who took notice after enough people reported the problem, and then investigated and fixed. Let's hope they can do something about this too.

Ongey

Hi folks, I guess there's not going to be any progress on this issue without support calls. In the meantime, I've generally been ok with Kontakt 8 - it's faster, takes less memory, and most of all, releases it and doesn't start grabbing more (and more etc). Of course, only KK can work with non-Kontakt instruments, but in many cases, you might just use the instrument's own software (e.g. pigments). Not particularly happy with this expensive and buggy software / hardware, but I guess nothing in this inter-communicating world of disparate music gear is perfect…

Felix Le

I experience the same issue (fl studio 20/24 with Komplete Kontrol and Kontakt 7 switching to Kontakt 8 as well as Battery 4). When I open older projects with K7/K6/Battery and I just open the interface, my memory continuously grow to unreached heights.. So I played around to make this growth stop before the DAW crashed. Over and over again :D

Here's what I found out:

Once I replaced all old Komplete Kontrol instances with Kontakt 7/8 or Battery 4 (the same issue!!!), the memory leak stops. The good thing: I can now use Komplete Kontrol with K7 K8 and even Battery 4 embedded. No memory leak anymore. The problem is that the presets with customized settings within Kontakt need to be saved so that you can re-open them in the Kontakt-only (or Battery-only) plugin..

Maybe it helps, even with my non-native english level..

Ongey

https://community.native-instruments.com/discussion/comment/206678#Comment_206678

Thanks Felix. Your experience sounds like mine, and like you, I've switched to Kontakt 8, which seems to have a smaller memory footprint (and no leaks!) and does most of what KK does, except housing non-Kontakt instruments, which I'm not too bothered about (e.g. if I want to use Arturia Pigments, then I won't be opening it in KK!) I've not raised a support call with NI, but I guess if there are enough people then they will take notice…

FilmCompos3r

So this is still happening here in ANY session I'm using Kontakt 8 within Komplete Kontrol, running latest versions of everything in latest version of Cubase 14. As before, after about 20-30 minutes of working in a session something breaks and memory starts climbing til it crashes the system.

Doesn't happen in session where I'm using plain old Kontakt 8, and doesn't happen using Komplete Kontrol with other plugins (Diva, Massive, etc). Only occurs when using Kontakt within Komplete Kontrol.

I'm generally getting around this thanks to the new Kontakt MK3 integration but I'd still like Kontakt working in Komplete Kontrol for legacy projects and for creating my own custom NKS files.

Any chance this is still being looked into?

Ongey

https://community.native-instruments.com/discussion/comment/212532#Comment_212532

I think the only way to alert NI is to raise a support ticket. As you say, you're ok with just Kontakt 8, and that's the experience of others too. I'm ok with it, and to be honest, if the KK bug was fixed, I might not switch back anyway.

If you do raise a ticket, then I'm happy for you to direct them to this thread, and am happy to get involved to try out things etc.

b-righteous

Wanted to chime in to say I am experiencing the same issue with KK 2.9.6 and Kontakt in Windows 11. I have been trying to track down this memory leak issue for a while. The issue happens when I leave a session open overnight. Seems to crash multiple DAWs including Ableton and Studio One. The common denominator is I have Komplete Kontrol with a Kontakt instance loaded on every session. Removing Kontakt from Komplete Kontrol remedies the issue and I get no crashes after leaving session unattended overnight and some longer than 24 hours.

It would be great if NI could try to reproduce this issue and provide a fix. Komplete Kontrol is an essential part of my workflow and of course I should be able to use Kontakt instruments without that combination causing crashes or memory leaks.

Super8boy

@Matthew_NI @Chris_NI whats the status update on the Kontakt 8 and Kk front regarding this bug?

Has it been reproduced? Is it only on cubase & studio one or do some people have that issue on Ableton live as well?

Haven’t upgraded to Kontakt 8 yet as I didn’t want potential instability

Jeremy_NI

@Ongey @Super8boy Have you contacted support already? If you haven't please do and mention me and this thread.

Ongey

https://community.native-instruments.com/discussion/comment/213385#Comment_213385

Hi, I've not contacted support because my workaround of using Kontakt 7 (and now 8) seemed to be better for me (in terms of memory leaks, memory usage, and speed of load), and with the increased integration of my KK S61 keyboard with Kontakt 8, I wasn't missing out on much.

Of course, workarounds are not what you, or any of us want to experience. I do observe that @FilmCompos3r and others were in contact with NI developers late last year (see page 1 of this thread) - not sure what the outcome of that was. It's best that someone who is actively blocked raises a support ticket. However, am happy to help with any evidence, so will keep an eye on this thread.

Quick links

Unanswered questions