Comment by smj-edison

There are loads of systems where every button and encoder has many functions, with modal or paged interfaces. But I'm trying to stick to a model of no hidden or ephemeral state with my modular, just for fun, I guess. Mostly analogue, so no non-volatile memory to store settings, the positions of the patches and knobs set everything, and the test is that if I power it down and back up it must come back doing what it was doing when the power went out (very long cycle lfos notwithstanding!)

When a laptop can simulate anything, the physicality of the interface is most of the attraction, so might as well go all the way...

The physical interface is an intrinsic part of the design of any eurorack module, including artistic elements. If you actually use these, then you quickly tire of menu diving for simple options, and only modules that do very particular things make it worth the bother. For everything else, the layout must be accessible, memorable, understandable, and not too crowded. And it helps if the visual of the thing conjures up memories of how it sounds or what it does.

If you had a little silkscreened circle around each parameter's LED, and a Hall effect sensor underneath, you could even make a passive magnetic knob that you could use to adjust parameters by simply placing it on top of them and twisting. It wouldn't feel great due to the complete lack of resistance but it's a fun idea :)

There was a trend in 80s synthesizers along these lines: Yamaha DX7, Ensoniq Mirage, etc.

They were famously hard to program. The DX7 in particular is known for basically being a preset machine because almost no one could figure out how to build patches with it.

Muscle memory is really important and it's hard for users to build a mental model of the internal architecture if the external architecture doesn't reflect it at all.