Vangelis (technology preview) progress

[hannesmenzel]

@riban

This is a “hardware->wiring” error as previously described be @jofemodo .

You mean this I guess:

@jofemodo

Users who customize the wiring profile are responsible of keeping it up-to-date with changes.
We could add more heuristics, but we can’t cover 100% of customization cases.

Therefore:

@hannesmenzel

EDIT: Ok, I just switched wiring config to something else and back to my recent MCP23017 V5Touch layout and reverted the right pinout values, and now it works.

[jlearman]

I’m using “Custom” (I think that was the default) for my no-hardware build. I don’t have any customizations nor do I know how to do them. Also, switching to A5 and back had no effect.

[hannesmenzel]

Look in the wiring setup for the entry where “Back” is configued as short press (Probably Switch 13 or so). It might be configured as UI action push. If you chose another profile and get back to custom it should be saying something like UI release action then. Can you confirm that?

[jlearman]

It says “Zynswitch.” But gee, now I have a way to find out what does what! I hadn’t looked here before.

It worked!

However, after reset, I had to also change my audio card and screen type back. Now it all seems OK, but the green heart in upper right corner is now a green circle arrow, whatever that means.

[jlearman]

@jofemodo

Users who customize the wiring profile are responsible of keeping it up-to-date with changes.
We could add more heuristics, but we can’t cover 100% of customization cases.

Right, of course. But it might be nice to retain the defaults for no-hardware builds, for people who’ve made no changes to wiring. Or perhaps, add a “no-hardware” option in the wiring list.

PS: I recognize that keeping things consistent for so many use cases is a nightmare, and my heart goes out to you all!

PPS: somehow my wiring changed back to V5. When going to fix it, the wiring list seems to have completely changed, with lots more options, and I now see “touch only” which I think is what I want for no-hardware. So, the issue seems more like the initial menu of wiring options was different at first? Maybe held over from Oram somehow?

If this is just a snag caused by upgrade, less of an issue.

[jlearman]

I added a sfizz chain and picked a sampleset. Now I want to change the sampleset. On Oram, that was obvious. On Vangelis I have no clue. What happened to the Presets menu?

[OutOfCheese]

I’m sorry, having no experience with the no-hw setup I thought if you can somehow press a virtual opt/admin button there would certainly also be encoder buttons… turns out that was wrong.

The green circle means there’s an update available - since this is the development branch this will happen A LOT (and may or may not also break stuff that used to work). The circle doesn’t mean you HAVE to do the update, just that it’s available. If you plan to use the box for jam sessions then if you’re on a relatively stable version maybe hold off on updates you don’t absolutely need.

[jlearman]

Thanks! I’m just fiddling, and as I hope to contribute to the project, I figured I should be using the latest. I won’t be using Zynth for anything significant in the foreseeable future.

[riban]

@jlearman

What happened to the Presets menu?

Pressing the Preset (on screen) button should show the preset menu.

[jlearman]

I don’t see one. Previously it was at the bottom of the screen, along with “next” and a couple others, but that section doesn’t appear.

[tunagenes]

New screen, overcame rotation issue, but now lost in touch & resolution space

If you don’t already have this set: In webconf, INTERFACE->UI Options, select Touch Navigation=V5 keypad at left or a different option if you prefer.

[jawn]

To add a different voice, on a hardware device like V4 I am glad to have this always accessible way to get to the Main Menu.

Cheers

[riban]

We have removed the old touch navigation. You must now enable V5 onscreen buttons to use touch only in Vangelis.

[hannesmenzel]

@jlearman

I don’t see one

As far as I recall you enable the onscreen buttons by tapping the meter in the top bar. I don’t know right now if you still have to enable it in webconf. Still I would love to have the state of it being consistent through restart, because right now I always tap the meter to enable the onscreen buttons as a first action after every boot.

@jlearman

However, after reset, I had to also change my audio card and screen type back.

This should not happen and typically it also does not.

@jlearman

green heart in upper right corner is now a green circle arrow

An update is available. Others might have answered this already. I would really take a drink of your choice (wine, tea, warm milk), sit down in your most comfortable place and read the oram wiki, followed by this thread for the vangelis changes to get the basic concepts. The more you get used to the UI, the more rewarding it is to read through the manual.

[riban]

@hannesmenzel

love to have the state of it being consistent through restart

It is. If not for you then report a bug with your exact shutdown workflow.

[rv5]

@jofemodo

We think ALL zynthian users should be comfortable with bold presses. They are part of the zynthian’s DNA and nobody should have problems with this.

To be honest
It’s still very hard for me
I don’t think I ever will be comfortable with it
Sorry surely I won’t be alone in this

[hannesmenzel]

@riban

It is. If not for you then report a bug with your exact shutdown workflow.

I’ll do that. I mainly did shutdown via the shutdown menu accessed by admin long press (now “legacy”).

[riban]

I just checked an rebooting from main menu persists the selection of on-screen buttons in vangelis.

Also, V4 users now access the presets view using bold SELECT from the control view. BACK will take you from presets to banks (if there are any banks). The V4 help for control view is not yet there, otherwise you could have just read about it there and not here! We are inching towards fixing all of this.

I am renaming this thread as there is no longer a “zynbleton” dev branch (having been merged into vangelis testing branch) and we are now using this topic as a general vangelis progress discussion.

[hannesmenzel]

@riban

just checked an rebooting from main menu persists the selection of on-screen buttons in vangelis.

I can 100%ly confirm that for me all tested reboot procedures lead to not recall the onsceen button state:

• reboot menu from long press back and from admin menu
• rebooting via webconf from different windows

[riban]

Use webconf to report issue and if possible, add a video of the reboot process.