Last modifiedby & filed under KSP Scripting (NI Kontakt) - Tutorials, KSP: Basics.

Never check “Absolute path” when publishing your instrument. Because with absolute paths, your customers/users are barely able to use your instrument. Learn more why…

save instrument 2

Absolute Paths

If “Absolute path” is activated Kontakt will always look for your files at the exact same position you stored your instrument, also when moving it to another location.

For example if you save your instrument to D:\My_Instrument\ and copy it to C:\Release Version\ Kontakt will still look for all resources at D:\My_Instrument\Resources\, D:\My_Instrument\MySamples\  and  D:\My_Instrument\MyResourceContainer.nkr.

You get the point. When publishing your instrument also your customer’s Kontakt will look for the files at your location which still is D:\My_Instrument\..

PROS

for your own purpose (developer environment) you can save samples, resources and the nki to different locations each, without reallocating your samples when moving your nki again to a another location. As an example you could store all your samples to an external drive and keep your nki on your local drive and even move it to another folder after on. Kontakt will always find the samples on your external drive.

cons

you can’t actually publish your release like this.
Your customers won’t be able to use your instrument without reallocating the content

missing-files

Relative Paths

If you leave “Absolute paths” unchecked Kontakt uses relative paths. That means Kontakt always looks for your files relatively from where your .nki is stored.

For example if you save it to D:\My_Instrument\MyInstrument.nki. For Kontakt your resource folder always is in \Resources\
Also when you are moving all files to a new location (hard drive, partition or sub folder).

So when copying all files to C:\Release Version\ the path to all your files still is \Resources\, \MySamples\ and \MyResourceContainer.nkr

Always relatively to where your nki is stored. This way we can publish our instrument without worrying where our customers/users will store our instrument package.

As long as all files are kept together (the way they have been published) Kontakt will always find them even if one puts the files into W:\Love\Subfolders\Even\More\When\Loosing\Track\

PROS

always working without a missing content warning as long as all files are kept together the way they have been published

CONS

it is not possible to separate resources, samples and nki files
eg. when putting only the nki to another location while leaving samples and resources at the original location you will get a missing content warning.

How useful was this article?

We are sorry that this post was not useful for you!

Let us improve this post!

Leave a Reply

use <pre></pre> to wrap code blocks

use <code></code> to wrap small code snippets

Your email address will not be published. Required fields are marked *