Solved Komplete Kontrol Software 2.1 can't modify mappings

A strange issue after updating to 2.1 on my Windows 10 X64
All existed mappings works ok, but if i try to add a new map (on learn mode) or modify an already existed, nothing happens
I tried with admin rights, uninstall and reinstal but this weird thing continues


Has anyone the same problem?

 

That doesn't look good

 

Yep, can confirm this and it's just another thing that is disappointing me with KK right now.

If you have Maschine a workaround is just to create the template there (still works) and then use that as the starter.

 

Hey Folks.
Thanks for reporting this and apologies for the inconveniences.
Our Developers are having a look at this at the moment and we hope to be able give an ETA on the fix soon.

 

Τhis is how I'm working now, but always i preffer KK for mappings. I hope ΝΙ fix it soon. Thanks Kai

 

You forget a step.
If you create a new page, in your case pag16.
Then you have to indicate a controller in the blue box.
You do this by clicking on the arrow in the blue box, then a list appears where you can make a choice.

René

 

Yeah, i know that. But in this case you need a lot of time to scroll down and choose one of (sometimes) weird names.
IMO the learn mode is much faster and i'm sad that now it's not working
Thanks

 

I notice in the release notes of KK 2.1.2:

I assume that refers to this issue. If so, it's not fixed for me - I still can't assign instrument controls to KK controllers in 2.1.2 on testing just now.

 

Yeah for me too. I report the problem to NI and i hope to fix it soon

 

Damn!

 

I'm not seeing this. Seems fixed for me. What VST are you using and what OS?

I'm Windows 10 and have tried a few VSTs and they all map controls just fine with latest 2.1.2

 

Hi Jason,

I'm on Mac OSX. On a bit further testing I see it does indeed work for some libraries.

In my case I'm trying to save NKSF presets, or snapshots, including mapping for the Cinematic Strings Kontakt library. To do this, I load Kontakt from the KK "Instruments" menu, then select "Edit View" to see all of Kontakt and then load an NKI from that library.

The NKI has an interface where you learn MIDI CC on controls, but when I highlight a KK control for mapping...



...then try moving some of the interface controls on the Kontakt instrument, nothing happens.

However, on other libraries, official NKS ones, I can re-map existing controls, and add new pages of mappings. I can also do this for plugins.

I thought perhaps mappings could be made for any library, then saved in the NKSF file - but I see now it doesn't work for some other more obscure instruments, either.

(btw Nice work on all your patch libraries - I bought quite a few recently!)

 

Working fine for me too, I just updated to OSX 10.14.4.

 

This is not a bug - for Kontakt instruments you need to assign host automation to params first, then map them in KK

 

Yeah I was just about to ask if you have done this. I don't do much mapping within Kontakt but testing KK with VSTs such as Xpand, Sylenth, Omnisphere all work as expected so no issue I can confirm for this.

 

Previously some plugins worked ok and some others not. After a clean install of KK now all VST's worked perfect. I would not have tried it, if Jester he had mentioned that for him worked ok. Thanks Jester. I expect the feedback from some other users, before i mark the thread as solved

 

Many thanks to all here - I had missed that requirement! Excuse the false negative - I confirm the issue is fixed too - in fact it was never the same issue I was seeing.

This means using KK is a bit more similar to just using a standard MIDI controller in Logic to control plugins than I had previously thought.
To summarise for others as well: host automation must be set up by accessing the full view of Kontakt, going to the Automation tab and dragging assignment numbers to UI controls. This does link controls immediately, and it auto-names them. Then the NKI must be saved.

If you then go and edit the KK controls, you are able to rename or re-map them and save this configuration as an NKSF snapshot, using the KK menu (only). You can recall this using KK or Kontakt's own snapshot loading control. You can only map UI controls that have already had their host automation params saved to the NKI, and only one control can target a given parameter.

I guess this is similar to the way it works with any plugin instrument too - host automation for controls saved to the actual instrument, then custom mappings saved in NKSFs?