NKS User Library

OK done I think, both layers now - there are some compromises to avoid having to map the hundreds of params that can actually be mapped and making this an impossible multilevel beast to use in performance, which is the main aim (my view is sound designers will still need to use a mouse, but performers need quick access to the most used params only). So for example I only mapped 4 LFOs per layer and no MSEGs (as these need a mouse anyway mostly), but if you feel the need to add more I can (but then you will need to change the order for me). Also the global layers annoyingly have 9 params so I left out the pitch ones but again if you feel they are needed they can be added on a page of their own with just 2 controls but it would need reordering the pages. Also I didn't map the fx.

https://dl.dropboxusercontent.com/u/5646041/Komplete/Synthmaster template.nksf.zip

Please test this with a KK controller, I don't have KK to test myself as I use Kore primarily, but I noticed that some of the mapped params don't respond to the mouse (eg ARP) if you try to move them in the KK mapping interface - only if you move them in Synthmaster itself - but I'm hoping they will move using the KK controller - otherwise this may be a bug with Synthmaster (params can be mapped but communication is one way).

 

@Kymeia
Thank you! I just updated SynthMaster2 presets including your mapping.
quick fixes:
- map ARP to Layer1:Arp instead of Layer2:Arp
- shrink parameter name of MASTER section
I will continue to update it when I noticed something.

 

hmm..many parameters doesn't work on KK. Maybe KK has upper limit(around 1200) of parameter's index range. I confirmed that those parameters work bi-directional correctly on mapping layer of other hosts(Maschine,Live and Bitwig).

 

Damn - not sure if that can be fixed. I have mapped many plugins with more user pages and params though. The params not working seem almost random as well - can't see any pattern to them.

 

Yeah the same params map fine in NI Kore 2.

I've posted something on the developer's forum, the big problem is while he could change automation IDs to make them work better in KK it would impact massively on backwards compatibility.

 

Just going by the order of params in the dropdown list this still doesn't make much sense - for example Layer 1 Filter 1 keytrack is one of the params affected, and yet it has many params that come after it that work perfectly fine so I would have thought they were numbered higher unless param order isn't the issue? Must say the way the dev has ordered params seems rather nonsensical if this is what determines how these are presented to controllers and DAWs - the topmost ones are for the most trivial things like fx and ARP numbers.

 

Yes, Layer1 Filter1 Keytrack(id=1093) is the upper limit. It might be related to the fact that KK plugin has following host parameters.
0 - 100 KK's arp, scale, chord, etc
101 - 1194 wrapped VST plugin's parameters(0-1093). The order of these parameters is not mapped result.

 

@Kymeia Thank you so much for your hard work. So appreciated. Do you have a link with your compiled work for download please? Thank you.

 

Someone please make NKS presets available for UVI products such as Vintage Vault using Workstation or Falcon!

 

Falcon would be very hard to map as it's modular so every patch has a different set of modules

 

Here's a template for PolyKB III which just came out

https://dl.dropboxusercontent.com/u/5646041/Komplete/PolyKB III.zip

 

Did anyone map the great Repro1 https://www.u-he.com/cms/repro-1 by u-he yet?

 

It has full NKS support built in

 

TX!：p

 

Anyone have something for Steinberg VSTi's?

 

Can't do - they only have AU and VST3 versions so don't load in KK

 

Thats not truth, i can run it with no problems in the KK software.

 

Not on Mac I can't, maybe on Windows there is a VST2 version? If so you'll have to do this yourself.

 

Thanks a lot. UVI Synth Anthology 2 is working well. My plan is to integrate other UVI Instruments working with the UVIWorkstation from the Vintage Vault. That's why a have to questions:

1) How can I add a bank to the instrument? I think it is not possible directly in Komplete Kontrol.
2) How can I make different instruments from the same VST-plugin. Like you have did it. The Synth Anthology 2 is working on the UVIWorkstation plugin.

 

Here is an example metadata of my SA2 NKSF file. In actually this metadata is encoded using MessagePack.

{
"author": "",
"bankchain": ["Synth Anthology 2", "Roland JUPITER-8", ""],
"comment": "",
"deviceType": "INST",
"modes": ["Classic Analog"],
"name": "JP8-Warm Ambient",
"types": [
["Atmosphere-Ethereal", "Roland JUPITER-8"]
],
"uuid": "ac42c0d9-d24c-4347-b831-8a7141702ef6",
"vendor": "UVI"
}​

If you save a NKSF file in KK, bankchain will be as bellow:

"bankchain": ["UVIWorkStationVST", "", ""],​

Currently there is no way for editing the bankchain in KK. You have to rewrite or create it pragmatically. Resource files(icons, etc) should be placed at:

<NI Content location>/NI Resources/dist_database/<vendor>/<root of bankchain>
<NI Content location>/NI Resources/image/<vendor>/<root of bankchain>​