UI idea: SELECT as a parameter-bank selector

[gospodindilly-ops]

I have a UI/implementation idea that could simplify the parameter navigation quite a bit.

Since the UI already works around groups of four parameters mapped to K1–K4, could SELECT be used to switch between parameter banks instead of opening separate sub-pages?

There is also some duplicated navigation in the current SEQ UI: on the sequencer pages, PRESETS and K1 can both be used to move the step cursor. It feels like this control could be used more efficiently.

For example, SEQ could have one unified editor:

• Bank 1: STEP — position / note / time / flags
• Bank 2: PATTERN — length / division / swing / gate
• Bank 3: CHANCE — step / chance / ratchet / etc.
• Bank 4: AUTOMATION — relevant parameters

SELECT would switch the active bank, while K1–K4 would always edit the four parameters of the selected bank.

This would make the sequencer feel like one unified editor and remove a lot of small submenus.

For other menus, the same concept could be taken further: instead of having separate screens for small groups of parameters, one screen could show up to 12 parameters (3 × 4) at once. SELECT would choose which group of four is active, while K1–K4 edit that group.

This way, you could see all the related parameters and their current values on a single screen, while still keeping direct K1–K4 control. It seems like this could reuse the existing parameter structure with mostly UI/navigation changes rather than requiring changes to the underlying parameter system.

[kurogedelic]

Thanks for the detailed proposal. This fits with the SELECT ideas in #84 and #79: I'm planning to rethink navigation (what SELECT does, pages vs banks, the duplicated cursor controls on SEQ) in one go for 1.2, and I'll use this as input.