It's like the one that publishes Wallpapers or collections of Wallpapers, but the history of .nicnt files is that with them you can screw up the Kontakt registry, that's why they are not shared, each library has a different Snipd, and if only it were to use it in Kontakt Portable fine, but once you share .nicnt files you don't know how people use it

 

Well I'm not one of them for sure. And I certainly do not want to install each and every available KONTAKT library anyway. However it would be nice to have the correct wallpapers instead of the ones created by KLC

However the intention of my script was basically to find libraries with missing .nicnt files, generate them with KLC and auto add them using the Kontakt 6 PORTABLE - Library Manager. At least it has proven very usefull and time saving for me

 

It´s a very good idea

 

if only there was a list of libraries not requiring or not working with a nicht file
its confusing

 

its nice, i have now done the nicnt file with KLC
and then add all my old libs about 100 libs
with the library add function from library manager and imported everything from my F: kontakt hdd

only the wallpapers are missing, any chance to add them ?

 

KLC itself can not find and download the correct wallpapers (for obvious reasons). However if a library already has a wallpaper file (but no .nicnt file) I think KLC will leave it be and not overwrite it with the generic KLC wallpaper. I'm not 100% certain but I will check it out. You can however change the wallpaper from within the library manager after importing your libs.

While KLC is a cool little tool it's quite limited in functionality. If only it could interpret commanline arguments the whole process of finding libs with no .nicht and create them automatically from within the script could be automated. Something along the line of

KLC.exe "libraryname" "path_to_library"
KLC.exe "Soundiron Emotional Piano" "F:\Soundiron.Emotional.Piano.Player.Edition.KONTAKT"

However extracting rhe library name from the filename will never be fool proof. And the library name has a limited character lenght as well (at least in KLC)

 

Last edited: Apr 13, 2020

This worked fantastic! Thank you!

 

Hi, I am an ancient relic, new to creating Kontakt libraries. I have a number of sampled ethnic instruments which I would like to setup as libraries. Last week my b/day gift was a NI licence pack and I have installed like crazy. All the NI libraries show up in Kontakt, but not the ones my buddy's drive. Most, if not all are missing the nicnt file. I do not have acess to WinOS. Do you know if this procedure would work in a Virtual Machine environment on OSX?

 

I forgot to say: if this has already been covered, please point this new-"old"-boy, to it. I don't like asking anyone to repeat what already exist. Thanks.