I've built a couple of Kontakt instruments for my personal use, but even though I haven't move any folders or change any of their names I still get the missing content error. So far, the only I've found to avoid this problem with by exporting as a monolith instrument, which works for my personal use but it doesn't work for commercial releases that require access to UI elements in an external folder.
How do I make sure that my customers won't get any missing content error when using my Kontakt 5 instruments?
By the way, I use the latest version of Kontakt 5, it's fully updated.
Kontakt 5: how to avoid missing content error?
-
- KVRAF
- 4314 posts since 31 Oct, 2004
-
- KVRAF
- 24447 posts since 7 Jan, 2009 from Croatia
Make sure you have "absolute paths" checkbox disabled when saving your instruments.
Also, your UI elements should not be in Resources folder for a commercial product, they should be packed back into the NKR monolith, which is pretty simple to do by going to Instrument Options and overwriting the existing NKR. But yes, NKRs won't work with NKI monoliths because the path to NKR is stored as absolute, so it won't work on other machines.
My suggestion is to commit to the folder structure of Kontakt Player libraries: Instruments folder, Samples folder, NKR can be either outside or inside Samples folder. All of this in one overarching folder that is your library. Once you have everything there, do a batch resave on the whole library folder (just make sure that that "absolute paths" checkbox is disabled when you try saving an NKI). That should sort things out!
Also, your UI elements should not be in Resources folder for a commercial product, they should be packed back into the NKR monolith, which is pretty simple to do by going to Instrument Options and overwriting the existing NKR. But yes, NKRs won't work with NKI monoliths because the path to NKR is stored as absolute, so it won't work on other machines.
My suggestion is to commit to the folder structure of Kontakt Player libraries: Instruments folder, Samples folder, NKR can be either outside or inside Samples folder. All of this in one overarching folder that is your library. Once you have everything there, do a batch resave on the whole library folder (just make sure that that "absolute paths" checkbox is disabled when you try saving an NKI). That should sort things out!
-
- KVRAF
- 24447 posts since 7 Jan, 2009 from Croatia
-
- KVRAF
- Topic Starter
- 4314 posts since 31 Oct, 2004
Thank you for your answer, it helps a lot! I've worked with Kontakt on and off and never got the hang of it. Hopefully, I'll get comfortable with more practice and active learning.EvilDragon wrote: Tue May 12, 2020 6:58 am Make sure you have "absolute paths" checkbox disabled when saving your instruments.
Also, your UI elements should not be in Resources folder for a commercial product, they should be packed back into the NKR monolith, which is pretty simple to do by going to Instrument Options and overwriting the existing NKR. But yes, NKRs won't work with NKI monoliths because the path to NKR is stored as absolute, so it won't work on other machines.
My suggestion is to commit to the folder structure of Kontakt Player libraries: Instruments folder, Samples folder, NKR can be either outside or inside Samples folder. All of this in one overarching folder that is your library. Once you have everything there, do a batch resave on the whole library folder (just make sure that that "absolute paths" checkbox is disabled when you try saving an NKI). That should sort things out!