Parameter jumps after changing presets

Garion2K
Garion2K Member Posts: 14 Member
in Komplete Kontrol

After changing presets in Komplete Kontrol, I'm seeing parameter values jump when turning knobs on my Kontrol S61 mk3 keyboard.

When I select a preset in Komplete Kontrol, the knob positions on the keyboard's screen, the top of the Komplete Kontrol window, and in the plugin itself are updated to show the correct values. But when I turn physical knobs on the keyboard the values often jump, and all of the onscreen displays jump too. From that point forward, the knob positions and onscreen displays remain in sync and the values don't jump again until I select a different preset in Komplete Kontrol. Multiple knobs are affected, and the values also jump when using the mouse to move the Komplete Kontrol knobs and the knobs in the plugin.

Here's some info on my setup: Komplete Kontrol 3.1.0, Kontrol S61 mk3, Komplete 14 CE, macOS Sonoma 14.2.1, Ableton Live 11.3.13 and 12.0b23, Mac mini 2023 M2 Pro. All plugins running in native Apple Silicon mode, using VST3.

It happens with multiple plugins, 1st and 3rd party. I'm able to consistently reproduce it with the following steps.

1) Load the "2 Sided Story" patch in Arturia Augmented Grand PIANO

2) Twist the first four knobs, they all remain in sync

3) Load the next patch ("80's Heartbreak")

4) Twist the first four knobs, they all remain in sync

5) Load the next patch ("1949 Vinyl Felt")

6) Twist the first four knobs. The values jump on most, if not all 4 of the knobs.

7) Load the next patch ("1981 Digital Harp Piano")

8) Twist the first four knobs. The values jump on most, if not all 4 of the knobs.

The same issue happens consistently with MONARK, NOIRE, and many other first and 3rd party plugins from Arturia, KORG, Synapse Audio, GForce.

I have not seen it happen with Diva 151015, which includes support for NKS2. But it does happen with REPRO-1 12092 and REPRO-5 12092.

I have also not seen it happen when running Komplete Kontrol standalone. I have turned off all other MIDI controllers and external devices and removed their settings from Ableton to try to rule out any conflict with another device but that didn't make a difference.

Is anyone else seeing similar behavior?

Best Answers

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,389 mod
    Answer ✓

    @Garion2K Sorry to get back to you after such a long time. Thanks for the videos and the detailed explanation. I can reproduce the issue and will forward this to the devs. Thanks for flagging this.

  • Garion2K
    Garion2K Member Posts: 14 Member
    Answer ✓

    Thank you!

Answers

  • Garion2K
    Garion2K Member Posts: 14 Member

    The problem does not happen in Logic Pro 10.8.1 either, so it appears to be something with the Ableton integration and Komplete Kontrol 3.1.0, at least on my setup. Does anyone using Ableton on a Mac not have this problem?

  • Garion2K
    Garion2K Member Posts: 14 Member

    I've narrowed this down to running the VST3 version of Komplete Kontrol in Ableton. The problem doesn't happen when I use the AUv2 version in Ableton. The VST3 version works fine in Bitwig, so the issue appears to be related to how Ableton works with the VST3 plugin.

  • Garion2K
    Garion2K Member Posts: 14 Member

    This issue is still happening with the newly released Komplete Kontrol 3.2.0 and Ableton Live 12.

    I've logged a bug with Ableton, but curious to know if anyone else can reproduce this.

    As I mentioned before, the AUv2 version does not have the problem but there are other bugs in Ableton with AU parameter automation not recording properly that prevent me from using it instead of VST3.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,389 mod

    I wasn't able to reproduce the issue, slightly different setup, MacOS 12 and Komplete Kontrol 3.2.0. I tried with Noire or Monark and I don't have Augmented Piano from Arturia. Could you make a small video + the steps you mentioned but with a NI product so we can try a repro?

    Are there any other MIDI devices on your system? Can you reproduce the issue with only the mk3 keyboard?

  • Garion2K
    Garion2K Member Posts: 14 Member

    Hi Jeremy,

    I can reproduce the issue with just the mk3 keyboard and no other devices turned on or enabled in Ableton.

    I've uploaded a couple of videos showing the issue using MONARK from within Ableton Live 12 and Komplete Kontrol 3 (v3.2.0 - VST3) on macOS Sonoma 14.4. In both videos I'm slowly turning the first 3 knobs on the keyboard to change Cutoff, Resonance, and Contour. I'm pressing the Next button on the S61 MK3 keyboard to advance to the next preset.

    I don't think this is a hardware issue. It doesn't happen in Ableton Live 12 using the AU version of Komplete Kontrol 3. It also does not happen when running Komplete Kontrol 3 standalone, or in Bitwig as a VST3. It doesn't happen if I use the keyboard for controlling CC values in Ableton with the Default MIDI Template.

    MONARK KK3 VST3 Ableton.zip

    Thank you for having a look at this!

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,389 mod
    Answer ✓

    @Garion2K Sorry to get back to you after such a long time. Thanks for the videos and the detailed explanation. I can reproduce the issue and will forward this to the devs. Thanks for flagging this.

  • Garion2K
    Garion2K Member Posts: 14 Member
    Answer ✓

    Thank you!

  • Garion2K
    Garion2K Member Posts: 14 Member

    @Jeremy_NI Do you have any updates on this? The issue is still happening with Komplete Kontrol 3.3.3 and the current version of Ableton Live 12 (release and beta). Thanks!

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,389 mod

    Sorry, no updates yet.

Back To Top

Categories