One or more Kontakt instances cannot be recalled correctly msg hangs Ableton

JimWalsh · 2024-12-17T18:47:29+00:00

There was an error rendering this rich post.

JimWalsh

when trying to open a project I get the message:

One or more Kontakt instance cannot be recalled correctly, perhaps de to missing content.

Please open any Kontakt instance in your host, Komplete Kontrol or Maschine to resolve the issue.

The OK button is unresponsive and Ableton hangs.

has anyone resolved a similar issue?>

Find more posts tagged with

Comments

haridas

Im getting the same issue since updating Ableton.

EsbenA

This is happening to me as well. Can't load any projects where it happens. Any news on how to solve it?

Burt Blackarach

I having the same issue. Won't let me select OK in live 12. Live 11 it allows me to select Ok. This is brutal

MorrisEd

Open Native Access and address any “Repair” notifications. You’ll either be prompted to relocate or reinstall the missing library. After doing that, follow the instruction at the link below to reset your Kontakt and Komplete Kontrol libraries. Last, open Kontakt standalone and let the program rescan your library. It happens automatically but takes some time. Repeat for Komplete Kontrol.

https://support.native-instruments.com/hc/en-us/articles/209554889-My-Komplete-Kontrol-Browser-is-Empty-or-Incomplete

JimWalsh

this didn't help as there is no repair notifications and no missing libraries.

I uninstalled and reinstalled Kontakt and it still gave the same message.

Vocalpoint

Judging by the reports - this feels like an Ableton issue with a new update.

I believe Jeremy_NI has engaged a few resources to look into this.

myrmur

Same here. That alert window always used to appear when opening some projects that involve specific Kontakt libraries because I moved some Kontakt patches into custom folders: still I was always allowed to click "OK" and then easily relocate the missing patches after the project opening. Now I can no longer click on OK: only thing I can do is forcing Live to quit.

dunego

Same here, can't open a project that I worked for the last 3 days and have to finish tonight. It freezes ableton, I have to force quit to do anything. Then I load another project that uses kontakt and it works fine. Just that specific project won't work. The last one.

Now this is crazy: I put kontakt 8 out of the plugins folder to open the project and maybe do something, and the project open but it don't say it has a missing plugin, so I go look at the 3 tracks that has kontakt as a vsti, and simply they now have a massive vsti instead LOL

animalplanet

This affected me as well. I lost 6 hours of great work : (

I'm hoping they fix this soon.

DunedinDragon

Generally speaking any time this happens to me it's due to the NI library reference being used in Ableton is wrong or not there. It's sometimes because I've gotten something messed up in the library location reference in Native Access. Once I fix the reference in Native Access everything works fine. The first test is to try and launch the library outside of the DAW directly from Kontakt or KK then fix the reference in the DAW project.

BPM Studio

I'm just facing exactly the same problem and it's driving me completely insane! Please, PLEASE fix it! I used to work on many different projects that included Kontakt (6) plugin. After updating to Komplete 15 and Ableton 12 I can't open them. Progress lost. Projects don't crash only when opened via ableton 11 but even then Kontakt confuses the databases and says my instruments are demo versions, although I've bought them.

Vocalpoint

https://community.native-instruments.com/discussion/comment/202793#Comment_202793

You might need to review this thread.

Kontatk 7 Recalling - Can't Click OK - Ableton Live 12 - macOS Sequoia - Page 3 — Community

And this post:

sublimelobc

I've had this same issue, it only affects certain Kontakt instruments for me (Noire, Analog Dreams and a few others). I found that the instruments that don't work don't show up in my browser in Kontakt 6, but I have some instrument racks saved with Noire and these other non working instruments saved inside, and when I try to open them is when I get the freezing.

When I open up Kontakt 6 from as a VST and not inside an instrument rack, I don't see these instruments. I've tried trashing and rebuilding the Kontakt database, still no luck.

There is one thing that works. If I open the Kontakt 7 Player, I can see all instruments in the browser AND they work! I'm wondering if the issue is specific to Kontakt 6, I don't have a newer version of Kontakt to test my theory, what version of Kontakt are you guys using?

sublimelobc

As an update to my prior post, I have found that if I try to manually browse to the instruments that aren't loading into the Kontakt 6 library, upon selecting any of the non working instruments I get the message "Your version of Kontakt is good old to load this file. Please update to the latest version."

This seems to obviously be an issue on the NI end, not Ableton as some others have suggested. Please NI, look into this, because all of these instruments worked fine with Kontakt 6 when I purchased Komplete, and this is a version conflict. I shouldn't have to update my version of Kontakt to be able to use software I have already paid for, and that worked fine until a NI product update seems to have killed some of the instruments.

My Instruments that stopped working are Noire, Modular Synth Icons, Lofi, and Hybrid Keys.

Vocalpoint

https://community.native-instruments.com/discussion/comment/206790#Comment_206790

If you are seeing the library too old message - this due to ALL Kontakt libraries being updated back in Fall 2023 to require Kontakt 7.6.1 ( or higher).

Do remember Kontakt 6 is long since retired but you can get your libraries back in shape by visiting the Kontakt forum. Find the pinned post about older Libraries not working. There are links in there to get the older version that will work with K6

After you fix the libraries that are giving you errors - if you are intent on staying with K6 - remember to never - ever- go into Native Access and “update” these libraries or you will be right back in this mess.

Quick links

Unanswered questions