NKS Development Discussion

chpiatt

What's the protocol for sharing Kontakt instruments with updated/fixed mappings? Assuming if you don't share the samples it's kosher? So, just the instruments folder + any relevant NI Resources?

Sunborn

https://community.native-instruments.com/discussion/comment/160084#Comment_160084

I was also thought about a Kontakt NKS related thread and i do have some material to post too. But i couldn't decide if it fits on NKS category or it should be posted in Kontakt category. But since you mentioned it. If @Kymeia agrees too, i can make a new thread here, tomorrow!

Kymeia

Probably best for its own thread, same as Reaktor. I also have attempted some Kontakt mods, with mixed success and not sure myself about what is safe to share

Kaldosh

for all I see so far , NKS is on the run to be despised in the long run and a lot of more open protocols are going to make it if maintained as is . I am NOT NKS 😁

Sunborn

https://community.native-instruments.com/discussion/comment/160095#Comment_160095

I did it.
I think is safe to share anything, since NKS presets will not work at all, if the library is missing!

But for start, we can focus on presets for free libraries only, and previews and missing resources for all libraries.

https://community.native-instruments.com/discussion/32165/kontakt-3rd-party-libraries-nks

Kaldosh

Great, keep doing this , I am on my way to solve my NKS issues using other NKS issues

chpiatt

For context, what I have ready are some fixes for Spitfire Audio Kontakt libraries (missing previews, broken knob mappings, etc.) Assume the place to put these would be the Spitfire Audio thread, but wanted feedback on the format before posting. Most of these are official libraries listed in Native Access, they've just been broken forever and Spitfire is not fixing them. I'm sure others would be interested in the fixes I made if we think sharing them is kosher.

Sunborn

https://community.native-instruments.com/discussion/comment/160118#Comment_160118

Spitfire Audio plugins should go of course in the Spitfire Audio NKS thread, but i think that Spitfire Audio Kontakt libraries should go to new Kontakt libraries NKS thread. @Kymeia what are your thoughts about this?

Kymeia

I think they should probably just go under Spitfire but either way is ok. I see the Kontakt thread as more dedicated to how to tackle Kontakt from an NKS standpoint as it’s one plugin I struggle with because its integration with KK is clunky to say the least.

chpiatt

https://community.native-instruments.com/discussion/comment/160199#Comment_160199

For sure. I've learned some things about what you can/can't seem to fix when it comes to Kontakt library issues at the moment from this process:

- Adding previews, images, etc. usually no problem.
- Creating KK mappings for Kontakt instruments where none currently exist is usually doable, just potentially time-consuming.
- Fixing broken knob mappings is pretty straightforward, just potentially time-consuming.
- Applying a knob mapping programatically to a bunch of Kontakt instruments from a single mapping done within KK is, shockingly, easier to do than it is with regular .nksf files (provided the instruments have consistent 'Host Automation' mappings - which is often not the case, at least with Spitfire's Kontakt instruments. So, time-consuming to fix.)
- Fixing 'vendor' mappings so that libraries show up under the right tabs in KK is, frustratingly: "it depends".
- Making snapshot-based presets for third-party Kontakt libraries load correctly in KK without having to manually resolve the link to the underlying samples every time you open the preset seems to be impossible (or at least really difficult) at the moment.

Would be interested to learn about other's methods when it comes to Kontakt or share my own if there's interest in that thread

Kymeia

Making snapshot-based presets for third-party Kontakt libraries load correctly in KK without having to manually resolve the link to the underlying samples every time you open the preset seems to be impossible (or at least really difficult) at the moment.

Yes, this to me is something that has needed fixing for years, this is why I need someone to test my Deepflight snapshots. It's even a problem if you change the drive the samples are on or move to a new computer. And yet NI authored snapshots seem to manage fine so yet again we have an example of them not really thinking much about the user experience, as long as NI and NI partner content works that's good enough.

Also I have been able to make it a 'standalone' instrument but for some reason KK still identifies it as a Kontakt instrument in that it shows the default Kontakt mst_plugin image, not the Deepflight one I made for it. I have tried everything I can think of…In the browser it appears as Deepflight 2 though and I was able to make audio previews for it.

Sunborn

https://community.native-instruments.com/discussion/comment/160329#Comment_160329

This is because, at least the snapshots from the official libraries are not directory-depended, but folder-depended. There is no declared path inside their code. As long as the snapshot is in the <Library name>/Instruments, it will always work, no matter where you move it

" I have been able to make it a 'standalone' instrument but for some reason KK still identifies it as a Kontakt instrument in that it shows the default Kontakt mst_plugin image, not the Deepflight one I made for it."

please download and check the resources pack i did, to see how to do it… a simple mst plugin image, is not enough… you need the "full pack", including the .meta file, all inside their own folder, and that folder should not be inside Kontakt folder

Kymeia

https://community.native-instruments.com/discussion/comment/160333#Comment_160333

Thanks - thing is I did all that and it still shows all images in the browser except mst_plugin

Kaldosh

in my configuration, I tried what all used to work. I don’t know what happened in the last maschine update . Could there be an issue about using KK 2.9.6 and last Maschine update ? So do you recommend downgrading trying to get everything back up and run in (as it should) and stay there ? I’d rather keep my old stuff working and stay in my school if that is the only way to get my hard work back on track. Because even after doing the usual trick it doesn’t want to work and want me to go through the same work all over again which is something I am going to wish to all to be understood. Let me know

James Steele

Has anyone encountered a situation in which a VI plays back completely fine when loaded into a DAW or even Blue Cat PatchWork, but has issues and certain notes distort when loaded into Komplete Kontrol? In my case this is happening with certain drum kits in Ugritone Drums and Komplete Kontrol 2.6.9. When I load certain kids, I'll get nasty artifacts on some of the samples… mostly kick and snare. But the strange thing is when I open Ugritone Drums VST3 inside of Blue Cat PatchWork, there are no issues. This isn't the first time I've encountered this with this particular VI… happens in other kits too.

Just very strange… it all sounds fine EXCEPT in Komplete Kontrol. Sadly, the developer which is based in Finland is going out of business, too.