I want a hardware knob on my Arturia Keylab 61 to immediately respond to volume down. But it seems like it only will “unlock” if I turn up first then back down while in setlist mode. Is there some parameter I need to tweak?
The knobs on this unit are continuous (no stop at hi or low).
It’s probably the behavior option. Change it from catch to jump
Tried Jump and it’s even worse when I do that.
In performance I just want my volume knob to immediately but smoothly respond to volume down.
It seems like “catch” only responds in one direction (up).
Instead of setting an Absolute value, if it’s an endless encoder you might be able to use one of the relative modes. You would need to configure your Arturia to send relative CC messages, and then configure the widget to use the same relative encoding. I don’t own an Arturia, so this is theoretical advice.
I did find this link on the Arturia site: https://support.arturia.com/hc/en-us/articles/4405741265810-How-to-switch-between-Relative-Absolute-Mode-with-KeyLab-controllers
The benefit of this approach is the immediate control while also avoiding nasty jumps of parameter values … no wait for your widget to catch the current value before changing it. Most controllers are set to send Absolute values, so the downside is the extra configuration required.
Try control mode “relative”
I’m not having any luck just yet. Tried experimenting with Arturia midi control center to apply relative setting in accordance with GP settings (where sometimes that parameter is greyed out). Any Arturia users been down this journey?
Updated the thread topic for specificity.
Looking at the Arturia support page posted above, the Relative 1 setting would correspond with Relative Offset in GP.
Me 
What exactly does not work? Setting the Arturia knobs to relative, or the widgets in GP?
BBB
I will attempt this tonight. Thanks!
So happy to report that I finally got this working! What was happening was the encoder knobs settings within rig manager, had defaulted to absolute which was overwriting my relative offset setting in the widget and Arturia definitions. Once I fixed all that everything is now working flawlessly. Thanks to this community!
