I spent some time today looking again at the wiki. I’m trying to understand some things like the CUIA to help interaction with the sequencer and other things. One thing I have noticed is how much these types of phrases appear: SHORT PRESS SELECT, BOLD LAYER, LONG PRESS LEARN etc.
It made me wonder…is there a visual way to represent this action to understand it at a glance? I came up with these examples. The four dots represent the encoders/buttons of the zynthian box, the icon to the right is an indication of time (I think I already have another idea for how this can be shown).
So from left to right: long press select, bold press layer, short press layer
My idea/suggestion is that these could be included as icons in the wiki that fit next to the text description of the button press. Of course the V5 kit is almost here so this icon might need another one to represent that too. It could get a bit cramped showing them all vertically at small scale though.
Are there reasons this would not work? Or can others think of some other suggestions/modifications? I just felt that it helps my brain (and probably others) to be able to glance at the instructions and get a visual reference that can be understood quickly.
With that said, I’d like to contribute to the wiki in some capacity. Can someone allow access for this? I was thinking about adding to the doc about headless tutorial as that’s been my experience of learning to use zynthian.
This is a cool idea but as you say, the 2x2 switches change to 1x4 in V5. It may be possible to dynamically change the indication so that the appropriate icon is shown if you select a different device but I’m not convinced the wiki supports this.
Instead of showing the clock we could use different colours or icon on the actual pressed switch. We could also use a different representation for each switch and just show that rather than its position within the layout although that may lose much of the benefit you propose.
The idea is good, but V5 workflow is very different to V4 workflow and the way switches are used is very different. Anyway, your idea is good in essence, so it should be profited in some way.
Regarding your offer for helping with the wiki, i will create an account and send you the credentials by PM.
Within the new colour mechanism the opportunity to display a staus colour might address this concern.
It is a issue when no screen is visible ( a remote control device at some distance from the zynthian for instance) in such a situation if one wants to shut down the device with a Long press on the Select encoder you have no direct indication that the message has been recieved and the screen is in fact displaying the Are you sure dialog.
A single RGB LED could encompass this concept by displaying or flashing at the time when information is requested in particular colours that represent known states.
In essence I can turn my cajon off in confidence by simply watching the colour inside it change. IT then successfully shuts down fifteen or so seconds later.
I am aware that this is not an issue within the kit environment but does provide genuine feedback potential and unification of the overall control loop.
I understand that colour is not regarded as an effective feedback device in all cases,. Colour blindness provides issues and total visual impairment obviously cannot benefit but the reassurance such mechansism provide allows one to shut a device off and proceed to the next aspect of the performance without waiting to know that the device has successfully accepted a Shut down for example.
Webconf debug mode could allow this to act as a useful debug tool.
For kits to confirm receipt of messages from encoders and switches.
I’m not across the V5 changes yet, or even <=V4 controls for that matter as I don’t have a kit. I actually just wrote that sentence about shutdown as an example of the icon being used in the wiki.
But…continuing off topic…I noticed when I hit C-1 using the midi keyboard, it shutdown immediately. I can see why this might be desired for a headless or remote setup like you say.
When I use the touchscreen (via VNC) it asks for confirmation.
This emerged from a discussion on zynthclub, many moons ago, when we speculated on what could be the smallest usable screen size and obviously a 1x1 pixel is nothing more than an RGB LED.
I’ve been using the cajon with a remote control that drives the mixer screen and it works rather well in that you have audio confirmation of actions and don’t need the screen.
The only lack you have is knowing which chain you are addressing.
I use a vnc screen in Read Only to monitor the zynth, but ideally this isn’t something that is required to operate the deivce.
Some other chat with low life individuals in the dark underbelly of the zynthian world felt it should light up internally…
I’s basically a GUI design exercise in what is required versus what is wanted.