UserControls and HardwareButtons

[Kirkwood West]

I'm working to create an extension for a buddy that wants to custom map the buttons on the midimix using right click remote mapping. That works fine but then the Leds don't function.

For one, I can't seem to get the UserControls bank to populate. So that class seems to be pretty unhelpful.

So I dug deeper to see how the Dozius Twister Sister handles this with their Knobs. I found they use the HardareKnob and there you can observe the target value. So that is one way...

Here I'm using a HardwareButton, so it seems to only be pressed() and released() which calls Actions defined in code and I can't seem to find a target value in the class.

Any suggestions about how to accomplish this?

[Kirkwood West]

I will try another solution using the new project remotes for mapping, suggested by minortom on the #controllerism discord. I think it will be cool.

Thinking to fill in banks of the project remotes and use tagging to make the controller point to specific sets of remotes.
midimix_mute
midimix_solo
midimix_rec

Then provide options for different knob/button rows to choose the project remotes instead of standard bank behavior.

[Kirkwood West]

Also quickly observing that its impossible to connect solo or arm buttons to project remotes. Still looking for solutions...

[Kirkwood West]

i'm thinking to create a new extension based on 8 cursor tracks that can be assigned anywhere and providing an option via config to set each control to a specific parameter. i.e.

Code: Select all

MIDIMIX_KNOB_1_1 = SEND1
//SEND1, SEND2, SEND3, SEND4, SEND5, SOLO/CUE, MUTE, ARM, VOLUME, TRACKREMOTE(1-8), PROJECTREMOTE(PageNum)(ParameterNum)

Doing the Cursor Tracks will be simple but might be a bit tricky to set up each knob via xml, json, toml whatever. I think it will be a decent solution for those that want to get funky.