Symbolic links

Hi @isabella, thanks for this explanation.

It's a good idea, but this approach will work only if:

1. The original sample/nki folder (or symlink to same) is at a path which is reproducible on any PC or Mac in the world (including localized versions, systems where the user has relocated important directories, etc.)
2. Every end-user is capable of making their own symlinks, without having to contact John for tech support. (Not too hard on Mac, far harder on Windows, highly error-prone on both.)

Hi, I'm not sure I understand why relative patch to the sample folder wouldn't work. All samples placed in subfolder within the main folder where the patch was saved should be located by Kontakt automatically, even if you move the whole folder (with subfolder containing samples) to another computer

@robert-p

As far as I can tell, Kontakt does find samples based on paths relative to the main folder containing each library. The problem arises because when a host program (like a DAW or Unify) requests its binary state-data, it includes the absolute path to that folder. When its state is later restored, Kontakt goes looking for the files at those exact paths, and if it doesn't find them, it pops up the dialog prompting the user to locate them.

So the issue is not that Kontakt cannot make use of relative paths; the problem is that it needs at least one absolute path which is what those relative paths are relative to.

Aaa, now I understand, thanks for the explanation!

need the symbolic link to run my unify kontakt patches