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

Can't open Kontakt patches inside Kore 2

Discussion in 'Technical Issues' started by chico jones, May 1, 2011.

  1. chico jones

    chico jones Forum Member

    Messages:
    261
    When I open up Kontakt inside Kore 2, then try to open up a Kontakt patch from the Kontakt Library/Database, I get the following message: "The patch could not be loaded (unknown error)".

    Same thing happens with the Kore 2 VST or standalone.
    Kontakt by itself will open the patches with no problem.
    I don't get the error if I open a Kore preset that uses Kontakt.
    The problem is trying to access Kontakt patches when Kontakt is opened inside Kore.

    This didn't used to happen. I've opened plenty of Kontakt patches within Kore in the past. Any idea what's going on?
     
  2. losan

    losan Forum Member

    Messages:
    627
    That's because the "internal" plugins Kore uses aren't in sync with any updates
    to the "regular" plugins.
    The version of Kontakt 4 inside Kore is still at 4.1.1,
    while the latest release of Kontakt is at 4.2.2 already.
    Any patch created with the newer version won't load in the older version,
    and you get this error message.

    There's a workaround for it: copy the newer plugin versions of Kontakt 4
    from your regular plugin folder over to the pluginfolder of Kore,
    overwriting the versions there.
    The path to that folder is (on Win):
    C:\Program Files\Common Files\Native Instruments\Kore 2\PlugIns

    if you're on an x64 system it's ...\Program Files (x86)\... instead.

    Cheers
     
  3. chico jones

    chico jones Forum Member

    Messages:
    261
    Cool, that worked. Thanks alot for the reply.
     
  4. a1mixman

    a1mixman NI Product Owner

    Messages:
    751
    Yes, thanks losan! Very cool work around.
     
  5. Starsky

    Starsky NI Product Owner

    Messages:
    18
    Wow! Hey that worked! But I can't believe that the NI updaters don't do this automatically. That's so laaaaaame, NI! Wake up, Berlin boys!
     
  6. chico jones

    chico jones Forum Member

    Messages:
    261
    Yes, it is ridiculous that the updaters didn't do this. Even more ridiculous that an update hasn't come out since this thread found the solution and an easy update.
     
  7. JPaul23

    JPaul23 NI Product Owner

    Messages:
    930
    It doesn't work for any of the other NI vst's either. Bloody ridiculous....
     
  8. Kymeia

    Kymeia NI Product Owner

    Messages:
    6,268
    They have in the past tended to update Kore after several updates to its various engines after a period of testing to ensure all the updates are compatible with Kore - and that would include the engine updates. It probably isn't a good idea for them to release individual updaters that automatically install updates into the Kore VST engine folder without doing that and generally- although the method Losan described is well established and I use it myself - NI have warned in the past that there could also be unintended consequences and that therefore it is an unsupported workaround.

    The problem here is there is always going to be some unevenness in the development process for so many different plugins but Kore of course brings them all together. So what should NI do? Delay the release of all updates until they have been thoroughly tested with Kore, and if necessary Kore updated too, or release them when they are ready (which then also subjects them to some field testing) and then update Kore? Neither way is perfect and particularly when there have not been updates to Kore in a good while this situation was inevitable but on balance I think their approach makes the most sense, even though they do really need to get back to work on Kore now.
     
  9. chico jones

    chico jones Forum Member

    Messages:
    261
    Well now I guess we know why the Kore dlls didn't get updated for the last Kontakt, Reaktor, Guitar Rig updates.

    Using this method seems to have worked for all three, but backup the old dll's just in case. Thanks again Losan.
     
  10. nielsdolieslager

    nielsdolieslager NI Product Owner

    Messages:
    2,122
    I also use this workaround. I can load my new Kontakt patches in Kore. But... more then half of the original koresounds can't open Kontakt for editing...

    How to solve that?
     
  11. chico jones

    chico jones Forum Member

    Messages:
    261
    I just tried out a few Kore/Kontakt patches. Just a quick test, but they all opened up Kontakt and were editable in Kore. What are some of the patches that you've had the problem with?
     
  12. chico jones

    chico jones Forum Member

    Messages:
    261
    Hmmm, maybe this is the problem? Kontakt patches that use other effects are often set up this way. In the picture the "Made In Rock" Kore/Kontakt patch is loaded. The first arrow points to the Kore sound, it contains the Kore controls. But you can't edit the Kontakt patch from here. You have to scroll down to where the Kontakt patch is located (second arrow). Click it and the "edit" tab will appear.

    P.S. You can't edit that Guitar Rig effect even if you have Komplete, because it uses Guitar Rig 3, not Guitar Rig 4. Grrrrrr. I hate that.
     

    Attached Files:

  13. nielsdolieslager

    nielsdolieslager NI Product Owner

    Messages:
    2,122
    Nope, that's not the problem. If I open "Made in Rock" I can't open Kontakt, doesn't matter where I click. I guess it's because of that workaround.
    I've had a long discussion with NI's support about how foolish that GR3/GR4 problem is and I got a free NFR version of GR3 2 months ago. You can try too :)
     
  14. chico jones

    chico jones Forum Member

    Messages:
    261
    I don't know what the problem is, but I don't think it's the workaround. I can edit all Kontakt patches in Kore after implementing the workaround. Double check and make sure the Kontakt.dll for both Kontakt and Kore are the same? You can check the date and filesize.

    Good luck and thanks for the GR3 info.
     
  15. nielsdolieslager

    nielsdolieslager NI Product Owner

    Messages:
    2,122
    Ha! It turned out I had moved the Kontakt.vst files from my Apple's shared audio vst folder to Kore's vst folder, hadn't copied them.

    I use Logic, so Kontakt worked anyway :)

    So thanks for having me check :)