Can I make one encoder encode faster?

[mlib]

@ggmanestraki

For relative controllers, it could be an open field that we fill in. (So that we could have an encoder with a “resolution” of 2, that would work like a switch, an encoder with a resolution of 40.000 so that we could do 0.5 hertz steps in EQ, an encoder with a resolution of 100 so that we could eventually reach that high frequency. Or we could just set the resolution be the same on all encoders and have some kind of shift button that multiplies by 100 or divides by 100.

I agree 100%. This is the exact reason I started this thread:

MIDI Remote, Relative value mode

Thank you Steinberg for including different relative value modes. As I see it, the downside with using Absolute MIDI CC values is the limited resolution of 7 bits (0-127). Using an encoder that sends Relative MIDI CC values can potentially overcome this limitation. Unfortunately, Cubase 12 currently does not take advantage of this as the scaling of the controller value to its destination is fixed and cannot be altered. Example 1 (Absolute CC value): The controller sends CC values between 0 …

@ggmanestraki

This is all for the surface editor. For scripts, I’m certain there are ways to do much of this.

There are workarounds. But they seem to introduce their own set of issues. Especially if you want some feedback on the current value of the encoder (ring LEDs or displays for instance).