How to fix Komplete Kontrol VST2 after 3.0 update ?

Ludae

Hey everyone,

I just made an update of a few things on Native Access 2 and now Komplete Kontrol is quite broken :

• The standalone app works (3.0)
• The VST3 plugin works in Ableton (3.0)
• But the VST2 plugin does not work anymore (stuck in 2.9.4) and shows the error message "It looks like your library is currently empty. Please click the button below to scan for your instruments and samples." (doing so does not solve the problem)

Problem is, it also affects all my older projects which means all instruments are now "unloaded", so i have lost all parameters within presets and if i do not remember what instruments i used i am screwed.

Do you have any idea if there are things to do to fix the VST2 version ? I'm fine with using vst3 for my newer ones, but i'd appreciate not losing all my previous work.

Thanks in advance

Kaiwan_NI

Hi all, a hotfix to address the VST2 issue is now available on Native Access.

As mentioned in the release notes, VST2 will be phased out in the coming months so it's recommended to switch to VST3.

Ludae

Edit :

I tried downgrading back to Komplete Kontrol 2.9.4 and everything worked again, from opening the VST2 plugin to having all my parameters and instruments loaded in older projects

In case anyone needs it, here's a link where you can download the 2.9.4 installer : https://community.native-instruments.com/discussion/17363/komplete-kontrol-s-series-mk1-keyboards-end-of-life/p1

Kaiwan_NI

Hi @Ludae there's indeed an issue with KK3. It removed VST2 components :( A fix for this is coming very soon.

chk071

And I thought KK3 was VST3 only.

It uninstalled the VST2 here when I upgrade to KK3.

Kymeia

https://community.native-instruments.com/discussion/17754/how-to-fix-komplete-kontrol-vst2-after-3-0-update

See my post here:

Feedback - Komplete Kontrol 3.0

Basically if you want to run both KK2 and KK3 on the same system you have to take into account the fact that:

a) they have separate databases (which is good as it means you don't lose anything you had before)

b) but they use the same plugin scanapp (which can be a problem as the scanapp is what enables KK to scan and integrate new or updated plugins).

Your KK VST2 plugin is trying to use the scanapp that was installed with KK3 but that version of the scanapp is only compatible with KK3 which is why you can't update the plugins in the VST2 version. If you want to run the VST2 version you need to reinstall the KK2.9.6 version first, then allow that version to rescan the plugins and that will fix the problem with KK VST2.9.6. If you then still want to update to KK3 and run that alongside the VST2 of 2.9.6 you need to backup both versions of the scanapp and switch between them as I suggest in the other thread, but it's not something I would recommend to users and I am sure NI would say this is not recommended.

Kaiwan_NI

Hi all, a hotfix to address the VST2 issue is now available on Native Access.

As mentioned in the release notes, VST2 will be phased out in the coming months so it's recommended to switch to VST3.

rdalcroft

No its not!!

After updating I still have no VST2.dll in my VST folder. Do I have to install Komplete Kontrol 2 first then update? Could you not have added the Vst2 in the update file???

Kymeia

https://community.native-instruments.com/discussion/comment/103010#Comment_103010

What the hotfix does do though is address the problem I identified with the VST2 and VST3 using the same scan app, even though they were incompatible, so it does now make it easier to have KK2 and KK3 on the same system

rdalcroft

OK, but they could have made it easier. I just had to downgrade, to get the VST2 file, then Upgrade,

There are issues though, Ableton does not like the VST2.dll as it crashes their plugin scanner??