I have a midi fighter twister. It really bothers me that when I program a twist knob to “reset”, it first sends a CC value (pushing down) of 127 before resetting the knob to a CC value of 0 (63 if in detent mode). The manual states that “In this mode the switch also sends a MIDI message as if it where configured for CC hold”. This “feature” of sending a CC value of 127 before reseting (up on knob) is super annoying. Does this bother anyone else? What’s the use case for this? There’s already a knob setting for this, it’s called “CC Hold”… “The switch will send a CC of value 127 when pressed and a CC of value 0 when released”. Is this a bug? I don’t suppose there is a firmware upgrade in the near future? If so, please make the “reset” feature reset without sending the high CC value.
Another thing that can help is forcing the software to refresh the LED/encoder state after the reset, so the hardware and software stay in sync. It can save a bit of confusion if values get out of step during a performance.
The logic behind it is being able to still map the button assign to reset encoder to potentially reset/update other parameters in software.
If set to reset 127
Received: ch1 CC0 vel=127 (b0 00 7f)
Received: ch2 CC0 vel=127 (b1 00 7f)
If set to reset 0
Received: ch1 CC0 vel=0 (b0 00 00)
Received: ch2 CC0 vel=127 (b1 00 7f)
If detent is enabled
Received: ch1 CC0 vel=63 (b0 00 3f)
Received: ch2 CC0 vel=127 (b1 00 7f)
In the examples above ch1 is the ring position and ch2 is the button’s state so the later will always send 127 on press and 0 on release respecting the channel and number assignments set in this section.
Note: Reset (127) was introduced in the 2026 firmware. If any of you still have issues of one affecting the other try updating to a newer firmware
Regarding being able to set a custom reset value, this would have to be a per encoder setting and that would not be possible due to Twister’s current RAM constrains so it would either have to be a global setting or have fixed values like we have now (0/63/127)
