

You will then need to launch Komplete Kontrol in standalone, go to the preferances, libraries, users tab, and then add the path to your newly created folder, and then perform a rescan of Komplete Kontrol in order for it to pick up the new location and add it to your database.

The second method is to create a folder named for example ‘Standard Sample Libraries’ on your main sample drive and place your non NKS library folders within this.

The first method is to simply place yor non-NKS Kontakt libraries into your user content folder, however this is not always desirable as typically the user content location is on your operating system drive, and as Kontakt libraries can be quite large in size adding several will diminish greatly the space on your OS drive which is best avoided. There are a couple of ways to do this based on your own preferances: NKI preset files to Komplete Kontrol, which will appear on the user side of the Komplete Kontrol browser.

Using Non-NKS Kontakt Libraries within Komplete Kontrol NKSN snapshots, this can save a good deal of space. NKI files are provided and loaded, and the presets themselves come in the form of. Many library developers now distribute their products in a way that only one or two main. Indeed if you alter or edit the parameters of a Kontakt instrument to your own liking and decide to save it as a preset, then by default it will be saved to your ‘user content’ folder into a sub folder that reflects it’s origin (for example user content/drumlab/my snare.nksn). NKSN are accurate describtions of their content, they take a snapshot of the current state of a loaded Kontakt patches parameter settings for later recall, and so can be thought of as presets. Kontakt snapshots with the file extension. nicnt file in the root of the library folder, and looking inside the samples folder itself will reveal iit’s sample format. and the samples used will be compressed into. nicnt file which will also bear the same name as the library itself (for example Drumlab.nicnt). It should be apparent from your own installations and purchase choices whether a Kontakt library is NKS ready and able to use the Kontakt player, however as a matter of confirmation these products will include a.
#REAKTOR VS KONTAKT FREE#
Have their most significant controls mapped to the hardware knobs on the Komplete Kontrol keyboards.Īs always there are one or two exceptions to the rule, and it is (with sighted assistance) possible to map your own NKS parameters for a Kontakt library, and indeed there are a couple of examples of free commercial non licensed/non Kontakt player libraries that are NKS ready, however due to the lack of licensing these will only appear on the user side of the Komplete Kontrol browser. Authorised through Native Access and Kontakt Player compatibleĢ. NKI presets but saved out as a self contained NKM multi, which unfortunately cannot be loaded into Komplete Kontrol directly.įor a library to appear within Komplete Kontrol’s factory browser specifically they need to be:ġ.
#REAKTOR VS KONTAKT PATCH#
NKSN, are Kontakt snapshot files, and NKM are Kontakt multi’s which is a multi part patch made up of several individual. NKI files this being the most recognised Kontakt file variant. There are many commercial Kontakt sample libraries available to use in Komplete Kontrol, Kontact being accepted as pretty much the defacto industry standard sample instrument. Most of the above file formats and their associated products are fairly self explanatory, however there are one or two which warrant a little more clarification. We have already established that Komplete Kontrol when first loaded as a plugin within your DAW is essentially an empty vessel that acts as a host to the plugins that get loaded into it, specifically Native Instruments own directly supported file formats are as follows: SO WHAT PLUGINS AND FILE FORMATS CAN KOMPLETE KONTROL RECOGNISE?
