NI Komplete Kontrol M32 - How to navigate and browse with 4D knob?

Anyone else with a NI Komplete Kontrol keyboard? I have the small M32.
I wonder if and how you could navigate and browse presets inside AnalogLab?
Comparable to the MiniLab functionality. I can get the knobs to control the macro parameters… but not the preset next/prev buttons. Also the bigger 4D knob would be perfect for navigating and selecting… As far as I understand the M32 behavior, it seems to send data over 2 different “ports”. One is MIDI, and the other one is called DAW. Not sure if the 4D knob is using another protocoll? Maybe MCU? I have to check this again with a monitor app.

if someone has experience with a Komplete keyboard (S, A, M32), your help is much appreciated.

Hi, if I recall correctly, the 4d knob is sending a midi cc (I think it was a 0xBF 0x3C, but can’t be sure right now), with values of 0x01 and 0x041 for the turns. What I’m sure is that it sends these values through the DAW port. This means that you can use utilities such as Bome MIDI Translator Pro to translate these two values to different MIDI CCs and assign these two new ones, to the preset Previous/Next functions. However, if in a DAW, you have to intercept NI’s implementation, by setting the MIDI Ports of their unit to none, in order to not consume these values.

Perhaps it would be more consistent to simply create a second template in your M32, and assign these functions to 1 or 2 knobs. This way, you wouldn’t interfere with the DAW mode of the M32, and do your job with the MIDI port.

1 Like

Hello again, thanks for pointing out the BOME software. Didn’t know it yet. Very interesting.

Here is a screenshot of the data sent on the DAW source/interface.
The first 8 values are from the joystick movement in all 4 directions.
The last 2 values are from turning it left and right. Those two values are just repeated on each “nudge”.
Funnily pressing the button down does not send anything?!?

The M32 source/interface does not show any data at all. But I have seen a scrolling behavior with that 4Dknob in another App… which was available as “Dknob” and could be applied to parameters with a label called “Delta”. It allowed scrolling only, no other actions. How can it work, when a monitor app does not get any data?

Hi, the messages that you see are when we are in MIDI and not in Track (DAW) mode and I understand that this can be confusing.

When we open a DAW with the M32 connected, a handshake is performed and then the 4d encoder sends totally different messages.

In Cubase we have the following, all CCs:

image