How can I prevent a stepper knob from rotating past its maximum value straight to its minimum?

Question

I have made what is a fairly simple layout for switching Stage Settings on a Casio Privia PX-5S keyboard.

The layout has a button that sends the Bank MSB and a knob to send the Program Change. Another knob (we'll call this the Selector) is set as a supercontroller for the Bank MSB button and the Program Change knob. The Selector knob is also controlled by two buttons, "<" (inverted) and ">" to step backwards and forwards through the Stage Settings, 0 to 99.

The problem is that, using the ">" button, when 99 is reached the next press of the button rotates the Selector knob to 0. The opposite happens with the "<" button. In other words, the buttons cause the Selector knob to continue to rotate with each press of the button.

Is there some way to prevent this, so that the knob only rotates from 0 to 99 or 99 to 0, just as it does when controlled directly?

Comments

Hi Teekay and thanks for the question. For right now this would be a "suggestion" as there's no way to limit the increment/decrement buttons... they always wrap.

I do wonder if wrapping is EVER a good idea, though, too.

We'll meditate on this as a feature suggestion.

Thanks, best!
Dan

---

Thanks Dan. I have another situation where this is undesirable - with a transpose setup. This is uses buttons to step through a range of pitch shifts from -12 to +12 semitones, and another pair of buttons that provide full tone (2 semitone) increments. A problem occurs when you reach +12 and press the button again... it jumps to -11. So as you can see, having a means of stopping the knob from wrapping is essential in that situation.

Regards
Teekay

---

Thanks for this. Let's see when this suggestion can get into MIDI Designer.

---

An even more serious problem with the wrap-around, if you're using a MIDI slider to control volume on an instrument or a mixer.

When you hit the bottom of the volume slider and the next decrement goes to full volume! Extremely dangerous.

I agree wholeheartedly that there really is no reason for it to EVER wrap-around, so why not remove that "feature"?

---

Hi mr-x, I've moved your post from an answer to a comment...I hope that's OK with you!
I can assure you that this issue has been noted by Dan and is sure to be addressed when time permits, but there are many more pressing issues that need attention due to the need to comply with the latest version of iOS and Apple's new programming language. I'm sure we can live the current situation in the short term.

---

Hey there, thanks for the discussion, all. We're definitely considering this, but -- while I agree with the logic for removing this -- changing functionality that users depend on has to be done carefully, and probably with a global option to turn it back on. For now, what teekay said is correct: your patience is quite appreciated.

So teekay: in your setup, the wrap-around is NEVER desirable?

---

Actually, scratch that question: for program changes it's definitely useful. This'll need to be an option to move it ahead. And an informal poll today revealed that some users find this useful, so that's new news.