TerraSin
I'm not sure if it can be done but why doesn't the Kontrol "Kommunity" open a website and make their own NKS files for the Kontrol and put them in a big library to share around? Or is NKS something that has to be scripted into the NKI itself? Seems silly that they would design it in such a way that people couldn't make their own if it's just a control standard
Well there is already a move to share templates for
VSTi's on the NI forum.
This thread contains a number of templates for download.
Kontakt libraries and VSTi's are different.
VSTiMost VSTis work "out of the box" if you are prepaired to accept the default mapping and often cryptic parameter names. Its not that difficult to edit the mapping to something more appropriate and save it. What you won't get is the preset lists appearing in the KK browser. You can save your own KK presets. I did this with True Pianos for example so Atlantis, Diamond, Amber etc. all appear in my user browser in the bank True Pianos. I dont fancy doing this for something like Rapture Pro however.
You will see the thread gets full of questions and comments so finding the downloads is difficult. I think NI should make a section on their User Libraries page for these.
Kontakt Instruments.Unlike VSTis these generally require some work by the user to map the host automation parameters. The steps I outlined in post #9 would make this process easier.
I have yet to test the portability of the *.NKSN preset files as they must point to a modified NKI file which may not be in the same location on everyone's computer. If any one wanted to try this out PM me and if we have a library in common I can send a modified NKI and a NKSN file to test.
A potential pitfall to a user site is some developers may object to modified versions of their NKIs being distributed.