Kontrol 2024 outlook: what was, what now, what next?

PreacherAtArrakeen

Thanks….2bodies.

Duffcat

https://community.native-instruments.com/discussion/comment/140267#Comment_140267

I’ve been using Kontakt and MK3 in Sonoma but haven’t experienced any major issues. What is the current issue Matthew?

Scott Frost

@Matthew_NI can Mk3 change the midi channel direct from the board? This was not possible from mk2, but was there in mk1. Having to connect to pc to do this, then disconnect is not very user friendly.

Thanks!

Matthew_NI

https://community.native-instruments.com/discussion/comment/140288#Comment_140288

Once MIDI Template editing ships, you will be able to do this yes. Or even do so by key zone or split. We're close to beta, and as noted in the roadmap intend to ship very soon, albeit later than our original goal of March.

Matthew_NI

https://community.native-instruments.com/discussion/comment/140283#Comment_140283

It's not a 100% repro, but for affected users it can be pretty consistent and severe.

When the two are used together, under certain conditions there is some sort of communication protocol that breaks down, which Apple have indicated they're responsible for fixing. It manifests very clearly as a catastrophic crash.

We have an issue number filed with them, and continue to follow up (last email was Monday).

Ojustaboo

https://community.native-instruments.com/discussion/comment/140153#Comment_140153

[EDIT] Sorry, ignore this thread, everything is working fine today, not sure what I did wrong yesterday

Apologies for my earlier rant.

A question I’ve just asked on Arturia forum is below. Is what I’m asking down to Arturia or is it a current limitation on what they can do with nks?

Thanks

——————————————

Hi, my keyboard setup is as follows.

Native Instruments mk3 S88 and Arturia mk2 Keylab 61.

In Komplete Kontrol the S88 knobs control various parameters.

Also in Komplete Kontrol I can sign an external controller to the 8 knobs (and for some buttons).

The relevant bits from Komplete Kontrol manual are

The way this works is, I simply assign the first 8 knobs on my Keylab to the 8 knobs in Komplete Kontrol. Now they happily control the same parameters as the S88, knob 1 on the Keylab controls exactly the same thing as knob 1 on the S88 etc. What’s more, it doesn’t matter what cc the 8 knobs on the Keylab were set at before assigning them, the S88 still also controls the 8 knobs, hence must have done something in s/w to allow this.

I can load any NI instrument and whatever the 8 knobs control on the S88, the first 8 knobs on my Keylab control the same. Even if on the S88 it shows there’s 3 pages of knobs, I go to page 2, whatever those knobs now control on my S88, my Arturia Keylab knobs also controls them. Which is very very very handy.

So, I only need to assign those knobs to my Arturia Keylab once, then next time I launch Komplete Kontrol, it remembers, and it doesn’t matter which NI instrument I load, or what page of parameters I go to on the S88, the first 8 knobs on my Keylab control exactly the same parameters as the 8 knobs on the S88.

However, when I load Arturia V synths into Komplete Kontrol, while the S88 happily controls them, they are not assigned in the same way as NI’s own instruments. 

For example I load in a v instrument with 3 pages of parameters on the S88, on the first page, only 2 of my Keylabs knobs control the same thing as two of the knobs on the S88, and not in the same place (made up example not near keyboards, say knob 2 on the S88 controls cutoff, knob 7 does on my Arturia.)

I then select page 2 or 3 and none of the Keylab knobs control anything, using my previous example, knob 7 no longer controls what knob 2 controls on the s88.

So NI seem to have coded their 8 knobs to always use the same 8 knobs that I can assign to an external controller in Komplete Kontrol, and whatever page of knobs I’m on, they still work flawlessly on my Keylab, but Arturia appears to use a different method where not only do they not use the same 8 knob’s assignable in Komplete Kontrol, but a knob that happens to work on one page doesn’t work on the other pages.

Sure I can use Analog Lab, but as you’ve made the very nice effort of making your v synths NKS compatible so we can use them in Komplete Kontrol, it would be nice to be able to control them from within it as easily as we can with NI’s own instruments.

Thanks

Matthew_NI

https://community.native-instruments.com/discussion/comment/140124#Comment_140124

Inevitably we heard the opposite in testing. But truthfully, it may not be as binary or polarized, but more like 60% prefer as-is (Mute default) and 40% prefer opposite (Solo default).

This could be added as an option in Hardware settings menu, and I'll never say never, but it's not on the radar for now. In the early days of a new product, I try to avoid the risk of polluting menus with lots of options before the simplicity of the thing has had a chance to live, breath, and get wider feedback. Then we have a clearer picture of what ongoing minutia users really want.

So, the feedback is helpful, and noted! I just don't want to make any false promises it'll change immediately, is all.

Matthew_NI

https://community.native-instruments.com/discussion/comment/140316#Comment_140316

This is super detailed, and quite specific. It's also not directly related to the purpose of the thread. Would you mind reposting elsewhere, in a new thread? Thanks!

Sempai45

What about Maschine integration the way the MKII has.

Duffcat

https://community.native-instruments.com/discussion/comment/140314#Comment_140314

I’m a member of the KK Beta group. Will the beta be available there before release?

Matthew_NI

https://community.native-instruments.com/discussion/comment/140382#Comment_140382

Yes. Everything upcoming will go via beta.

Matthew_NI

https://community.native-instruments.com/discussion/comment/140342#Comment_140342

That is currently not on the roadmap. We may do a rudimentary Transport control integration once the aforementioned priorities are behind us, but that's a maybe. A deeper integration is almost certainly off the table, due to reasons I've mentioned here and in other threads. It was a large effort, and very few people used it.

nightjar

Hmmm.. just trying to think of some "outside the box" stuff...

Better "on-device" QWERTY input might be handy for lots of stuff.. naming stuff, text input for AI assisted discovery..

Maybe there is away to use the keys for this? There are at least 49 of them just sitting around wanting something to do. And perhaps velocity sensitive cap/lower case?

Matthew_NI

https://community.native-instruments.com/discussion/comment/140405#Comment_140405

That's being implemented, actually. To start it's being used for MIDI Template editing, but is modular and can be applied elsewhere as we see fit.

If anyone has used a Nord, it's a similar concept, using the wheel to quickly cycle through letters and complete words. This has proven more logical and intuitive than mapping to keys.

nightjar

https://community.native-instruments.com/discussion/comment/140412#Comment_140412

I can see where casual use would favor the simplicity of just using a wheel to cycle through letters/words..

But as an ongoing common need (AI assisted text query) many users might feel encumbered by this approach and would want to develop the muscle-memory advantage of using the keys.. like they do with their QWERTY key-command shortcuts.

Fun to think what would be the "best" arrangement of layout of letters/numbers to 49 keys

A fresh look a Dvorak-style approach? "Sustainable" Vowels with left hand, consonants in smart "clusters" with the right?

An extension of "speaking with your fingers" with or without actual sounds...