Not very effective, haven’t heard anything back, the bug is still present in 4.0.1 and it makes Twister’s relative knobs painful to use with automation. To restate, when moving the knob (with createRelativeBinOffsetCCValueMatcher) it ignores the current automated value and offsets from the last known hardware knob value — even though the LED ring display is correct. In other words, knob.targetValue() is correct, but hardware knob is apparently not aware.
I can help explain how to reproduce this, but it will probably help if someone else sends in an additional bug report. Sent a followup email.
Read more here: Source link