Komplete Kontrol 3.3.4
Comments
-
I installed KK 2.9.6 now and at least the full scan every time has stopped, but it is still a massive downgrade from KK 3
0 -
So does mine. So does everyone's until you press ESC.
VP
0 -
10-20 minutes can be considered as normal, only on the first time scan. After that, it is not normal.
But it has nothing to do with what KK version you are using.Most common causes are:
- You didn't make a complete scan in KK stand alone mode (not as a plugin). This is necessary and it is one time only. After that, it should be open between 3 and 15 second, depending on your computer power.
- You do have a problematic plugin that delays the scan. Please take a look at the start-up screen and check on which plugin name the scan stuck.
2 - You didn't make a complete scan in KK stand alone mode (not as a plugin). This is necessary and it is one time only. After that, it should be open between 3 and 15 second, depending on your computer power.
-
Also, if by any chance you have Waves plugins or any plugin that uses USB license, then, this is another cause for the problem.
As you can see in the thread below, from November 2022, same problem appeared with KK version 2.8 and the cause was that. Waves plugins USB stick license:
1 -
The thing is there is no error or hold up. I just goes through without any issues, I just have a lot of plugins. But for some reason every time I open KK it does a full plugin scan even tho the previous one ran through perfectly fine. I do not understand this problem, it was working fine before I wiped my hardrive and reinstalled. Nothing changed, still the same computer, same OS, everything is the same, just now it is not working any more
0 -
Mine does a full scan as well - every time. This is by design. KK has never ever not done a full scan at startup. It might appear to go really really fast the second time but it's still a full scan.
VP
0 -
Prob confusing the case between "full scan" and what I would call a "deep scan"
Initial load, KK has to interrogate every plugin to know what it is, what version it is, capabilities and vendor so it can populate the plugin list.
This can take a long time and even "stall" if you have a lot of plugins, ideally you remove what you don't need or what is not a full version to make this faster.
Once it completes this it should set a flag in some config file that says it is no longer the "first time start" of KK and it then switches to the "quick scan" method on startup which is suppose to be a simple check of the plugins in the menu to make sure they still exist, if any have changed or if there are any new ones and this will trigger the scanner top then interrogate those plugins.
Issue some find is some plugins that use shells or constant "always online" auth methods may find these plugins will cause a slowdown in the scanner on every load. Plugins such as Waves, Roland and even the latest Air Music plugins can all cause slowdowns in startup.
I noted (myself and via a lot of feedback) that KK V3 seems to have more problem in the startup scan than V2 so not sure what is at play there. Yes you can press ESC to bypass the scan but of course if it never did the initial scan on first start, no plugins will appear in your list.
Things to make sure it is as efficient as possible:
- Remove all old plugins, 32bit plugins and if you don't need them, VST2 plugins and just scan VST3 plugins
- Make sure all plugins you do use are properly registered and able to be launched without asking for activation
- Do not add any additional VST scan paths that are not direct folders with the plugins in (like I have seen some people literally add C:\ as a scan path). You should really just have 2 folders at most, one for VST32 plugins and one for VST2 plugins (if you use them).
The more plugins you have the longer it takes but even with 500+ plugins, anything for the quick scan beyond 1 min is usually indicating an issue of some kind, usually under 30 seconds is what should be expected, up to 1+ hours potentially on a deep scan
1 -
“Once it completes this it should set a flag in some config file that says it is no longer the "first time start" of KK and it then switches to the "quick scan" method on startup which is suppose to be a simple check of the plugins in the menu to make sure they still exist, if any have changed or if there are any new ones and this will trigger the scanner top then interrogate those plugins”
This makes more sense. That first scan was painful but now it’s just a few seconds.
VP
0 -
"some config file that says it is no longer the "first time start"
Very correct.
This file, on Windows, is the Plugin_kk3.data (or Plugin.data for earlier versions), at:
C:\Users\user\AppData\Local\Native Instruments\Komplete KontrolIf you open this file with a text editor you will see that it is just an "archive of locations".
So, at first full (deep) scan, this file is created, that's why it needs more time. But after that, when you open KK, it simply "reads" this file, that's why the software opens almost instant.
Backing up those kind of files (before formatting or moving to new disc) will save you a lot of time!
A similar file exists for Mac too, and the procedure is the same.Now, in our case here, all the above brought me a simple idea: @KarlKaos please check your location for such file. If it does not exists, then my idea is that KK does not have full access to write on your hard disc.
0 -
So I kinda gave up. I figured out what plugins I could get rid of and formatted once again and I am now running 2.9.6 … it is not ideal but at least it works. I already gave KK full disk access on mac, but it still just wouldn't work. I think the main problem here is that macOS 12 isn't officially supported any more for KK 3, so that is probably what the issue is. It somehow worked before but definitely not any more
2 -
Yes, the VST data is stored in that file, but there is another option which use to be a registry setting that said "firstLaunch" or something to that degree which actually controlled the scanning behaviour irrespective of the existence of the pluginData file. The reg key no longer exists so this is likely in some other location, may have also been something only in a beta some time ago but there is a mechanism that switches this scanning behaviour.
2.9.6 is, in all honesty, just more robust. V3 is kind of like KK was 10 years ago now and seems since it has come out it's been a non stop run of chasing bugs and issues, which is still constant. Many of us are sitting back on .2, just waiting for V3 to improve in some way.
1 -
"2.9.6 is, in all honesty, just more robust"
Agreed.
VP
0 -
Maybe (not totally sure yet) I might try to have KK 2.9.6 do the first scan and when it created the file, I upgrade to the new version. Maybe I can trick it that way into "thinking" the first scan is already done
0 -
As far as I know then there is also this sort of fix :
Quote Kymeia October 2023 :
Well there is the scan app itself, I have not tried it myself but I guess you could see if moving it to a temp folder stops the scan on startup, rather than causing a crash (which I think is possible as when I had KK2 and KK3 on my system I had effectively a non functional scan app for one of them but it didn’t cause a crash).
Obviously when you update plugins you would need to move it back temporarily so don’t just delete itQuote Daniel January 2022 :What I do to use KK without the scanning process: I rename the "ScanApp" to "ScanApp_" … After KK won't recognize the ScanApp and will launch automatically without the scanning process.Here you find the Location for the ScanApp on your Mac:/Library/Application Support/Native Instruments/Komplete Kontrol/ScanApp.appThere should be a similar path on Windows …
0 -
That is just it. You cannot just "upgrade".
In order to use KKv3 (correctly) - where KKv2 was there previously - you must fully uninstall KK v2.9.6 and then install KK v3 clean - where this "file" will most likely be stripped and recreated any way.
Again - not sure why you keep pressing for KK v3 if you do not own and MKIII series keyboard - especially on this OS - which is now end of life.
If it were me and I was committed to OS12 for now - I would stay on the tried and true KK v2.9.6.
VP
0
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 62 NI News
- 785 Tech Talks
- 4.1K Native Access
- 16.6K Komplete
- 2K Komplete General
- 4.3K Komplete Kontrol
- 5.7K Kontakt
- 1.6K Reaktor
- 379 Battery 4
- 846 Guitar Rig & FX
- 429 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.8K Maschine
- 7.3K Traktor
- 7.3K 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