Komplete Kontrol loading issue, apple silicon or vst2 to vst3

jan.rifelj
jan.rifelj Member Posts: 6 Member
edited December 10 in Komplete Kontrol

Plug in/preset could not be loaded, as it may not yet support apple silicon or vst2 to vst3 migration.

Hi guys, I am getting this error on komplete kontrol standalone version. I ve just bought Mac mini M4 Pro..

Answers

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,081 mod
    edited December 7

    This is not a Komplete Kontrol error.

    You are using an old and unsupported VST2 plugin.

    Most probably, you used a VST2 version before, now you use a VST3 version but the presets were made with the VST2 version and the plugin does not support VST2 to VST3 migration.

    Note: It will be much easier to get answers if you provide real information (for example, which plugin is it? which version? etc etc.) instead of generic talk where no one can guess what you mean.

  • jan.rifelj
    jan.rifelj Member Posts: 6 Member

    No Plug in/preset is working.. I am getting this error for all of them

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,081 mod

    Maybe you use an older Komplete Kontrol version?
    Latest one is the 3.3.3, if you don't have it, please update.

    Or maybe you are still using the VST2 versions of the plugins?

    Check these options:

    Make sure the above 2 options are enabled at Preferences → Plug-ins → Manager:

    Make sure that this folder exists at Preferences → Plug-ins → Locations
    and in the very rare case that don't exist, add it:

  • jan.rifelj
    jan.rifelj Member Posts: 6 Member

    Version is 3.3.3. and everything is checked

    I just dont find check box "Use VST3 Plugins"

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,005 mod

    I'm not seeing Reaktor on there, do you have the VST3 version of that installed?

  • jan.rifelj
    jan.rifelj Member Posts: 6 Member

    Yes VST3 are working but others aren't…

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,081 mod

    If VST3 is working then you don't need the VST2 anymore,
    unless of those who do not support yet VST2 to VST3 Migration,

    So, keep VST2 only if:

    • there is no VST3 version at all, or
    • they do not support migration

  • jan.rifelj
    jan.rifelj Member Posts: 6 Member

    I think that only instruments from Kontakt are working and other dont.. Accelerating Spectrals and Soft E-Piano were one of my favorite and I am still geting same massege..

    And I dont get it why I dons see VST2 or VST3 folder

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,081 mod

    Kontakt Instruments are libraries… not VST's!

    If your problem is just with Kontakt instruments, then we are looking at the wrong direction since the beginning… nothing to do with VST.

    To make you understand, the only VST in this case is the Kontakt. Whatever you load inside it, are just libraries, sounds…

    …Jesus… have you ever read any manual? …at least the basics? 😳

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,081 mod

    ok, here is your problem:

    man, you have 3 Kontakts! 🙄

    Don't you remove the older versions when installing new?
    Are they all Players (demo versions?) or do you have a full version too?

    Anyway, in any case please remove the oldest Kontakt (which is the first, the one without a number and probably Kontakt 6)… unless if it is your only Full version.

    If all your Kontakts are Player versions, then keep only one! The latest, Kontakt 8

  • jan.rifelj
    jan.rifelj Member Posts: 6 Member
    edited December 10

    "…Jesus… have you ever read any manual? …at least the basics? 😳" Dude please!"

    u remove the older versions when installing new? First of all I asked politely if anyone can help.

    Second of all.. I did like 5 installations on windows and maybe with 3 different software (Cubase, Abeltone, ..) and there was no problem with VST or Komplete Control stand alone software.

    Now I have a new Mac and I have installed everything in the same way, by Native acces and everything updated up to date.

    There was no olders versions of Kontakt and no its not Demo I own a M32 and I have licensed Plug-Ins and I do not know why Native instruments installed 3 Kontakts on my computer

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,081 mod

    It is a common practice, since decades (at least among experienced users), the newer version always replaces the old.

    On most cases, there is absolutely no reason to keep the older software.

    There are exceptions of course, but they have to be somehow practical. For example you made a track years ago with version 6, which had a specific structure (or a unique sound) that they don't exist in the newer version, but this is very rare.

    Also, technically speaking, in many cases, keeping old versions, while there are newer ones installed, might confuse the system and cause problems.

    Back to your case, as i wrote, the "numberless" Kontakt,vst is the older one, most probably from Kontakt 6.

    Now, if you try to open a newer library with this version, you will get a problem, because they are incompatible! I believe this is a good reason to remove the old version, isn't it?

    Here is another case:

    Some Kontakt 8 new style libraries are made for Kontakt 8. If you try to open them, even with Kontakt 7, you will get an error. Some Kontakt 7 libraries can not work with Kontakt 6 etc etc.

    However, the newer application (Kontakt 8) of course can play all older libraries.

    So, now you came with a problem and we are try to find it and help you. After some research and based on what you wrote, we narrow it down to Kontakt instruments and not VST's. But if you had, for example, only the latest Kontakt version, most probably there would not be any problem at all!

    I believe you got an idea about what i mean. :-)

    Now, to finalize this: I believe that your problem is that, an older Kontakt version is trying to open a library created with a newer version. So, in order to fix things you have to remove the older version. For start, just move it to some other folder temporarily and try to open the plugin/library that didn't worked before.

    "Some VST working some others not"…

    It will be really helpful if you actually write the names of the problematic plugin/libraries!

Back To Top