YOU CAN’T UPDATE YOUR BOOKWORM BASED IMAGE TO GET THE BETA!!!
Old bookworm-based Vangelis images are not longer supported.
Please, don’t complain about any issue if you are not running the Vangelis BETA SD image, based in Trixie.
Apart from the Trixie migration, not too many changes from the first testing release. Mostly bugfixes and workflow refinement. Just to enumerate a few:
Improve boot splash and first boot experience. No more inverted text and things like that, at less on official kits.
MINI_V2 kits are now autodetected and configured in the first boot. So the list of officially supported hardware kits is:
V3
V4 (Pi4)
V5 (Pi4)
V5.1 (Pi5)
MINI_V2 (Pi4 & Pi5)
Improved UI icons. We have more than 100 now!!!
Improved Main Menu
Launcher’s pattern ccpy/paste is fixed and now work nicely
Launcher’s ccpy/paste now supports audio clips too.
Phrase automation now works nicely with audio clips.
PFL output now has a global volume controller that has been mapped to the APC40 “cue level” knob.
And a bunch of bugfixes and little improvements !!!
Please, download and test it as much as you can because we want Vangelis to be the best zynthian release.
What a milestone is finally reached!
Kudos on this .
A few questions about the first official image:
Are the Beta image features synced with the system updates of Vangelis Testing, which many of us have used and perused during the last year or so?
For particularly customised and regularly updated Vangelis installations, will it be possible, at a given point, to keep on using them simply switching the release branch to Vangelis Stable in webconf?
Have you considered, as a development team, to put in place a configuration template migration system, in order to allow the save and restore process of a given OS style preset (colour scheme, fonts, CUIA key-bindings, wiring configuration and installed packages)? That would make the circulation and testing of newly released OS changes much easier and attractive, for users of Zynthian installations engaged in active projects.
Thanks to you, @riban and the others, for all the fantastic work done!
As far as I could test, the official V2 is working as well.
Considering the issues I run into whenever I try to update, I’ve been thinking about leaving it frozen in Oram. Still, I’m pleased with the testing so far - I guess I just need to stick to the “expander” use case and master the basic four buttons/encoders operation.
Congrats, this is a great achievement and a fantastic milestone!
And (EDIT: after successfully downloading and installing the new BETA Vangelis) the update icon appeared as I was writing previous message. I dared and it succeded, despite an error (?) message close to the process end: /zynthian/zynthian-sys/sbin/regenerate_engines_db.sh: line 21: 2402 Killed ./zynthian_lv2.py $arg1
This BETA is the first Trixie based image we release and i would like to note a few facts about this:
If you want to use Vangelis, YOU MUST DOWNLOAD AND INSTALL the BETA SD image.
We don’t support the older Vangelis bookworm-based images anymore. Please, don’t complain if things stop working in your bookworm-based Vangelis image. Sooner or later these images will be broken by some update. If you really want to keep using an older bookworm-based Vangelis image, don’t update anymore.
We don’t provide any route to upgrade from Bookworm-based images to Trixie-based ones. Of course, it’s possible, but please, don’t expect any support and don’t be surprised if you have to invest a huge amount of time to get things working in a stable way. We don’t recommend trying to upgrade from Bookworm to Trixie.
We do a big effort to test new images in as many devices as we can. In my case, i’ve tested with 4 different zynthians, and @riban tested in 3 or 4 more.
But we can’t test with hardware we don’t have, sorry. Users with custom builds must do a little effort and fix the issues by themselves. Then send PR or explain, in detail, the steps they followed to fix the issues.
Hi, looks good so far on original V5 kit here. Thank you for the huge step forward! Obviously, on mixer page, the right peak meter of a channel strip is somewhat narrower compared to the left one. Is this intended?
Yes, understood. I booted from the newly provided image burned on the sd with Raspberry Pi Imager, not through trying to update. I’ve attached the firstboot.log file. Any other files that might be helpful?