Loading Issue - Could not load Plug-in

JonPR · 2024-06-11T23:03:12+00:00

There was an error rendering this rich post.

I'm getting this message from Komplete Kontrol in Reaper. I've followed all the solutions given here - https://support.native-instruments.com/hc/en-us/articles/210276165-Komplete-Kontrol-Error-Message-Loading-Issue-Could-not-load-Plug-in-Windows - twice. Everything seemed to have scanned correctly, but it still doesn't work. (The "Scan Library" button flashes up a window very briefly.)

Any ideas?

Find more posts tagged with

Accepted answers

JesterMgee

If things work in the standalone version of KK but not in Reaper, that suggests likely the plugin DLL file is older than the version of KK.

This can happen with the VST2 version of KK because you can manually set an install path for the VST2 plugin but when you update the same install path is not used by default.

Confirm you are using the VST3 version of the plugin in Reaper and not VST2 then also, check the version of the plugin by clicking the KompleteKontrol logo and compare to the version of KK standalone.

If you open the preferences and view the plugin tab, does it show plugins listed? The "Cannot Load Plugin" is a rather useless message since it could have been designed to actually offer some info, such as WHAT damn plugin it cannot load but we can't expect too much. If the plugin you are trying to load is not listed in the plugin list this is what causes the error and if it's only in the VST version of KK and not standalone that is usually an issue with version mismatch between the plugin DLL files and the actual installed software version.

JesterMgee

https://community.native-instruments.com/discussion/comment/159649#Comment_159649

So the latest version installed from Native Access will be KK V3 and that does not offer a VST2 version for DAWs anymore, only VST3. The fact you are loading v2.6 in Reaper means you are loading a VST2 version which is now no longer compatible.

My suggestion is usually to just roll back to at least KK V2.9 as 2.6 was quite old but if you want to stick with the latest V3 version you need to delete that VST2 plugin and switch to using the VST3 version. Just keep in mind that this whole thing was VERY poorly done and any projects you created in the past using the VST2 version of KK wont load anymore and there is nothing you can really do there other than roll back anyway then manually update your projects to V3. This is why I suggest if you don't own a MK3 keyboard, just save yourself the headache and uninstall V3 of KK and reinstall V2. Otherwise, you have some figuring out to do.

https://community.native-instruments.com/discussion/17840/komplete-kontrol-2-9-6-last-vst2-supported-version

All comments

JonPR

Just adding to the above. KK works fine as a standalone. Just won't work as a plug-in FX in Reaper.

garg

hi i am new here how are you doing

JesterMgee

If things work in the standalone version of KK but not in Reaper, that suggests likely the plugin DLL file is older than the version of KK.

This can happen with the VST2 version of KK because you can manually set an install path for the VST2 plugin but when you update the same install path is not used by default.

JonPR

Thanks for your reply. Just a quick response for now (late night here!), I may get back tomorrow.

Clicking the logo (in the plug-in) says version 2.6.0. The standalone is 3.2.1! So I guess that's it?

Under Preferences in the plug-in, the Plug-ins window is blank. (Four folders are shown in the Library window).

In Reaper, Komplete Kontrol is shown as VSTi - not VST2 or VST3. I re-installed KK from NI Access just a few days ago, as part of my attempts, so I assumed I had the right version - I suppose I also assumed the standalone and plug-in were one and the same! - or at least that both would be installed when I updated….

Further tips on what to do next? (I looked up downloading Komplete Kontrol, and the site was confusing. It mentioned a "New" tab on Native Access, and there is no such tab on my version; and the download button downloaded Native Access, not Komplete Kontrol…)

JesterMgee

https://community.native-instruments.com/discussion/comment/159649#Comment_159649

https://community.native-instruments.com/discussion/17840/komplete-kontrol-2-9-6-last-vst2-supported-version

JonPR

OK, thanks - I finally solved it. Found the old dll and deleted it, and re-scanned the plug-ins on Reaper - I had already tried that, but I hadn't cleared the cache first. That fixed it!

Thanks again (both), and it seems I was just being a little dumb… 🤔

Quick links

Unanswered questions