KSP Scripting (NI Kontakt) :: BASICS :: Absolute vs Relative File Paths
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…
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 have probably already recognized the problem: When publishing your instrument also your customer’s Kontakt will look for the files at your location which still is D:\My_Instrument\..
cons |
PROS (developer only?!) |
|---|---|
|
|
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 Kontakt will look for the resource folder in \Resources\
Also when 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 install 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\
CONS |
PROS |
|---|---|
|
|
Hinweis