We don’t advertise changes during development. It would be too onerous. Anyone following dev can look at commit comments which we try to make useful. At stable release and at point releases we will try to provide release notes but they are likely to be incomplete due to the quantity of incremental changes we make. We will try but no promises.
3 Likes
The demo version of Pianoteq bundled with zynthian-2409 (Oram) has been updated to V8.
Unfortunately it will not be possible to run Pianoteq V6 on zynthian-2409 (Oram). This is because Modartt only produced a 32-bit ARM version of V6 and Oram is 64-bit only. Modartt have actually removed the ARM version of V6 from their download page which means you can no longer obtain it and must rely on previously downloaded copy. Modartt offer an upgrade option for €29 which is the only option you have if you want to use your existing V6 licensed Pianoteq on Oram. The alternative is to leave your zynthian running zynthian-2401 which is the last stable 32-bit version of zynthian.
It pains us to make this decision but there is no alternative. Sorry!
3 Likes
Well, indeed it can’t be considered a “decision”. Simply there is no arm64 binaries available for PT6. I checked against my collection of downloaded PT packages (i have my particular version of the Internet Archive) at home) and i can confirm that arm64 support begins with PT7 series.
Cheers,
2 Likes
Hi @jofemodo, and thanks for all the advancements with Oram!
I just wanted to gather if I can avoid installing this new release, and rather update my current September 2024 installation (please, see the attached system screenshot for release point specification).
I would prefer to eschew to whole OS reconfiguration process on nvme.
[Edit: I am obviously talking about my custom Pi5, not the official Pi4 V5, whose system I will serenely reset from scratch]
Let me know! Thanx 
I don’t see a big problem. Everything should work as expected. Anyway, it could be some differences because the base system is not the same Raspberry Pi OS image, so please before reporting any issue, test against the latest zynthian 2409.
Thanks!
1 Like
I’m terribly sorry if this is a repeat question. I just flashed and tried the latest dev version (bookworm) on my rpi and i saw somewhere that the password for the UI had changed (and so after adopting the new password, i could login to the UI without issues).
But while i have the rPI connected to a monitor, it keeps “looping” into this screen that screams “ERROR” in red letters constantly.
So i tried to change the password via the UI from “raspberry” into the new password (for this dev-version) but it won’t allow that change.
I’m using the rPI 4 (4GB) model.
I don’t know if I understood your problem correctly. But try logging into webconf toll, for oram is password opensynth and correct your hardware settings.
https://wiki.zynthian.org/index.php/Web_Configuration_User_Guide
Thx for replying 
I did that. I have no issues logging on to the webui using “opensynth”. But as i have the unit connected to a monitor, i see it loop constantly with the “error” message (even after rebooting).
I made sure to update my HW settings to my DAC also (ref: Latest Zynthian with IQAudio DAC+ causes boot-loop) by setting the hw:0 to hw:IQaudIODAC
I don’t know what the issue is exactly but i will retract to a stable version instead (which is good by all means)
Your sound is not well configured. You should fix this because Oram is close the release and we can’t test against all soundcards and configs in the list. Users with custom configs must persevere to get their config to work in Oran and then give feedback so we can update and fix the faulty configurations.
Going back to stable is not sustainable and you loose all the advantages of Oram. Please, try to find the way with Oram.
Regards
1 Like
@jofemodo Can you, please, fix the limit of zynswitches in zyncoder as I mentioned in the other thread? It’s the cause of my “puzzle” trouble. Thanks.
jofemodo, of course. And i understand.
I just flashed and configured “back” successfully, but naturallly i will try Oram out again and help out the best i can 
So, in the end: I decided to pull the trigger, Zynthian embarked in a MASSIVE update routine, and finally all went well (phew!), even after a series of test reboots.
Thus all is good, except…
again, the Raspi 5 has fallen back to normal clock mode (no overclocking active), and obviously it doesn’t handle that computational hog of Pianoteq 8.3.1 at full sample rate and polyphony, as it easily should at raised CPU frequency.
[I am very wary of changing the overclocking from webconf, since it is after that step that the previous time my Oram on nvme crashed beyond repair…] EDIT: As a matter of fact, and rethinking the subject, I am not completely sure whether this webconf settings affects also Rpi5 or concerns Rpi4 only.
Should I try to raise the clock in webconf? Any ideas as to how/why the underlying Raspberry OS update forces a reset of Rpi5 to standard CPU speed?..
Thank you!
Flashing the dev-build again and the only way i could get the boot-loop to cease was to change the sample rate (-r) from 48000 (on Oram) to 44100 (as it used to be). Until i did that, it flashed “Error” constantly.
The web-ui takes me to the regular place, but i notice that on the console, i first get a prompt (where i now login with root/opensynth) successfully but it stays on the prompt) and after a while, the (rpi-connected) display once more boot-loops into the “Error” screen.
Why have you selected V5_ADAC as audio interface? You are using iqaudio dacplus, right?
I am. And i’m sorry about that. I switched the interface to the proper one and naturally it started to work. My fault. All good
2 Likes
Excellent! You may also be able to return to 48000. (It probably already has.) We recommend 48000 because some modules only work at that rate so it avoids you missing out on some zynthian fun! It is possible that some soundcards don’t support 48000 but most do. We advise not going higher as it provides minimal benefit but adds overhead.
Hi All,
I cannot select anything anymore in the MAIN window after installing the latest oram (2024-09-12) image… E.g not able to load an snapshot…
I get this error message:
Sep 14 09:14:22 zynthian startx[1111]: ~~~~~~~~~~~~~~~~~~~~^^^
Sep 14 09:14:22 zynthian startx[1111]: IndexError: list index out of range
Sep 14 09:14:22 zynthian startx[1111]: ERROR:zynthian_gui.zynswitch_read: Traceback (most recent call last):
Sep 14 09:14:22 zynthian startx[1111]: File “/zynthian/zynthian-ui/zyngui/zynthian_gui.py”, line 2016, in zynswitch_read
Sep 14 09:14:22 zynthian startx[1111]: self.zynswitches()
Sep 14 09:14:22 zynthian startx[1111]: File “/zynthian/zynthian-ui/zyngui/zynthian_gui.py”, line 1854, in zynswitches
Sep 14 09:14:22 zynthian startx[1111]: if i < 4 and self.zynpot_pr_state[i] > 1:
Sep 14 09:14:22 zynthian startx[1111]: ~~~~~~~~~~~~~~~~~~~~^^^
Regards,
Maarten
Hi @maartmaart and @jofemodo,
Same thing here. After updating yesterday my custom Pi5 to latest 202409 Oram, the whole range of alternatives for the selection function became ineffective.
I cannot select/activate anything in Main, either with touchscreen, USB keyboard, USB mouse, Key-binding to keyboard and keys/pots of my programmable keypad.
Furthermore, my current last state snapshot failed, and I had to remove all of its processors through webconf, in order to start the system. I tried to save another snapshot as last state in webconf, to no avail.
Thanks 
It looks like your devices doesn’t have any physical knob, right? OK, I think i’ve fixed the issue. Please, update and test.
Regards
Thank you @jofemodo, for the kind and prompt feedback.
My custom setup with touchscreen has no physical controls on board, but I do use a convenient programmable keypad with four potentiometers, that mimic the behaviour of the Zynpots through key-binding.
I will update and test, as soon as I get back to home later this afternoon. I hope to be able to fix the selection issue, and also to load another functional snapshot, getting rid of the current last-state.
I will get back to you and the forum with the outcome