New touch screen build

I did some testing of latest oram touch capabilities and I found the following:

Titile bar:

  • short press on title bar opens main options for that screen
  • bold press on title bar opens sequencer screen
  • long press on title bar opens admin screen

Status Bar:

  • short press on status bar opens metronome
  • bold press on status bar opens subsnapshot (zs3)

Chain bottom:

  • short press opens controls
  • bold press opens chain options menu

What I could not found is:

  • how to consistently go back to mixer. For example, if you are on control screen, bold press on title bar will still open sequencer and left arrow on title bar will go to presets screen (not back to mixer which was previous screen). Even when in presets, bold press on title bar will open sequencer. It is only if you are in bank screen bold press on title bar will open mixer. This is very confusing.

  • how to open snapshot screen without going through mixer options menu’s

Am I missing something ? Going to snapshot screen only using mixer options menu maybe is ok but going consistently to mixer screen is important. Should we have long press on status bar to always lead you back to mixer ?

Also we should have consistent use of left arrow in title bar. Sometimes it is used to go back to previous screen and sometime to go to presets. Can we have presets button as additional button at the bottom where previous, pages, hide controls, and next buttons are instead using left arrow in title bar. Do we really need hide controls button and can we use it for presets instead ?

Hi @stojos

When touch navigation is enabled in webconf, a virtual button with a left arrow should appear in the upper left corner of the screen, at one end of the status bar.

This is where you can return at whatever time to the mixer panel.

First, thanks for trying this. Luckily, all your observations have already been considered and most have been documented. (Press Touch at the top right to show touch UI docs.)

Some basic principles:

  • Short tap topbar title area acts as a menu button. First press to show context menu (if any). Second press to show Main menu (called Chain menu on V5).
  • Bold press topbar title area to go to zynpad.
  • Long press topbar title area to go to admin menu.
  • Short tap back button (top left) to go back to previous screen or canel current operation. (There are exceptions - see below.)
  • Bold press back button to return to mixer
  • Long press back button I think should also return to mixer but does not - that may be a bug.
  • Short tap status area to show tempo, including transport buttons.
  • Bold press status area to access ZS3.
  • Long press status to send all notes off (panic).

Snapshots are seen as a low frequency access workflow. The idea is a snapshot is used to configure the zynthian for a performance or session then zs3 are used during the performance which is why zs3 access is fast.

I agree with you that back button in chain control view to access presets is not intuitive. (I have been lobbying against this for years!!!) But it is the workflow by design and hence retained in touch UI. Previously I had a button on the button bar to access presets but removed it because of this workflow design. We could put it back in place of the Hide Sidebar button (which is there because we have reduced display due to the button bar). It could (as it used to) direct access preset / bank based on short / long press. Lets get more input on this and also, see how people get on with this workflow info.

Another oddity is bold press back button in pattern editor goes to undo/redo which breaks the bold-press-back-to-reach-mixer policy. Again - I don’t like it but we needed some way to access this.

Hopefully this info helps to understand the touch UI and may assist with further feedback.

2 Likes

I disagree. I use snapshots a lot

Well its just two taps for snapshot from mixer:

  • Tap topbar to access main menu.
  • Tap snapshot entry in main menu.

There will of course be workflows where you want to change the whole zynthian configuration, but many will be able to configure what they need in a single snapshot, using just the chains they want and changing presets and parameters for each part of the performance. This is possibly the most popular (or expected) workflow.

I know there are many users who are using various workflows, either because they are unaware of preferred (designed) workflows or because they have requirements that are not suited by those preferred workflows. As we garner more examples, we will document common workflows.

Anyway - my current interest in this thread is whether the work done to improve touch UI has been worth the effort!!! :blush:

2 Likes

Thanks for the updates to the touch interface.

I would like to vote for the return of the preset button instead of the hide sidebar button.

1 Like

@riban thanks for explanation.

Bugger, I did not see that there are different docs for V4, V5 and touch user interfaces. This selection is not that obvious in docs.

Now I know - bold press on title bar back button is always going back to mixer screen.

Testing further back button on title bar I found another oddity. If you have fx first in chain that has no presets (e.g. Calf compressor), short press on back button will do nothing when you are on chain control screen because FX without presets is selected first in control screen. In this case it should go to previous screen. It confused me a lot when I was testing touch.

1 Like

Yes - I agree. I will change the touch UI back behaviour in chain control view to be more intuitive. This will not change the behaviour for V4 encoder back switch

Okay - it is done.

  • Touch back button now returns to previous screen.
  • Button to access presets.
  • Bold press status to go to ZS3 (like before). Bold press status in ZS3 to go to snapshot.

There is still the oddity that pressing back button in preset list will take you to the bank list (if there are banks). I don’t want to change this because this particular workflow is by design and would require some consideration before any changes.

1 Like

All tested and it works !!! It is much more consistent now. Thanks.

5 Likes

I think it has, I can get where I want to go with a lot less touches now!

2 Likes