Suddenly vst plugins not loading in KK3?

holonology

Hi folks, I may have caused myself an issue and wondered if anyone else has had the same problem.

So I recently did a rescan of plugins in kk3. I'm on an M1 Mac, and have had one or two issues with individual plugins not quite working as expected before today. However, for the most part, I was able to use KK3 to load any and all plugins.

Since the rescan I now get the "may not support Apple Silicon or VST2 to VST3 migration" message when loading NKS plugins (Arturia, Uhe, AAS etc) but this time it happens on literally any non NI plugin. All NI plugins load fine. The plugins themsleves are all working, and they do load if I select a VST3 via the dropdown menu, so they are there. I should also say that the same plugins are working just fine in Maschine.

It seems like there's a disconnect between the NKS presets for all of them and loading the correct plugin. However, as I mention, this had been working without issue, so I'm not 100% sure how this has happened.

I've deleted the database and rebuilt it in KK3 also.

Can anyone shed any light on anything else worth trying in terms of resetting things? Anyone resolveed this on their own?

holonology

I think we have an answer. Will leave this thread here in case others find it useful.

I followed the process in this article, as well as the steps above:

https://support.native-instruments.com/hc/en-us/articles/360000826178-Komplete-Kontrol-Error-Message-Loading-Issue-Plug-In-not-found-Please-open-the-standalone-application

What cleared this for me was, deleting the whole KK files (not just the DB) then rebuilding in standalone. From there, open in the DAW and then rescan in the DAW. That did the trick in the end.

Phew. Was beginning to think I was losing my mind there!

Kymeia

This can happen sometimes if someone does a rescan in Rosetta mode for some plugins (esp uhe) as they adapt to the mode they are in when initialised by the scan. Make sure you are not in Rosetta mode and do a full plugin rescan

holonology

Thanks @Kymeia - let me check that - I've avoided Rosetta entirely but you can never be sure.

holonology

I think we have an answer. Will leave this thread here in case others find it useful.

I followed the process in this article, as well as the steps above:

https://support.native-instruments.com/hc/en-us/articles/360000826178-Komplete-Kontrol-Error-Message-Loading-Issue-Plug-In-not-found-Please-open-the-standalone-application

What cleared this for me was, deleting the whole KK files (not just the DB) then rebuilding in standalone. From there, open in the DAW and then rescan in the DAW. That did the trick in the end.

Phew. Was beginning to think I was losing my mind there!