Kontrol S-Series MK3 2.0 update - Encoder Issue / values jump up only

TQ · 2025-08-14T00:31:51+00:00

There was an error rendering this rich post.

I have a weird issue with the firmware update in Logic - when choosing smart controls, or any non-NI plug in, or the DAW controls, moving the encoders lets the values just jump up in big steps, but not down (even if I turn them left). It's not usable right now with any non-NI instruments, as all the parameters will just go the max with one or two touches. Midi CC page just works fine and as expected, as do the Kontakt and Komplete Kontrol instruments, so it's not a hardware issue. Btw,Massive X does exhibit the same behaviour, though!

I already trashed the control surfaces settings and rebuilt, as described on the web page as the solution when in trouble - but not luck.

I guess it's just a stupid software setting for the encoders, but I do not see where to change that behaviour - and again, it works completely fine in Kontakt and Komplete Kontrol.

Find more posts tagged with

Komplete Kontrol SW

Komplete Kontrol Keyboards

Accepted answers

Kymeia

Also, the keyboard is set to MIDI 2.0 (just in case that might be an issue).

Absolutely it is an issue - Logic at the moment is very buggy with MIDI 2.

But to revert to MIDI 1 is a bit complicated but you probably should - here is the guide

https://support.native-instruments.com/hc/en-us/articles/20213420674333-How-to-Switch-a-Kontrol-S-Series-MK3-Keyboard-to-MIDI-1-0

timrae_NI

That's it… we strongly advise not to use midi 2 until DAW support significantly improves, which is going to take a few years, it's still very experimental or non existent, so you're just shooting yourself in the foot by enabling it atm.

Yes, I found it in the meantime as well. It's the MIDI 2.0 input that was enabled in the MIDI settings in Logic. I disabled it, and then it's butter smooth. Funny enough, I did not enable this myself actively in Logic, but only in the keyboard itself, and that wasn't an issue until the firmware update.

Maybe there should be a warning somewhere about this, for example when enabling the option in the keyboard, as I didn't expect a setting there that may cause issues with some of the main DAWs on the market…?

Anyway, this solves the issue for me - thanks for the help and patience on the way. (Btw, disabling the MIDI input port seems to be enough, even when Midi 2.0 is still "on" in the keyboard - but maybe it's better to go back to 1.0 also there (?). Well, I did, and it works now as expected - lovely!)

Sorry, not a native speaker here. Just to clarify: When disabling the MIDI 2.0 port in Logic (as shown in the screenshot above: Settings → MIDI → Inputs), the encoder behavior returns to normal and works fine.

I later switched to MIDI 1.0 in the keyboard's settings as well, and then deleted the entry in my Mac's Audio MIDI Setup and reinstalled the Kontrol S MK3 there, as indicated here:

https://support.native-instruments.com/hc/en-us/articles/20213420674333-How-to-Switch-a-Kontrol-S-Series-MK3-Keyboard-to-MIDI-1-0

However, returning the device itself to MIDI 1.0 seemed to be more of a safety step, as disabling the MIDI 2.0 port in Logic did already the trick and solved the issue for me. (And again, everything seemed to work fine in Cubase before, even with 2.0 enabled everywhere - i.e. the keyboard was set to MIDI 2.0, the entry in Audi MIDI Setup was the 2.0 version , and still, the encoders worked fine.)

But sure, you are absolutely right: If there is no benefit of MIDI 2.0, it's better to return to 1.0. I just thought that I need to set it to MIDI 2.0 if I want to fully use all the features of the device… (and until the new firmware came along, it worked without a problem).

Anyway, happy user now - the new features in firmware 2.0 are amazing! 😎

All comments

Kymeia

Not seeing that here, except the first time I load Massive X the smart controls macros do jump a bit from first positions but once I have selected a patch they stay in the right places and respond smoothly. Logic is definitely flakier than the other supported hosts though.

timrae_NI

Does reinstalling Logic help?

paulbaarn

I have the same probem. Just installed firmware 2.0.4 and for non NKS plugins the values only go up and are on 100% in no time and won't come down. Tried with Massive X and Analog Lab V. It works fine with Kontakt and Komplete Kontrol. Also my custom Midi templates work. I have one for Analog Lab V and that works fine. Only the plug-in mode doesn't work for other plugins. I'm on the latest version of Logic. I won't reinstall it. ;-)

Kymeia

What MacOs are you on?

https://community.native-instruments.com/discussion/comment/237503#Comment_237503

Yes, that's the issue - same thing!

It's not a hardware issue for sure, as the Midi CC behavior is totally smooth, as is the Kontakt and Komplete Kontrol behavior (also within Logic). Here, the encoders are doing their job as expected. Using smart Controls, the new adaptive plug in setting with any third party plug in (and also MassiveX), and also the DAW setting do not work correctly - here, the encoders jump and go up to the max, and won't come down.

I also do not intend to reinstall Logic and everything within - I have a huge plug in folder, so this would be days of work. Also, the DAW controls worked fine before the firmware update, encoders were not behaving like that.

I could imagine that this is related to the control surface settings of the keyboard within Logic. I already deleted and reinstalled it, as described as the trouble shooting step on NI's website, but that didn't do the trick.

I could install Cubase here - do have a license - and see whether I get the same results, but that would be quite some work as well. So if somebody actually knows an actual solution (instead of the "reinstall all solution"), I would prefer that...

https://community.native-instruments.com/discussion/comment/237505#Comment_237505

Mac M4Pro Mini, Sequoia

paulbaarn

I'm on Sonoma 14.7.1. M1 MacBook Pro, if that matters.

jcress_NI

I would suggest shutting down logic, deleting the logic cs files again at /Users/your.name/Library/Preferences/com.apple.logic.pro.cs
Reinstalling the Hardware Connection Service from Native Access
Then restarting your computer

If the issue persists could you go to a non-NKS plugin, open the Control Surface>Controller Assignments window. And turn a encoder and send me a screen shot of what the screen says.
For example this is mine

https://community.native-instruments.com/discussion/comment/237514#Comment_237514

Did that already, but will try again. Will take a bit, though, as I am not at my studio machine.

jcress_NI

Yes I'm aware I would suggest trying again then sending the above details when you can

Additionally (Edit: only do this after checking the file locations outlined below) these are the steps apple suggests if you have any issues with logic but obviously if we can resolve it on ourside we want to but it may be worth working through it
https://support.apple.com/en-gb/119881

jcress_NI

Additionally checking you don't have any NI device scripts in any of the following locations would be good (if they exist there delete them)
~/Music/Audio Music Apps/MIDI Device Scripts

~/Music/Audio Music Apps/MIDI Device Profiles

/Library/Audio/MIDI Device Profiles

/Users/Shared/MIDI Device Profiles

/Users/Shared/MIDI Device Scripts

paulbaarn

I think I've done as instructed, but no change. Same behaviour.

https://community.native-instruments.com/discussion/comment/237517#Comment_237517

O.k., did this again - no success. Here's the screenshot you asked for…

Just a quick update - it works fine in Cubase on the same machine, I just tested it with Korgs MultiPoly, which works fine there (and not so in Logic). So it's probably due to some Logic controller setting or the profile in Logic (?).

paulbaarn

I have monitored the midi messages for DAW mode and for a custom template. For the custom template you see a smooth transition through the values. In DAW mode I see values bunched together, either high or low or medium.

Custom template while turning knob slowly:
[ControlChange channel:1 number:93 [Chorus Depth] value:87][ControlChange channel:1 number:93 [Chorus Depth] value:87][ControlChange channel:1 number:93 [Chorus Depth] value:88][ControlChange channel:1 number:93 [Chorus Depth] value:88][ControlChange channel:1 number:93 [Chorus Depth] value:89][ControlChange channel:1 number:93 [Chorus Depth] value:89][ControlChange channel:1 number:93 [Chorus Depth] value:90][ControlChange channel:1 number:93 [Chorus Depth] value:90]

DAW/Plug-in mode while turning knob slowly:
[ControlChange channel:16 number:83 [General #8] value:16][ControlChange channel:16 number:83 [General #8] value:0][ControlChange channel:16 number:83 [General #8] value:16][ControlChange channel:16 number:83 [General #8] value:0][ControlChange channel:16 number:83 [General #8] value:16][ControlChange channel:16 number:83 [General #8] value:0]

The value is oscillating between 16 and 0, or 127 and 112, or 67 and 1. Those are the values I see in DAW mode and in the plug-in mode.

custom-template-midi.txt

daw-mode-midi.txt

Quick links

Unanswered questions