I’ve scanned the correct folder with Kontakt 8 as shown below but it never shows up within the standalone application and also doesn’t show up within the data folder that houses the json data for where the vst’s are located on my nvme.
Can’t really tell you what is wrong, but If it can be of any encouragement, Kontakt 8 does work fine on my Win 10 machine and Kontakt 8 is in the same folder that you indicated. Restart, re-scan plugins in MG3 perhaps ? Try from your DAW to see if it works ? Maybe someone else has a better idea on how to fix this.
Yes, I’ve done all of that. I even created a custom .json file and managed to get the plugin to show up, however when I go to activate kontakt 8 it just says unable to load plugin with no reference within the log file in the data folder. However, works just fine in Midi Guitar 2, which I’m currently using right now, lovin it.
If it’s not being recognized by the MG3 scan, perhaps try loading it inside a plugin host that can be loaded within MG3, like Kushview Element or Blue Cat AudioPatchWork. Or maybe try Komplete Kontrol? I’m not a Windows user, sorry. Just looking for temporary solutions to keep you moving forward.
FWIW, in macOS, a handful of recent NI plugins (Audio Units specifically) are not picked up by MG2’s plugin scan — only VST2 or 3 works. That said, I haven’t had any plug-in scanning issues in the MG3 beta for a good while now. E.g. Kontakt 8 loads fine.
In my experience, I’ve only seen “unable to load plugin” messages appear (again on macOS) when trying to load an MG3 preset/patch and the originally instantiated plugin is no longer in the MG3 database, usually in my case because I’ve completely removed a given plugin from the system.
I don’t think this is a common issue. Kontakt also works here and I’m afraid I don’t have any suggestions. Obviously it’s widely used and an important plugin, so if anybody else has issues with it, please let us know.