I need to print this out. This probably explains things in a way that makes more sense than the manual, where it will probably sound good on paper but be a head scratcher in use.
I’ve spent a grand total of 30 minutes using the device UI, so I can’t really offer anything meaningful beyond “this is what a moron would try to do, or think, looking at the controls as a newb”
There is a gravity to the big knob (that’s what she said) which really at first doesn’t seem to do much since you have to use other navigation buttons. Ive reached over to that out of reflex more than a few times for sideways scrolling, and tried to click it a couple times. (And it’s the only kob without click functionality) You sort of expect that to play a much more prominent navigation roll.
30 minute newb opinion:
- They should have considered putting an “open” button in between the dpad nav buttons. That would make some sense so you don’t have to move your eyes to a different area and play Russian roulette between “do I hit the edit button or enter?”
- If the page arrows are ways to cycle within a particular context (assuming you got that far) they would have made more sense directly over or under the screen, not directly under the nav arrows.
That really seems to be the crux of it, trying to figure out when to hit enter vs edit, and page arrows vs nav arrows vs the big scroll knob.
Doesn’t really matter as this thing will live tethered to FM3 95% of the time, but I think I’ll put enough effort in to at least be able to create a patch entirely from the device. Just to say I can do it.