1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Kontakt 5.4 VST version doesn't load Session Strings Pro

Discussion in 'Technical Issues - KOMPLETE (Archive)' started by Erdertainment, Oct 18, 2014.

  1. Erdertainment

    Erdertainment New Member

    Messages:
    7
    Hello community,

    I recently tried to open Session Strings Pro in Kontakt 5.4.1.211 VST (I tried both 64 and 32 bit), but all I got was a message box telling me this Kontakt version is too old (ironically, it is the newest version), I should close Kontakt and update it in the service center (where no update is available). In the standalone version though, everything works fine, no complaints. But the standalone version is pretty useless as I can't use it with Cubase. Please fix that error.
    If you need any more informations about my system or something, please let me know.
     
  2. Erdertainment

    Erdertainment New Member

    Messages:
    7
    After some research, I found out my version is still on 5.3.something, but the service center displays it as 5.4.1.211. The folder where I download my updates to is also empty. What can I do to fix that?
     
  3. DarkStar

    DarkStar NI Product Owner

    Messages:
    2,089
    Double-check the versions of your Kontakt standalone program and of the plug-ins. I'll guess that the update installer put the new versions in another folder.

    Search your whole disk for "Kontakt" (without the quotes) to see what's where. Let us know the result.
     
  4. jamesL

    jamesL New Member

    Messages:
    1
    I was in the same boat. DarkStar is correct (unless your issue is somehow different).

    Installers put the plug-in .dll files in "Program Files/Native Instruments/VSTPlugins 64 bit" (and a matching "32 bit" folder if you installed them).

    Those needed to be (in my case) copied-and-replaced in the "Program Files/Steinberg/VSTPlugins/Native Instruments" folder (or wherever you may have Cubase looking for your VSTs).

    Then all is well.
     
  5. Erdertainment

    Erdertainment New Member

    Messages:
    7
    Nope, that didn't do it for me. I did exactly what DarkStar adviced me to do, but everything I could find was the .dlls (by the way, I checked the versions number in the properties - 5.4.1.211 too) and the NI EULA. I also specified the folder the VSTs should be installed in, so that couldn't be the matter at all.
    @jamesL the folder you told me to search for doesn't exist, this is probably because of the install folder specification I did. I am completely sure the 5.4.1.211 VSTs are in my VST folder, it has to be a bug.
     
  6. DarkStar

    DarkStar NI Product Owner

    Messages:
    2,089
    Where did you see the "5.3.something" version number?

    I would also raise an NI Support Ticket for some one to one help.
     
  7. Erdertainment

    Erdertainment New Member

    Messages:
    7
    I can see the 5.3.XYZ when I open up the Kontakt VST and click on the "Kontakt" in the top right corner (that yellow box that contains credits, the serial key and the version number).
     
  8. DarkStar

    DarkStar NI Product Owner

    Messages:
    2,089
    OK, so the VSTi loaded into your DAW is NOT v5.4.1.211. I can only think that there are multiple copies of the dll files somewhere.

    If I were in this position, I would find those v5.4.1.211 dll files and copy them to wherever my DAW host is scanning to load those v.5.3XYZ dlls. But, tread carefully.
     
  9. Erdertainment

    Erdertainment New Member

    Messages:
    7
    ...and exactly that is the problem. Every DLL file with "Kontakt" in its name (there are only three) is marked as version 5.4.1.211, though they are displayed as 5.3 in my DAW. Since I don't have any other Kontakt DLLs on my drive, I guess a software error or something occurred/update failed etc.
     
  10. Erdertainment

    Erdertainment New Member

    Messages:
    7
    Hello,
    I just wanted to say it works now. I don't exactly know what I have done to make it work, but well... it is fully functional now.
    Thank you, DarkStar, for your friendly support :D
     
  11. DarkStar

    DarkStar NI Product Owner

    Messages:
    2,089
    o_O Good oh, I think :thumbsup: