I have recently acquired a Native Instruments S61 keyboard and I really love using Komplete Kontrol, having keyboard zones shown by the light guide and having labelled encoders for instrument parameters in front of me on the keyboard.
 
It seems unlikely that a lot of the small, low cost Kontakt instrument developers will adopt the NKS standard as it looks like libraries have to be registered in Service Centre etc. which is going to add work and cost.
 
What can be done however is to assign host automation parameters in the NKI, once this is done Komplete Kontrol will assign encoders to the mapped parameters when the NKI is opened inside the Komplet Kontrol software or plug in. I have been working through some of my favourite libraries and even a complex NKI can be mapped in around 15 minutes.  So utility for customers could be greatly enhanced for minimal investment.
 
Keyboard zone mapping to the light guide on the keyboard works for all Kontakt instruments where the zones are coloured on Kontakt’s virtual keyboard. The vast majority of developers do this and others should follow suit. It’s not only Komplet Kontrol users that will benefit from a visual representation of the key zones.

Hi Glyn,
 
I've been planning a major revamp of our sample libraries (updating the UI, making the whole package more user-friendly, releasing new sample content, etc).  
 
I got a Komplete Kontrol S61 a while back... and like it a lot.
Even just for my personal use, I'd like to have the libraries configured for use with the S61.
I just have to find the time to get it done...    

Hi Jim,
 
Thanks for the reply. I dont know if you have seen this thread where I an collating my "guide" to setting up non NKS content from the user point of view. I am still on the learning curve, mainly due to the lack of a clear instructions. I have just added my latest discovery to the thread.

if you are looking for votes Mr. Roseberry, well, I still love your drum library, but I don't use it as much as I used to because it is a bit cumbersome to set up and tweak. I am pretty certain that an update would breath new life into an already outstanding library.

Thanks Bill!
I've got some ideas for the UI that should make it quicker/easier to use.
All mic selection will be done directly in the UI.
You'll be able to configure/mix everything inside a single Kontakt instrument.
Got a copy of Cinema 4D, so there will be a totally new 3D GUI.  
 
Can't wait to ultimately get the Sonor Delight samples assembled.
I've owned numerous high-end drum kits over the past 30 years.
That Sonor kit was the best I've ever played/heard.
 
Now, I just need to clone myself 5 times...   
Time Management... 

Hi Glyn,
 
I've bookmarked your thread on using Komplete Kontrol.
I'll spend some quality time reading it this weekend.
 

Hey Jim - can you clone your self only 4 times if I promise not to call about tweaking my DAW in the near future?
 
Wish I could help...

Great thread, Glyn, hope it works.

So, I have gained a lot of insight going through my Kontakt libraries.
 
Here is a list of five things that would make a library “NKS Friendly” without going down the road of complete compliance (Komplete Kompliance??) to the standard.
 
Use snapshots or the older systems of menus for pre-sets rather than multiple NKI files. The user has to make the host automation assignments once and then save each of the snapshots as a new instrument in Komplete Kontrol without reassigning automation. When viewed in the browser the instrument will appear as a “Bank” and all the pre-sets will be one level down in the structure just as they are with the NI factory libraries. If there are multiple NKIs each one appears as a separate bank. It would be good if NI added a feature to enable you to group NKI into a bank but…... (I will be adding a feature request on their forums).
 
Ensure the keyboard mapping is done so different keyboard zones are in different colours. This helps everyone, not just KK users, but in KK it will ensure the light guide for keyboard zones works correctly.
 
Avoid the use of black keys for unused key zones as these lights up purple on the keyboard, white will just remain unlit.
 
Ensure on/off switches are set up consistently. I have seen some cases where they were not consistent within one NKI.  Most common, and logical is knob to the left = Off.
 
Give sensible names to controls. It’s much easier if a parameter appears in the host automation as say “Attack” than as “8ghb7”.
 
Some further steps.
NKIs could be supplied with host automation parameters already assigned.
I suspect it would also be possible to provide a *NKSN pre-set files but I am not sure if different path names for the related NKI would cause a problem.

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