Bogus error message when trying to load NKS presets

mickeyl

I'm on macOS w/ Apple Silicon. Loading all VST3 plugins works fine, as long as I don't try to recall an NKS preset. Then I'm greeted with

which sounds, uhm, wrong to me, since ZebraHZ is indeed loading very nicely, just not by using an .nksf preset.

What's wrong here? This renders all the NKS libraries broken for now, since no preset can be recalled.

Kymeia

This is why:

https://community.native-instruments.com/discussion/7484/komplete-kontrol-2-8-0-update-m1-native-compatibility-vst2-to-vst3-migration-compatibility

Basically NKS presets that were saved with the VST2 version are trying to load the VST2 version, but as VST2 is no longer supported in the Apple Silicon Native version (and many VST2s are not Apple Silicon native in the first place) you get this error for some plugins (not all by any means). Some plugins do have the ability to load data from a project made with the VST2 version into the equivalent VST3 - this is called plugin 'migration' but while NI hosts like KK and Maschine do support this, plugin developers also need to enable it and in some cases also fix incompatibility issues between the VST2 and VST3 versions (such as automation params that don't match up). This will take time unfortunately and this is not really something NI can do much about other than provide support to those developers. I have started a list of apps plugins and developers that do support migration here - it is certainly not the case that all NKS libraries are 'broken' many plugins do support migration and in the meantime those that don't support it still load the NKS (and VST2) fine if KK is run in Rosetta mode:

https://community.native-instruments.com/discussion/7554/plugins-that-support-vst2-vst3-migration-a-list

And also a number of us have been making working VST3 versions of NKS templates and presets in the NKS User Library thread here:

https://community.native-instruments.com/discussion/332/nks-user-library#latest

Kymeia

This is why:

https://community.native-instruments.com/discussion/7484/komplete-kontrol-2-8-0-update-m1-native-compatibility-vst2-to-vst3-migration-compatibility

Basically NKS presets that were saved with the VST2 version are trying to load the VST2 version, but as VST2 is no longer supported in the Apple Silicon Native version (and many VST2s are not Apple Silicon native in the first place) you get this error for some plugins (not all by any means). Some plugins do have the ability to load data from a project made with the VST2 version into the equivalent VST3 - this is called plugin 'migration' but while NI hosts like KK and Maschine do support this, plugin developers also need to enable it and in some cases also fix incompatibility issues between the VST2 and VST3 versions (such as automation params that don't match up). This will take time unfortunately and this is not really something NI can do much about other than provide support to those developers. I have started a list of apps plugins and developers that do support migration here - it is certainly not the case that all NKS libraries are 'broken' many plugins do support migration and in the meantime those that don't support it still load the NKS (and VST2) fine if KK is run in Rosetta mode:

https://community.native-instruments.com/discussion/7554/plugins-that-support-vst2-vst3-migration-a-list

And also a number of us have been making working VST3 versions of NKS templates and presets in the NKS User Library thread here:

https://community.native-instruments.com/discussion/332/nks-user-library#latest