Widgets + Komplete Kontrol's prev/next preset selection switch MIDI interaction issue

[Vaultnaemsae]

This all started because I was trying to use MIDI program changes to select presets in Equator 2. It was an exercise in confusion and futility…try it and see for yourself! I gave up. Apparently, it will work if you use a Roli controller though I’m not sure what order of messages it sends.

To overcome the issues with remote browsing presets in Equator 2, on a KVR forum member’s recommendation, I started using NI’s Komplete Kontrol (KK) plugin. It appears to be potentially useful for remotely selecting presets when setting up/exploring configurations that you might want to save for use in a dedicated rackspace. It’s got a nice preset filtering system and MIDI-assignable preset scrolling functions.

Now, I’m having a basic yet perplexing issue. Preset scrolling is supported in KK but only via CC messages. Any value (0-127) sent on the assigned CC will trigger movement in a specified direction, but not when it’s the same value. i.e. 0, 1 = will step; 0, 0 = will not progress. This seems to be the issue. I tried using a dial but that seems not the right approach also.

So, I can load KK in the global rackspace, put in place two widget buttons — one assigned to CC 20 (prev) and one to CC 21 (next) — then connect these to automatable parameters in KK (among the several thousand automatable parameters are direct CC commands.) When I click on one of the momentary-touch widgets (buttons), KK steps through two presets, but I only want to make one step at a time. So, I tried using a toggle state. This “works” but it is confusing because the LED on/LED off states have the same function, only with a different visual representation.

How can a make I momentary button that alternates values 0 and 127 (but realistically 127 could be any number from 1-127) each time it is triggered without showing an on or off state? Is this even possible? Am I overthinking this? I’m trying to set it up like this so I can eventually control the widget with an external controller.

After a few unsuccessful attempts to make it work, I recall having had the same issue with Neural DSP plugins when trying to use the automatable arrow keys to scroll presets. Is there a best practice here?

[pianopaul]

I cannot reproduce.
Are you using this setting?

[edm11]

@Vaultnaemsae

How can a make I momentary button that alternates values 0 and 127 (but realistically 127 could be any number from 1-127) each time it is triggered without showing an on or off state?

I accomplished this with a scriptlet wired to a MIDI Out block. It sends alternating CC values of 127 and 0 to whichever CC number you choose.
Add a Pad widget and assign it to the Send parameter.

Var
CCNum ("CC") :parameter 0..127 = 0
Send : parameter "On" , "Off" = "Off"
Alt : Boolean = True

// Called when a parameter value has changed
On ParameterValueChanged matching Send
    If Send == "On" then
        If Alt == True then
            SendNow(MakeControlChangeMessage(CCNum, 127))
            Alt = False
        Else
            SendNow(MakeControlChangeMessage(CCNum, 0))
            Alt = True
        End
    End
End

[Vaultnaemsae]

@pianopaul

Are you using this setting?

Interesting, my parameters at 901 are empty…I didn’t know that was even an automatable parameter. Anyway, selecting 901 doesn’t send a message to trigger the next preset when selected. I’m on macOS and I’ve tried out VST3 and AU with the same result.

I was sending the message to a MIDI block (IAC driver) and selecting the automatable MIDI CCs that are available as parameters in that internal plugin.

@edm11

I accomplished this with a scriptlet wired to a MIDI Out block. It sends alternating CC values of 127 and 0 to whichever CC number you choose.
Add a Pad widget and assign it to the Send parameter.

Thanks, I’m going to try this scriptlet out. EDIT: Perfect. Thank you so much. This scriptlet does exactly the job required!

One thing I’ve determined (at least I think this is correct) – if it were possible to randomize the sent value (0-127) and block every second value, assuming there was never a duplicate, it would achieve the desired result.

[Vaultnaemsae]

@pianopaul

I cannot reproduce.
Are you using this setting?

OK, the plot thickens on this point. It seems that the automatable parameters that expose themselves in GP5 under Komplete Kontrol (KK) are not necessarily KK parameters! They seem to be changing with every new synth/preset you load in KK. I realoaded KK and opened a MiniFreak V preset. Instantly when I searched “next preset” it was visible but with a different number (I think it was parameter 257). It seemed to be controlling the selection of presets within the loaded plugin, not KK parameters. Very confusing. I’m sure it’s a KK issue and not a GP5 thing but it’s def worth looking out for if you’re a KK user.