How to implement a knob controlling a second knob

Question

This layout controls Other/Unlisted Maker

I am trying to design a simple function with the following desired behavior

    Tap tick once, Knob 5 advances 1 tick

     Knob 5 wraps around, Knob 4 advances 1 tick.

     Knob 4 wraps around, Knob 3 advances 1 tick

When Knob 5 wraps around, Knob 4 advances 2 ticks, not 1.

What am I missing? I did not connect Knob 4 to Knob 3 yet. I use Named ticks in Knob 5 to trigger the Stepper button to try to advance Knob 4. It triggers at wrap around OK.

Downloads: 425
Download 1
Downloads: 425

Answer 1

Make the tick button "send on only" - MDP2 evaluates the named tick value on both the on and off action, which sends a double action in this case.  I do not believe this is a defect, just a feature, which mostly is good.

Comments

Thank you. I had to have any button driving knobs set to "send on only" to make it work. Not obvious that both the on and off action triggers a step.

---

"Not obvious that both the on and off action triggers a step."  Not exactly what I said.  A "stepper" is triggered only by a momentary button going on.  I will repeat the cause for emphasis.  When the tick button changes state, the subcontrol values are evaluated and sent.  In the off direction, the knob 5 does not advance, but the MIDI value of 127 is retransmitted, which sends a repeat "on" command to the stepper button, causing a duplicate step.  Stepper has never gone off, but had the on state triggered twice.  And you do need to apply "send on only" at every level where this can cause an issue.

---

What happens without 'send on only' is different for the second and third Knobs. The second Knob does change 2 steps at once as you state.  However, the third Knob does not change 2 steps at once, but changes one step when it's Stepper Button goes on, and again when it goes off (one tick later).

But the cause doesn't matter in my layout. As long as they step as intended with 'send on only' applied to all stepper buttons.

Answer 2

Make the tick button "send on only" - MDP2 evaluates the named tick value on both the on and off action, which sends a double action in this case.  I do not believe this is a defect, just a feature, which mostly is good.