@ingox , man just as I was starting to feel pretty comfortable with pd.... wt...? [text...]... will look into those

And here is an example usage with one button and one knob controlling two inputs/parameters

no sorry necessary, I know how to code, but pd is different way to go about it and I'm just barely starting to understand some of the common patterns. My uses of [route] thus far always seem to simplify down to using [select]...

Below is the above idea as an abstraction.

packing the data that way and using route is interesting and has me thinking....

@whale-av, thanks for the reply. I don't think I totally described it. I'll finish, it's short...

[ab_sigcross] emits a 1 when it detects that two values have crossed, I use it to see when the current control value has caught up to the stored value.

The output for the parameter is the [f][73] lower right. There's no using of the parameter in her yet , just trying to make the multi-mode thing work in a generic way so that I can reuse it.

I'm writing an abstraction now which will probably help clarify as well.

Thanks again!

I've been building some patches for the Befaco LICH modular platform which has potentiometers for the parameters that come through the framework as floats in [0-1]

Having run out of knobs on the LICH... I'd like to make it multi-mode so that each knob can control multiple-parameters, one per mode. The knob should remember (and output) each modes' value as the modes are changed. In the event that the knob and it's value get out of sync, it should have a simple way to re-sync the control, like turn it past it's previous value to re-sync.

I have a couple "working-ish" versions but I feel like I'm working too hard at it (against the system?) and there is a more straight-fwd approach that I am not seeing. Does anybody have any experience or thoughts on handling a multi-mode parameter gracefully and implementing it in Pd?

2-mode-param.pd

ab_sigcross.pd