as you probably know, the release name is a tribute to Dafne Oram (the venerable lady in the picture above), who was an electronic music pioneer when very little people conceived such a concept.
It’s been a long and hard road, but the result is amazing! Enjoy it!
The amount of changes, improvements and fixes from the old stable is too big to enumerate all.
If you are upgrading from the old stable, be aware that Oram includes some breaking changes. It’s highly recommended you take a look to the Oram user’s guide:
It’s not totally finished yet, but it documents the most important features and changes in Oram.
Below it’s an incomplete list with the most relevant changes in Oram:
Based in bookworm aarch64: fully 64bits OS!!!
Raspberry Pi5 support, what implies adapting important hardware interfaces, like GPIO, for instance.
Chain Manager: A complete refactorization of zynthian’s UI code, that separates core and UI code, re-implementing chain management and removing some limitations we had in older stable. Most important changes in Oram comes from this refact.
X-Y controller touch-pad: It’s now accessible on touch and V5 (controller options menu)
Improved Mixer’s MIDI learning
Step Sequencer / Pattern Editor
Smooth zoom and scroll in pattern grid
Swing, humanization and playing-chance
Step offset
Quantized / Raw MIDI capture
Undo/Redo (modification history)
Step Sequencer / ZynPad
Playing position feedback in pads
ZynSampler integration: PoC work in progress (trigger sample with pads)
Internet Radio => Audio Generator / Others
Improved management of external storage for captures, soundfonts and presets. Still not perfect.
I must say that almost all the hard development work was made by our great @riban. I simply offered encouragement and (dubious) advice, fixed silly bugs and implemented some amenities.
What an impressive feat of a work you have daringly completed, to reach this much anticipated stable release point.
Switch to 64 bits and official Raspi 5 support in one stroke, besides a long list of OS improvements and workflow rationalisations!
It was nice yesterday to launch the latest update and see the grinning face of Dafne Oram at reboot: a pivotal moment in the challenging development of this remarkable project.
@C0d3man there wasn’t really a testing branch or, if there was, no one should be using it. There is the Oram branch which has formed the development branch for several months (similar to old “testing”) which became the staging branch and is currently (but will soon change) the stable branch. So, if you were using a recent oram image then updating should be fine but of course, it is good to use a known starting state so use of the stable image is recommended.
We have plans to rationalise how stable, development, testing, staging, etc. are managed. You should hear about it soon.
Hi @jofemodo ,
I just wanted to md5sum zynthianos-last-stable.img.xz with the md5 file.
But it only contains information of one of the developing images.
Regards
Issue: no patchage on system after a fresh installation and updating to latest.
Clicking on Patchage in the VNC window does not open patchage.
Terminal CLI does not expand to patchage after typing “patcha”.
Seems as if patchage recipe was not executed…?
It’s great how many functions have been added in the last few months. It’s nice to see the Zynthian getting better and better. Thanks for pushing it forward!
After a freshly installed image and after updating around 2 days ago, midi system messages are not sent as received from external device.
Create a simple midi (through) chain, with receiving the external midi system messages and sending them to i.e. midiTTY (also tried with USB connected midi device), the START/STOP/CLOCK sequence sent to midiTTY was the following:
SYS START
SYS START <—
SYS STOP <—
SYS CLOCK
SYS CLOCK
SYS CLOCK
SYS CLOCK
just to be sure…