Using DP K7 projects on two identical computers ?

Michael Groarke

I use Kontakt within Digital Performer and need to be able to move between a studio setup and a home setup. What steps can I take to make it more likely that a project started on one machine will open just the same on the other machine? Are there preference and settings files that I can copy over? I already set up matching external disks for the sound library giving each volume the same name and folder/path structure.

Our MO is to have two instances of Kontakt Player. The first instance uses a "multi" to provide bass, chords, and melodic parts. The second instance is exclusively for drums. The first instance has multiple stereo outputs and the drum instance uses multiple mono and stereo outs.

Jeremy_NI

Got some great feedback from the Kontakt team about this:

As long as there have been only presets used, which have been provided by the Kontakt libraries in use, there is no need to manually copy any files to the other machine.
The libraries in use have to be properly installed and activated on the other machine and the regarded presets should be found automatically, as Kontakt will save so called relative paths within the host chunk. Meaning if you open the same project on the other machine, Kontakt will try to find the libraries using the libraries registry entries which contain the installation path on that system.
All the alterations of a loaded preset in the project (its parameter settings) should be saved within the so called host chunk within the DAW project and would then be recalled accordingly when loading the project on the other system.
If for some reason a path to a certain library is not found (the content folder was renamed, either on the source or destination system) the relocation dialog will appear and the path can be fixed by pointing to the regarded library folder and resave the project on the destination system.

If one wants to work with custom instruments, there is three options for saving NKIs for example (absolut path, relative path, monolith)

• monolith saves the nki including the used samples into one file
• absolute path means the exact path to the used samples is written into the NKI (will cause relocation when moving to a different system or moving renaming the sample location)
• relative path, will save a part of the path, seen relative from the NKIs save location (typically a sample folder located next to the NKI file)

I would recommend to use the first or the last option depending also on the number and size of the samples. Smaller instruments use monolith, as its the safest option to bind the samples to the nki. Bigger instruments use the last option (relative path) and for practical reasons save the NKI + its sample folder inside of the folder for your DAW project. This way you move everything that belongs to the DAW project over to the new system by copying this whole project folder.

For snapshots (presets) if they have been saved from a properly installed library, it should find the regarded library once you load such a preset. Just make sure to collect the presets (snapshots) properly, by either saving them also to your DAW project folder, or to the default NI User Content Location and then move them over to your new system as well.