Kontakt 7 very very long to launch
Answers
-
Supplement:
Starting with the Steinberg Built In ASIO Driver is therefore faster because it only starts 2 inputs/outputs. The same is possible with the ASIO4All driver with only 2 inputs/outputs.Incidentally, Kontakt 7 took 27 seconds to start with the Steinberg Built In ASIO Driver before the update, instead of 6 seconds. Therefore, the increase is more noticeable there.
0 -
instead of one minute it now takes 15 seconds, while Kontakt 6 still takes 4 seconds.
Whats about Kontakt 8, Maschine 3 and Komplete Kontrol 3 - will this loadiong mess problem gets therere adressed too or shall i stick with Kontakt 6 and maschine 2 ?
Maschine 3 also uses nearly one Minute to open this damn plugin, while Maschine 2.16 uses 4 seconds
0 -
I’ve been working with an alternate audio interface - a 2 in 2 our Presonus Audiobox - this week and noticed save times in Cubase / Kontakt 8 are much much faster than using my RME Fireface 802, 18 in and out.
I noticed a few folks commenting that the number of audio channels is impacting Kontakt save times…so is this really a thing then I need to look into? Are there other factors? The time savings have been massive.
0 -
Anyone still with a slow load issue should also be installing K7.10.7 - which is the final update and for Windows users - it can really improve load times.
VP
0 -
yea but it seems like this “number of channels on the audio interface” thing might be affecting other aspects of save/load times even after the latest Kontakt 7 update (I’m using 8 so the update is moot for me, but I still experience much longer save times than should be needed on my “big” RME interface.)
0 -
I have an RME UCX-II (up to 40 in-out) and haven't seen any delays or issues saving any project in Studio One.
And I use Kontakt a lot - pretty much every track has a minimum of 4 instances - but I never use Kontakt as a standalone instance - all are exclusively in use via Komplete Kontrol (v2.9.6)
Anyway - thought this thread was about "load times"?
If this thing has morphed into "save times" - which is completely unrelated to the ongoing issues some were having with Kontakt start up times - which has now been fixed with 7.10.7 - might be time for a new thread devoted to "save times".
VP
0 -
Apologies for morphing the thread topic, I had just never before seen anyone saying the interface driver itself would have any impact on load times (and in my case, save times), and I'm leaving no stone unturned on my quest for Kontakt to behave reliably. Combining that with the fact I happen to be using a smaller interface atm, and seem to be seeing better results, and I thought I'd ask.
0 -
The slow load issue is very well known. And now fixed.
That said - I have never heard of anyone ever complaint about save times - until the latter part of this thread.
A slow "save" injects a DAW into the equation and an infinite number of variables - none of which I would think should have anything to do with your audio interface.
If it does - that is bordering on totally weird and obscure and must have a different cause.
VP
0 -
Very slow save times within the DAW (in this case, Cubase, which was referenced above) are a major issue for those of us in the film music world with a lot of instances running. You'll find numerous other threads on that topic if you search, such as this one:
saving times taking 3 mins since loading Kontakt 8 (KT-10248) - Page 3 — Community
In any case, I'll start a new thread on the audio interface thing when I get back my bigger interface so I can properly A-B the situation. It does seem crazy that there'd be a link between audio inputs/outputs on the interface and Kontakt but honestly none of the bugs I encounter with this program are very intuitive.
0 -
Well - I have seen the Cubase issue - a lot.
But because the same does not happen in Studio One - stands to reason this may not specifically be solely a Kontakt issue. Or have anything whatsoever to do with audio in/outs. I really cannot grasp how that would matter.
If it only happens in Cubase - might be time to knock on Steinberg's door and ask them what is up.
VP
0 -
Hi all, I have the same problem like y'all: excessive loading times of K7 and KK2.9.1. My template rendered nearly unsuable (4 yrs. of work).
So I looked a bit deeper and maybe I found a (or the) reason (at least in my case) for this strange and worsening behaviour:
every time K7 or KK starts its reads the komplete.db3 SQL database (as I documented by using procmon.exe). And the loading time increases considerably over time because every new information is written into this database. My komplete.db3-file has meanwhile increased to nearly 1 Gb (!) in size. So every time K7 or KK load up they have to go through that (whole) database (you will find it in "C:\Users\xxxxx\AppData\Local\Native Instruments\Komplete Kontrol"). Can you image? Every single time (afaik)!
If you want to replicate this:
!!! - Don't delete the file komplete.db3 - !!!
Check the size of komplete.db3 on your system and rename the komplete.db3-file temporarily (*don't* delete it!!!). Both KK and K7 start fast now. But: don't panic! - every information about all your libraries will be gone - K7 or KK are "empty" for the moment. Close the app, delete the newly built komplete.db3 - file, rename your original to komplete.db3 and voila: there are all your libraries back in place but the long loading times occur again.
I opened the database in SQLstudio and tried to reduce the size of the file by using the 'VACUUM' method - no success, the file size remains the same. Has anyone a better method?
So the problem seems to be systematic - that's probably the cause why NI can't solve it. The DB-connection is baked into the applications and the whole system relies on it. And it gets worse over time. The bigger the database the heavier the complaints of the users will be.
Someday this will lead to a complete halt of the whole NI-realm if NI doen't solve this problem.Has anybody made the same experience? Please tell or confirm my findings, I would appreciate that.
Steve
0 -
"Has anybody made the same experience? Please tell or confirm my findings, I would appreciate that"
Just checked mine:
Create date - equals the exact date this DAW went online. Modified yesterday. File size 207MB
Disk Type = Samsung 1TB NVMe 990 Pro.
RAM = 64 GB of Corsair DDR5
CPU = 13th Gen Intel i5-13600K.
Komplete Kontrol (v2.9.6) and Kontakt 7 (v7.10.7) open in mere seconds.
I have Komplete 14 ULT - with approx. 60% of the package installed. Studio One scans 411 VST3 plugins at startup in 2.78secs. No issues that I can see.
How many plugins are you rocking over there - exactly?
If it's over a 1000 - not exactly sure what you are expecting if Kontakt has to grind thru that many plugs everytime. and then let's add these items into the calculations:
What kind of drives are you running?
Is OneDrive somehow wrapped into this?
Is your CPU from 2017?
Has Windows Defender been tamed? Because it will ride right alongside Komplete Kontrol and do an internal malware scan on every plugin - adding scads of additional waiting time - every time - if has not been specifically instructed to stand down.
Lots of overhead is possible without a deep dive.
VP
0
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 61 NI News
- 772 Tech Talks
- 4K Native Access
- 16.3K Komplete
- 2K Komplete General
- 4.3K Komplete Kontrol
- 5.6K Kontakt
- 1.6K Reaktor
- 376 Battery 4
- 835 Guitar Rig & FX
- 425 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.7K Maschine
- 7.2K Traktor
- 7.2K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators