Dunno about that, i’m fine with most of these controls, as long as they’re well implemented.
So for example, if you were to add buttons, pls don’t take the generic " Button press sends button down command to device " approach, but rather just do it smoothly on board, for example :
( wait for confirmation of intent, if button is held for more than 200ms, start routine, otherwise ramp up by fixed amount )
( for as long as the button is held, update at some rate, like 100 times a second, increase/decrease the gain a small amount based on the direction of the button )
( Maybe throw in an ease curve in there, maybe not )
Implementation Notes on this : On iOS you can set the absolute device volume based on internal playback volume on the headset, so you’ll be able to provide full volume range without any extra work involved, while Android doesn’t have the API for that so that’s a bummer for android users who’ll have to deal with two volume bars. On windows, same as android, but that’s the expected behaviour.
With dials it’s just dials. I’d love dials. Dials are the best. But you’re going to have to do a circular cup design for dials. Or tack it on as a small thing somewhere on the edge. At which point it’s just a little better than a pair of buttons.
And touch, if you have a Zik2/Zik3 in the office, just do that, that one does it almost perfectly, except the leather surface, which stretches and deforms if you’re not gentle.