Komplete Kontrol presets won't open from instruments that do work

TEMAS

Hi. I recently updated to the latest KK 3.x and most of my instruments are now up and running, but even though they are working and I can open the instruments, in some case I can't open presets I that I saved from KK 2.x.

So for example - with U-he Diva I can open the VST3 instrument inside KK and I can open KK presets that use Diva, but with U-he Zebra 2 I can open the VST3 instrument inside KK I can NOT open KK presets that use Zebra 2.

It's similar with Arturia. Pigments VST3 KK presets open, Moog Modular V3 VST3 KK presets don't open. All Spectrasonics VST3 KK presets open, Reveal Spire VST3 KK presets don't open.

The reason, I presume, is that the KK presets that don't open were using VST versions of the instrument and when KK tries to open the presets using the VST3 version of the same instrument it can't translate the file (for instruments but not others).

My work around so far is to open KK standalone in Rosetta mode, open the KK preset using the VST version of the instrument, save the instrument settings as a file, open KK in Logic, open the VST3 version of the instrument, open the instrument file I just saved and then save and replace the KK preset. Then I can open the KK preset as normal.

Has anyone else found an easier way to make KK V3 read all presets files that were made from the VST versions of the instruments that are now VST3? Hope that makes sense. Thanks

Kymeia

You need to ensure you have the latest versions of the NKS for these plugins as they do all work with the VST3- once you have done that, go back into native mode then do a complete rescan of NKS then plugins

TEMAS

Hi thanks.

Just to clarify what I'm trying to do - I frequently use the KK GUI inside Logic Pro as a plugin host for all my NI and third party instruments. I find it a faster and more convenient way to search through all my saved favourite user instrument sounds than using Logic's Library panel. Whenever I add a new instrument to my collection I access it via KK and go through the presets, saving anything I like to my database in KK, which is all menu'd and tagged in a way that works best for me and then I never have to go back to any of the presets that came with the instrument that I have discarded.

I have all the latest updates for all my instruments and all the ones that are VST3 are working in KK and the presets that come with the instrument will load. The issue is that many of my saved user presets will not load. This is most likely because they were created when I was using an older VST (not VST3) version of the plugin inside KK, so KK is trying to open the VST version of the instrument that the user preset was saved from and not the new VST3 version of the instrument that is compatible with KK. I tried deleting the whole VST folder to try and force KK to open them with the VST3 versions, but that didn't work.

I just wonder if there's a way to convert KK VST user presets into KK VST3 user presets, without having to open them one by one to save them. Hope this makes sense. Thanks again

Kymeia

It shouldn’t matter as all these plugins support VST migration now. But if you keep moving between Rosetta and native that can cause confusion as they lock into the correct format when plugins are scanned. If you stay away from Rosetta and do a full plugin scan in the standalone KK it will usually reset them to migrate to the VST3 even if they were saved with the VST2

TEMAS

Thanks again. I really appreciate your assistance and it does give me hope that I'm doing something wrong, but the re-scan in Standalone native didn't work. Attached are two screenshots, one showing what happens if I try to load the preset and the other proving that I can manually open the instrument inside KK and then load the plugin's sound.

TEMAS

Just to clarify this test was done in native mode, not Rosetta. The instrument loads if I select instruments>VST3>Arturia>Modular V3, but the it won't load if I try to open a KK preset that uses the instrument.

Kymeia

It should work if all installed correctly and uptodate

It may be the NKS patches have not been updated by the Arturia software centre. Sometimes users have the install option for NKS disabled but don’t notice because silent install is selected in options. Try disabling silent install in ASC then when the first installer loads make sure third party content is selected, allow that installer to complete then you can turn silent installs back on and they will all follow the same options. Then rescan again