nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why is Komplete Kontrol interacting with seemingly unrelated software at Startup?

Vocalpoint

Having finally migrated to a new S61 MKIII and starting to use Komplete Kontrol v3.5.x - I am seeing some odd behavior with several bits of "accompaniment" software that is called during KK usage.

Today - I simply fired up KK v3.5.4 (standalone) to examine my settings/prefs/etc and while the app fired up fine - and exited fine - in Event Viewer after the fact - I see these crash entries scattered around:

There are five of these entries in total.

But what is very odd is that the "faulting" modules (Highlighted) - are NOT part of my Komplete Kontrol paths or any scan inclusions whatsoever:

I am not even using VST2 plugins at all in this build - yet Event Viewer is recording crashes as the ni-plugin-info.exe file (presumably called during KK startup) insists on going out and scanning these bizarre paths and then decides to crash on files I do not even use (like bx_subsynth.dll) which is a VST2 plugin.

Before I enter a ticket - does anyone know what is going on with this scanner (ni-plugin-info.exe) and how it is getting instructions to scan all this unrelated crap?

Is there a database file I need to delete and rebuild?

Anyone else has seen anything like this?

Find more posts tagged with

Komplete Kontrol SW

Komplete Kontrol Keyboards

Comments

mykejb

Most likely the DLL is a support DLL that's loaded from the VST3 rather than a VST2? The path it's being loaded from isn't the default path for the UAD VST2 installs, although I guess you might have changed it?

Vocalpoint

https://community.native-instruments.com/discussion/comment/266922#Comment_266922

That's what I first thought - but I specifically set my KK prefs at first install - being very careful to remove all paths that do not matter and especially to not allow ANY VST2 - which is very noticeable with the *.dll file extension.

AND - every single UAD plugin is unchecked in the KK Vst Plugins area:

The path that is being referenced for that UAD bx_subsynth.dll (which IS on the machine as part of the annoying default UAD-2 install routine which one cannot modify) - but that location - has zero to do with anything whatsoever. It is 100% ignored system wide.

Even my default VST2 path (that is there as a catch-all) is specifically set to C:\Program Files\VSTPlugins.

So why this ni-plugin-info.exe is somehow going into:

C:\Program Files\Universal Audio\Powered-Plugins\UAD-2 Powered Plugins\UAD bx_subsynth.dll

And trying to scan this thing - is beyond me.

There should be no possible way for that EXE to even know this path is out there.

PoorFellow

https://community.native-instruments.com/discussion/51526/why-is-komplete-kontrol-interacting-with-seemingly-unrelated-software-at-startup

From personal experience when programming then I know that no error information that you are served on a list is more accurate than the intelligence of the original sub-routine programmers error catch routines allow and this will be even more amplified if there are any sources of lack of accuracy built in into the OS itself.

UAD in particular in my opinion have a cr*p attitude towards how plugin scanning is supposed to work and in my experience then a scan of their plugins among other triggers their client software to run if installed why I have uninstalled their client software and uninstall it every time that I am done installing what needed installing.

In my opinion it is entirely possible that it could be something built into third party software that sends the KK software on what appears to be a stray path where it does not belong. The fact that the "ni-plugin-info.exe" is listed as faulting application could possibly mean nothing more than the scan app initiated the whole chain of events and that we are served the result without any information about the in-between chain of events.

(I think that you need to look deeper to get any conclusive results)

Kymeia

Scaler hosts VSTs so possibly it is that which is referencing those plugins?

mykejb

I think you'll find it's the architecture. UAD installs VST2 into subfolders in C:\Program Files\Steinberg\VSTPlugins\Universal Audio. VST3 are installed into subfolders in C:\Program Files\Common Files\VST3\Universal Audio. The actual audio processing functionality is a set of DLLs in C:\Program Files\Universal Audio\Powered Plugins\UAD-2 Powered Plugins.

When you load the bx_subsynth.vst3 DLL from VST3 folder that in turn loads C:\Program Files\Common Files\VST3\Universal Audio\Special Processing\UAD bx_subsynth.vst3\Contents\x86_64-win\UAD bx_subsynth.dll so what you're seeing is a bug in the processing functionality.

There's no 'client software' being started as the faulting plugin is UAD-Powered, not UAD-Native.

PoorFellow

There's no 'client software' being started as the faulting plugin is UAD-Powered, not UAD-Native.

I never wrote that that was in play here and I never meant so , I only used it as an example !

Vocalpoint

https://community.native-instruments.com/discussion/comment/266932#Comment_266932

Agreed.

I think I read somewhere a while back the Universal Audios "VST3" programming skill was that of a 10 year old and instead of actually coding correct (to actual SDK spec) VST3 plugins - they simply laid down a series of bogus VST3 "shortcuts" in the VST3 folder that lead right back to their tired old VST 2 plugins.

That said - I still did not allow Komplete Kontrol to scan ANY UAD plugins whatsoever - so the fact that these are still being picked up by that ni-plugin-info.exe app is a total mystery in itself.

I thought that a checkbox ON in the KK VST Plugins area - means "scan me" and a non-check = "ignore me".

mykejb

Not really … it's a "Don't show in the list" rather than "don't scan". It's catch-22, needs to be in the list so you can exclude it. When I was in the UA hardware plugin world years ago I had a batch file that deleted all the plugins that I didn't actually own cos having all the plugins listed got annoying.

Quick links

Unanswered questions