Hi there, is zynbleton in vangelis now?
Tried finding out myself, but did not succeed 
Regards
No, not yet.
1 Like
PLEASE TAKE NOTE
Within the next few days we will be merging our bleeding-edge development into vangelis (testing) branch. This will make vangelis a development branch that should not be used for production. (Not that you should have been anyway!)
Please move to oram to continue to experience a (relatively) stable workflow. Vangelis may be broken at any point (hopefully for not too long!) and should only be used to test the latest bleeding-edge developments. We strongly recommend using a dedicated device (or boot media) for vangelis, separate to your normal, day-to-day zynthian usage (which should use oram).
There are many changes in this development version and full forward / backward compatibility is not guaranteed. Indeed, you are unlikely to be able to move between oram and vangelis without a degree of hurt.
Please heed this warning! Move from vangelis to oram and / or do not update vangelis unless you want to feel the same hurt that we developers experience.
8 Likes
Thanks for the clear notification!!
Cheers,
Maarten
Going back from Vangelis to Oram Staging breaks the Internet Radio (and probably other things as well, I suspectā¦).
So we are anyway forced to set up a fresh Oram, with all that setup-hassle and preset and data transferring involved, is that correct? NO LIKE 
Could you please enable a fully functional rollback to Oram, please 
PS: The chaos is there already whith trying to make a new Oram Staging microSD.
TAL-U-NO-LX-V2 is not useable any more, because it is not possible to reinstall the presets:
/zynthian/zynthian-sys/sbin/regenerate_lv2_presets.sh https://tal-software.com/TAL-U-NO-LX-V2
locks up and vomits errors once killedā¦
It did work in Vangelis. Many of us were forced to use Vangelis, because of many fixes that have been Vangelis exclusive and now we shall not use it any more?
We will merge the latest Vangelis fixes into Oram before we change Vangelis. This should go into Oram staging and then we will do a point-release.
I may do the merge soon. I had been waiting for @jofemodo to do it (so that I want blames for another Christmas nightmare release! I am still traumatised from last year.)
3 Likes
I have merged vangelis into oram (staging). @fussl please test to see if you can now move back to oram. Anyone on staging please check this update still works as expected. You are our beta testers 
.
1 Like
never felt any different! 
Unfortunately, the above problems persist. I have no more online Vangelis installations to test on, as the last one is now fried.
The last Island Zynthian still works and will never see updates, nor will it ever be connected to a network, to prevent update problems and Iāll keep that for making music.
I think the other two will be decommissioned and taken apartā¦ lost the love for themā¦
HI @zynthianers!
I hope all of you are enjoying the winter these days. 
Iām away from home, sharing christmas with family and friends in Pamplona, so little time for zynthian these days.
Regarding this thread, I would like to say that recently i moved from Oram to Vangelis and back with no issues. I always use a good connection and preferably update from command line because itās easier to detect and fix issues while updating.
Anyway, although Vangelis (our current testing branch) has been quite stable in the last times, we always warned against using it for production, specially moving between Vangelis and Oram and back, what is a ādangerousā operation. Itās always better to use several SD cards, one for Oram, one for Vangelis, or make a copy before updates, etc.
Finally, please, remember we have been warning about the upcoming breaking changes in Vangelis. In a few days/weeks, things are going to move a little bit in Vangelis and those of you wanting a working device should move to Oram stage ASAP, not missing to backup your snapshots, etc. because moving back from testing to stable is, and probably always will be, a ādangerousā operation.
All the best!
5 Likes
Hi @fussl !
This is not a very common feature in any system. I mean, when you update from a version to the next one, itās rarely supported to rollback to the previous version. You can upgrade from Debian 12 to 13, but downgrading from 13 to 12 is not supported. I donāt know if you can upgrade from Windows 10 to 11, but iām almost sure you canāt rollback from 11 to 10. Of course, iām sure we can find some examples, but itās not commonly offered, and this is because itās not easy at all.
Zynthian is one of the rare systems that offers this possibility, but we warn about it because we canāt be sure this is going to work always. It would be really time consuming to test every update in both directions and ensure you always can undo all changes when going back between versions!! Perhaps we should remove this possibility and avoid the headaches, but we normally prefer to keep all options and let the user to take the decision. Perhaps we should add some extra warn when moving from Vangelis to Oram 
Regards,
3 Likes
It has happened today!
We have merged the zynbleton development branch into Vangelis branch. This is likely to break your workflows.
Please ensure you have switched to Oram before doing any further updates. Oram staging is updated with the most recent changes in Vangelis so you should have the same experience. We will shortly release a new stable Oram version (image) with the latest fixes and enhancements.
After today, Vangelis will be very different and may be broken at any time. There will not be a simple way to move between the two branches without breaking snapshots. If you want to use Vangelis then please use a separate SD card.
You have been warned.
13 Likes
Okay - now that you have been warned and have all dutifully moved to Oram, I cordially invite the more entrepid users to consider helping with testing the new developments.
As we always recommend, it is advisable to use a separate boot media for stable (oram) and testing (vangelis) so that you can use your zynthian for production whilst playing with the new developements.
Vangelis aims to support backwards compatibility, i.e. your oram snapshots should work on vangelis but the opposite is not true. Vangelis snapshots will not load on oram.
Further, vangelis may be broken, suffer regression or change significantly at any time and without warning. It may behave different tomorrow than it does today. We are aiming to refine the current feature set so do not plan to make such large breaking changes, but it is within our gift to do so at our whim.
Here is a list of some of the changesin vangelis for the brave to try:
- Sequence launcher integrated into mixer view - farewell zynpad, my old friend.
- When launchers are visible, still have access to mute & solo and can still see fader level, pan/balance and meters (reduced in height).
- Arranger disabled - not accessible but dormant, awaiting a revivial at a later date.
- Audio clip launcher (I call him āclippyā) providing synchronised, warpable audio samples to be played in sync with sequences.
- Bypass fore every effect - allows for true stomp-box workflow.
- Audio mixer controls are now a processor allowing consistent access to all parameters and MIDI binding using standard MIDI learn process.
- Visual chain management - weird tree view is gone and graphical block-based layout is here with abilty to add, remove and move processors and chains (including dragging with touch - cool man!)
- Pinned chains - as well as the main mixbus, any other chain may be pinned to the right of the mixer view. Pinned chains are always visible and do not scroll. Other chains will scroll underneath them.
- Additional mixbuses (send / return loops) - as well as the main mixbus, any number of extra mixbuses may be added. These act like effects returns and each additional mixbus gets a āsendā control in each chain. So you can build effects chains and send signals to them with different levels.
- Changed (more ugly???) launcher colour scheme that better matches RGB LED colours in Novation and Akai hardware controllers.
- Better touch interface, e.g. block/icon driven new-chain chooser - this is very much a work-in-progress and may not make it into the next release.
- Display of tempo, time signature and current beat in top bar.
- Ability to automate playing next / previous phrase after specified quantity of bars - we call rows of launchers a phrase.
- Ability to set the beats per bar and tempo for each phrase - with the ability to switch between 7 and 13 beats per bar, now you can perform you favourite prog rock songs!
- Access to chain parameters directly from the chain manager view puts all the chain configuration in one place - change MIDI channel, audio or MIDI input and output routing, key range and transpose, etc. You know this makes more senseā¦
- Akai APC40 integration - but other devices are probably broken - we need help from their authors.
There are many other changes under the hood and quite possibly some user facing features I have forgotten about. This is quite a change in UI and may require some documentation changes which we tend to avoid too early because updating the wiki too early is awkward and things are still changingā¦ but we can add some tips here.
12 Likes
I have updated a MicroSD to the latest Vangelis and have successfully booted with it on both my homebuild and V5.1. I got my Tascam USx08, waveshare 7ā and Romoral keypads working. My Akai APC Key25 MK2 did not work, it seems there is no driver.
It looks very nice. and the above list are fill of very fine points!
Here are a couple of questions:
I have looked for clippy but did not find. How/Where? (just a pointer in the right direction)
Hmm - there is a second hand APC 40 MK1 available locally - is it both MK1 and MK2 that is integrated?
This is a joy-ride! Thanks a lot!
1 Like
Can your share pointers to the changes device drivers need to make? I can look into the akai APC key25 family.
1 Like
To add a clip launcher simply add a āClipā chain. This is a first class citizen so gets its own āAdd engineā menu option.
I have only integrated the APC40 MK2. I am not sure what would be needed for the MK1.
2 Likes
We are considering how we might write some guidance on driver migration / writing. I will try to put together some pointers in the next few days. Some things are simpler so some of the workarounds done in old driver code needs to be removed.
Is there somewhere where it is possible to control which chains that go to record?
The āAudio Recorder ā Record chainā is no longer an option in the audio out section of a chain (also not on main)