• SONAR
  • Kontakt Can't Find Instrument
2017/03/12 05:26:56
konradh
Apologies in advance if this post doesn't belong here but I am not sure if this is Kontakt, Sonar, or both.
 
Certain Kontakt instruments don't load with the project.  I get an error message that Kontakt can't find the instrument and I have to load it again.  This means I have to re-do any settings in the instrument.
 
This is not the worst problem in the world, but it is odd and inconvenient.
 
Any thoughts on this?
 
Note that this is using the full version of Kontakt 5.  The issue happens with some Native Instrument instruments and some third-party instruments.
2017/03/12 13:21:28
PeteL
Did you try a batch resave for those instruments? This can fix it if the paths to those instruments have changed in any way.
2017/03/12 15:31:37
sharke
I don't know if this is related, but sometimes I will load a project and be told that Reaktor can't find the ensemble that I'd saved with the project. Which is weird, because I've never changed their location. I have to manually point to it. And also last night Geist had this weird popup saying that a certain kick drum I had loaded onto a pad had "moved location," which it hadn't (it was still there on the pad and playing normally). So I did suspect that Sonar had somehow erroneously flagged those things as missing when they weren't - although I'm sure someone will tell me that Sonar has nothing to do with it and the plugins are at fault. 
2017/03/12 19:51:15
konradh
I have not done a batch re-save but will try that.  Thanks. (I don't remember how, but I've done it before and will figure it out.  I use Kontakt a lot.)
2017/03/13 12:29:29
dcumpian
The only reason I can think of is that you have moved the library files (or samples) since the last time the project was saved.
 
Dan
2017/03/13 17:33:21
zrapture
Hi there konradh,
 
I had the same issue that you did with a couple of Kontakt libraries, and I do a "batch resave" on all of my libraries to speed loading times. Assuming your samples are present, your disk isn't corrupt, you've already done a batch resave, etc.... in short, that nothing seems to have changed and that the behavior is sudden and unexpected, I recommend that you open a ticket with Native Instruments directly. They will walk you through resolving the problem, which can take up to two weeks, with emails going back and forth between you and Europe (so that's another timezone, plus some normal administrative delay).
 
The process look like this:
  • They send you a program which will run some telemetry on your computer. It doesn't report back directly to Native Instruments, but creates a file and it is up to you whether or not to send them the resulting file. I've reviewed the contents of some of these files, and you're not giving away any private info, passwords, etc. The file contains a number of reports to guide trained technicians in pinpointing your issue.
  • You send the file back to them, and wait a couple of days.
  • They send back a fix, which may be partial or full.
  • You implement the fix and test, then report back again. (Ticket closed, or still open?)
  • They give more direction, incrementally fixing the various settings involved.
If you're lucky, they pinpoint the problem the first time around. If not, it has been my experience that they can fix you within 3-4 email exchanges.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account