What's new

Kontakt 7 PC Launch Time Issue Fix

YaniDee

Senior Member
Kontakt 7 was taking several minutes (!) to launch, and was driving me nuts. Based on info I gathered from the NI Forum, I went to the C:\Program Files\Common Files\Native Instruments\Service Center folder, and removed non NI XML files, which included each of my 40+ waves plugins, and numerous other synths and plugins. K7 now loads in a couple of seconds! Anyone know what is the purpose of all those XML files? In any case, my workflow has just improved immensly..

Forum link: https://community.native-instruments.com/discussion/9538/kontakt-7-very-very-long-to-launch
 
NKS I would imagine...

And what do ya know... It seems to work in macos as well... (Path is different: Library/Application Support/Native Instruments/Service Center) Load times just dropped from 20-30 seconds to about 2... I'll see if the snappy load times stick after a reboot though, as the snappy loading could theoretically also being due to caching.

Assuming it is NKS this would obvioiulsy potentially impact people who do rely on it for controllers, the KK plugin, etc. Something to think about... I made a folder outside of the Service Center folder and called it Service Center Moved so nothing actually winds up being deleted...
 
I didn't delete the files either, but I don't use anything that would require them, and still don't see what Kontakt has to do with Synthmaster , AAS, Waves, etc. I just use Kontakt in the "old fashioned" way to load libraries. They should give people options, or at least an awareness that it will slow down loading times..
 
and still don't see what Kontakt has to do with Synthmaster , AAS, Waves, etc.
Those products have implemented NKS assets, and the new browser in Kontakt just scans through all installed products that have NKS (there is no way to know that something is only for Kontakt, without scanning it first).
 
Yes, but it scans everytime you instantiate K7 OR open the GUI. That's really bad design.
I really hope the feedback gets heard and NI changes that situation.
 
Database is instantiated only once as far as I know, when Kontakt is instantiated on a track. It makes no sense to do it any other way.
 
Hi !

I think I've found the source of the problem with my configuration.

I have a network drive turned on only occasionally to make backups.

I removed the disk mapping and in addition in Kontakt in the tab ➡ Files ➡ View ➡ I unchecked "Show network drives" and this solved the problem at least for my configuration.
 
Last edited:
Kontakt 7 was taking several minutes (!) to launch, and was driving me nuts. Based on info I gathered from the NI Forum, I went to the C:\Program Files\Common Files\Native Instruments\Service Center folder, and removed non NI XML files, which included each of my 40+ waves plugins, and numerous other synths and plugins. K7 now loads in a couple of seconds! Anyone know what is the purpose of all those XML files? In any case, my workflow has just improved immensly..

Forum link: https://community.native-instruments.com/discussion/9538/kontakt-7-very-very-long-to-launch
Got excited there for a minute, but sadly no appreciable difference in load time clearing those files here.

On the linked thread, this post from _Stevie in November caught my eye:

Yeah this is really frustrating, even more, since I found the root of the issue. It is caused by the NKS implementation, which is scanning the content of all VST folders.

I used the Sysinternals Process Monitor to track both, Kontakt 6 and Kontakt 7.

It captured 10 000 000 events (file access and registry access) when starting Kontakt 7. Yes, you read correctly, 10 million events.

Monitoring Kontakt 6 creates 46 000 events and literally only accesses the Quick Load entries.

If this is accurate, its very hard to understand why NI are still baffled by what is causing it, over a year later.
 
Have the same problem. Have tried all the fixes. The first version (7.0) worked fine for me.Then I think it was the first or second update when this problem appeared. That should help pin it down when something was changed.
 
Top Bottom