3.5.0 hangs no matter what plugin it is

I have this problem where Komplete Kontrol Software hangs on opening while scaning plugins I have tried all the suggestions on the community and still does not work it hapens both on standalone and in daw as plugin
Best Answer
-
OK, so, the avox choir was loading an instance of code meter which crashed ableton and fl studio when i tried to load it. run the autotune central app and they are moving over to ilok so had to set it all up, now loads with no issues.
analog va2 and dune 2 loaded with no issues.
run the updates in waves and cleared the waveshell error.
solina asked to sign into my account n the air website and redirected me back
updated komplete kontrol in native access to 3.5
loaded with no issues 😍
Thanks Jason for pointing the errors out, convinced it was codemeter loading with Avox which was the culprit.
many thanks guys tanks for the help
0
Answers
-
@TeeJay2075 It looks like this scan log points at some things being scanned that are definitely not audio plugins. Please check your VST2 and VST3 folders for any dll files that are not audio plug-ins.
0 -
Post a screenshot of your Preferences > Plugins > Locations screen
0 -
Hi all, I'm having the same issue, just updated to 15 and not really used Komplete Kontrol for a while after moving and just now resetting everything up.
It starts up and scans all plugins,,, gets to last plugin scans that one and just hangs there.
tried uninstalling and deleting the KK folder in the app data local folder, then re installed and tried again but did exactly the same just hangs. I have my S61 mk2 keyboard setup and just shows the the midi dims on the screen nothing else.
0 -
Have seem some people are downloading and running a previous version of 3.2.1 who are having the same issues.
Is that the best temporary fix for the minute ? I'm currently running 3.5 and having no joy with it loading.?
loaded up maschine 3 with no issues?
As the program isn't loading I can not get into preferences Jason to find the plugin in locations, will they not be default after a fresh install ?
0 -
On a default install yeah should be default unless you have installed KK at all in the past or even updated (which you do say you updated in another thread), the settings are carried over so unless it is stated this is a brand new install it is not known if this is the case so any information to clarify is always welcome. However, it will point out exactly what locations are set even as default so you can then simply focus in those locations. Just FYI, in your other thread with a log it shows non default locations being scanned:
C:\Program Files\VstPlugins\
C:\Program Files\Steinberg\VSTPlugins\also the 32bit location which is no longer supported by KK and should be removed (I think KK ads this by default but I always remove everything except the VST3 path and my main VST2 path):
C:\Program Files\Native Instruments\VSTPlugins 32 bit\A
You do have a few plugins failing the scan which could mean these are problematic so may be an idea to check these and update them:
Scanning plugin AVOX CHOIR failed with result code -1073740791, error code { .value = 0, .category = system, .message = The operation completed successfully } and message ""
Scanning plugin Ultra Analog VA-2 failed with result code -1073741819, error code { .value = 0, .category = system, .message = The operation completed successfully } and message ""
Scanning plugin Solina failed with result code -1073741510, error code { .value = 0, .category = system, .message = The operation completed successfully } and message "*** Queue destroyed without being stopped ***
[ERROR] Scanning of plugin C:\Program Files\Common Files\VST3\WaveShell1-VST3 15.0_x64.vst3 with name failed because not valid information could be obtained
[ERROR] Scanning of plugin C:\Program Files\Orion\VSTPlugins\DUNE 2.dll with name failed because not valid information could be obtainedOn the previous v2 of KK you could press the ESC key when the loading splash screen displays to cancel the scanning and go straight into the KK software. Not sure if this is still possible in the latest v3 KK (should be if it was designed by someone with sanity) but was an important function to allow easy changes to the scanning paths in the case where a user has multiple locations where VSTs are, more applicable back when VST2 was a thing and people had a mess of plugins scattered around their system. If you can bypass the initial scan then you can go into the plugin locations tab and select one location and click rescan to try and rescan again from within the software.
The request for that screenshot was for the OP and Jeremy's note that in that case it seemed to be hanging on files not related to VST's at all and I have seen some silly things over the years such as people just setting their c:\ drive as a VST location so KK has to scan every .dll file on your system which is ultimately going to cause a problem.
However I have seen far more reports of this issue just in the last few months than I have for years before so it seems more an issue with how the plugin scanner works these days which is why I just cannot use KK V3, have never had an issue with KK V2 in this regard and I have well over 600 plugins over VST2 and VST3 without a single scan issue
0 -
OK. cheers for that Jason. I will have a look later tonight at the offending plugins when i am finished at college.
loaded KK 3.3.4 on last night in frustration and everything worked ok. Even added my freelance NKS location in user and they all worked ok.
Don't understand how Maschine 3 is working and loading ok where komplete kontrol doesn't with the same location folders set up
0 -
OK, so, the avox choir was loading an instance of code meter which crashed ableton and fl studio when i tried to load it. run the autotune central app and they are moving over to ilok so had to set it all up, now loads with no issues.
analog va2 and dune 2 loaded with no issues.
run the updates in waves and cleared the waveshell error.
solina asked to sign into my account n the air website and redirected me back
updated komplete kontrol in native access to 3.5
loaded with no issues 😍
Thanks Jason for pointing the errors out, convinced it was codemeter loading with Avox which was the culprit.
many thanks guys tanks for the help
0 -
Here you go also I removed those files that are non vst and still no joy and systematiclly rmoved the vst or dll that caused problems and still hangs no matter what vst it was I also reverted to 3.3.4 and it worked perfectly
0 -
Basically, it is always 1 step forward, 3 more back with KK. This is why I cannot update to V3 at all and stick to 2.9, too many issues and frustrations with V3. It is still (IMHO) completely Beta software because it is unfinished, lacking basic functions (that KK V2 has) and is struggling with stability, not something you expect from software that has been out for 10 years (even close to 2 years now with V3).
1 -
Yeah there are definitely issues in the latest release, always appears to be some issue. Honestly if you do not have a V3 keyboard i'd strongly suggest sticking to kk V2 for another 24 months maybe, buut at the moment if 3.3.4 is working, just stick to it and forget updating for a while, hopefully thehy have this ironed out in the next 3 years…
1 -
If you wish to have this looked into, please get in touch with our support here: https://bit.ly/NI_Support_All
1 -
support is non exsistent unfortunately and the support ticket process is not the greatest plus my issue is resolved by reinstalling the previous version this is the last screen shot taken before i uninstalled and installed 3.3.4 so as you can see any plugin it mostly hangs and my product is a KOMPLETE KONTROL M32 so dont know if they have to revisit the plugin scanner in KK 3.5.0
0 -
Hey all, back again. Just a quick update for you after sorting the errors with the plugins and installing 3.3.4 then kk 3.5 Initially got the software working but after running another plugin scan it still locks up after scanning all plugins and does not open, have to close the program down and when it reopens everything is there and working???
I will include the log file which does not have any errors apart from a NI one which is this :
Application: mixpanel start
Application: initialisation done
A software instance was not closed properly or is inoperative. Its IPC data has been removed.
[ERROR] Layout contradiction - height of Bar Footer is given at line Komplete/Dialogs/DialogBasicPanelStyling.txt:269 of the stylesheet but also computed automatically by styleBreadthXXX!!!
Skipped 1 duplicate messages..As you can see the issue has not been resolved :
John :(
0 -
What about if you deselect the VST2 option and rescan? Clutching at straws because this issue just doesn't happen in KK V2, it may crash during the scan but that is usually a sign of a bad plugin. Seems the scan is reaching the end and then just giving up almost like it cannot write to the drive (which I assume you have given KK full disk access)?
0
Categories
- All Categories
- 18 Welcome
- 1.7K Hangout
- 67 NI News
- 887 Tech Talks
- 4.6K Native Access
- 17.7K Komplete
- 2.2K Komplete General
- 4.8K Komplete Kontrol
- 6.3K Kontakt
- 1.1K Reaktor
- 407 Battery 4
- 916 Guitar Rig & FX
- 464 Massive X & Synths
- 1.5K Other Software & Hardware
- 6.3K Maschine
- 8.1K Traktor
- 8.1K 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