Using encoder presses to change encoder functions.

Do you need value pickup / memory for each state while the module is plugged in?

I’m not sure—what does that mean?

Encoders are absolute by default and with outboard gear it's often good that they are absolute: relative +1/-1 input from encoders is usually not processed correctly in those situations

But if we just switch the CC of the encoder, then their value will still remain the same

And value jumps can occur

To avoid that, it's a bit more complication to add previous value recall to the encoders

For a start, if value jumps is not a concern, then you can change the button to have 3-steps. The button will have 0, 63 or 126 as it's value.

Then on the encoder event, you can add an if block with an else if and else branch. In those branches, check the button value by calling self:button_value() and add self variable action blocks which will hold the cc value on your encoder.

Then you consume this cc as self.cc in the midi action block.

Oh that's super helpful, thanks! I think the Disting NT actually handles relative CCs, so the approach you described would be just fine. If I needed to send absolute values and I wanted the previous value to be recalled when switching between the three modes, I gather I would use some variables for that somehow?

Yes, preferably a table which can hold multiple values, or variable like self.cc1, self.cc2 and so on

Hi @user could you share a snippet that handles also value recall?