OK, so obviously the November Community update Q&A is now closed, which means unfortunately, not for the first time, all the questions about the future of Komplete Kontrol will remain unanswered, so I'm opening a new thread. We have seen significant developments for the Kontrol keyboard firmware and DAW integration, as well as for Maschine, but why does Komplete Kontrol, the centre of the whole NKS ecosystem, keep getting ignored? It is high time KK3 gets the attention it sorely needs and as I suggested in the Q&A thread, at the very least this should start with point 1, with a clear commitment to a roadmap to address the other points in the near future:
- Restore what is missing - sub banks, properties editing and drag and drop (of samples) between the browser and plugins and DAW
- Enhance the NKS editing functionality to bring it onto a similar level to the MIDI templates editor, such as support for user page insertion at any position in the mapping, and user page repositioning (drag and drop to rearrange param order would also be useful) .
- Expansion of properties editing to also include bank/sub bank name fields and giving users the tools to apply templates to a batch of presets at once and generate previews etc to make KK a fuller NKS1 authoring solution would be very welcome
- Finally, while it is great to see developers like UAAudio adding NKS support, given that most of their portfolio are FX, a lot of them mastering solutions, it really does draw attention to the rather large Elephant in the room that NI have been studiously ignoring since incomplete FX support was added many years ago now. i.e that FX support is so incomplete it is virtually useless - as a bare minimum we need a dedicated effect version of KK (so it can be used as an insert or on the master buss), plus full support for FX automation and FX chain saving. It was ridiculous that FX support was ever added in such a half assed way and we are well past the time to address this.
Tagging @Simon_NI @Chris_NI @Matthew_NI @timrae_NI