Hi creal,
I think it’s a widespread bug (on Windows 11 at least).
My Keystep37 first knob won’t map at all in Pigments, AL, Prophet (presumably other instruments). Would you confirm it’s not specific to CZ?
In Cubase, turning the first knob on a midi track registers as a midi event. But no learning possible with first knob.
Learning with first knob is possible with my old Yamaha Cp33 Stage piano.
I loaded Keystep 37 in Midi Control Center, changed the CC value of first knob from 11 to 10 and the K37 first knob now works in CZ V and Pigments.
I tried setting first knob CC value to 11 to no avail. CC# 11 is an unlucky value.
On my side, the first knob sends CC74. I can monitor the values thanks to the “MIDI Monitor” Ableton device.
When I add the CZ V, I can see the default mapping for the Keylab MK3, which specifies that CC74 controls the Brightness macro. But when I turn it, nothing happens.
I haven’t tested all the Arturia plugins, but it seems that, on my side, only CZ V is affected.
Maybe a Keylab MK3 owner can help to check this bug, please?
I have just checked the two instruments as much as i can without having the controller.
The MIDI Configs are for/ in the instruments.
It look like there is something wrong with the MIDI Configs and the controller parameter assignments when using the Keylab MK3 controller setting and Keylab MIDI config.
I think there is something strange going on with the Macro parameters and/ or the assignments. Perhaps the Macros appear with two names.
Please contact Arturia support through your account.
You can also construct a new Keylab MIDI Config yourself i assume.
Please note that, as for the touching knob bug, everything works as intended with standalone apps. So there’s definitely a problem with the VSTi. If I had a Mac, I could try the AUi versions, but it’s the case, unfortunately.