Zynbleton Vangelis - READ ME

SIGNIFICANT CHANGE TO TOUCH

I have just pushed an update to vangelis that signifcantly changes how touch works.

What
We have removed the touch-only workflow and replaced it with V5 button overlay. This results in 2 supported workflows:

  • V4: 4 rotary encoders with switches, optional touchscreen
  • V5: 4 rotary encoders with switches, 20 push buttons, 5" (or larger) touchscreen
    Touch-only will use the V5 layout with emulated buttons and encoders.

Why
Maintaining 3 official hardware workflows (V4, V5, Touch-only) has proven too much of a challenge. Code, documentation, user support, etc. This simplifies all of this and offers more consistent workflows across hardware configurations.

When
This is the roadmap for vangelis. Oram will not change. This will be the only touch-only workflow for vangelis.

Who
Many thanks to @wanthalf for the inspiration and inital implementation of this and appologies for the amount of butchering I have applied to it, e.g. flattening the buttons to a single canvas (optiisation).

Where
Hopefully on your TEST system. A reminder to not use vangelis branch for production.

How
Most of the touch-only workflows have been removed. After this update the system attempts to detect your previous touch configuration and set the new configuration… but if this fails you may need to reassert the required config in webconf INTERFACE->UI Options, Touch Navigation.

Touch actions are now (click==tap):

  • Short/bold click Status Area (top right): Toggle V5 buttons.
  • LONG click Status Area: All Sounds Off.
  • Short/bold/long click Topbar: Navigate to mixer/launcher or toggle mixer/launcher.
  • Short click mixer chain legend strip: Navigate to chain control view
  • Bold/long click legend strip: Navigate to chain manager view.
  • Short click launcher: Toggles launcher play state.
  • Bold/long click launcher: Access pattern editor or phrase menu.

Please give us your feedback on this. There was a lot to implement and probably more to fix so please report issues, ideally in the tracker. If you are sure you have an issue with this migration to V5 button overlay then you may add a comment to this ticket.

5 Likes