Hi,
Problems are solved now. Thanks.
Bert
Hi Riban
after update to:
zyncoder: oram-2409.2 (36691b3)
zynthian-ui: oram-2409.4 (dc1a1ca)
zynthian-sys: oram-2409.4 (9cf56bd)
zynthian-data: oram-2409.3 (305b301)
zynthian-webconf: oram-2409.3 (25cda92)
I created a snapshot with 2 instruments chains:
- Fluidsynth with Electric Piano (MIDI Ch.1)
- Setbfree (MIDI Ch.2)
When I load it playing the keyboard I heard a kind of Pipe organ.
022-Easy.zss (8.3 KB)
I opened a ticket
I cannot reproduce this but have updated the ticket with my diagnostics and question to you @piattica.
Hi @riban,
In answer to your earlier post, Iām kind of on 2409.4, but webconf is still frozen on an earlier version. Iāve not been able to set the repositories in webconf as I just get an internal server error when viewing the page - can this be set via cli at all?
Current software versions below -
Update logs show iām still having issues reading a file in webconf/.git/objects/
getting a fatal :unresolved deltas left after unpacking
I suspect due to the issues Iām having I may have a corrupted install, which may have been present before the original updates.
Reflashing wonāt be an issue, but happy to continue troubleshooting on current install if itās of any help to pinning down other problems.
Its taken me a week to run the update because I only have 1GiB ram and it kept crapping out trying to compile setBFree with the zynthian-webconf service running. Please for the love of God, if anyone knows how to build debian packages and host a repo, can you give us a hand?
1 Like
Please reimage. I think the fixes that are in vangelis will resolve many of these git issues so a future update should be less painful.
Ta, will do.
same behaviour also with other another Zynthian and using a distributed SF2
Now and then, the broken Midi-recorder shows up like a ghost.
This is valid for 2409.3 and 2409.4 and vangelis versions of zynthian-ui. 2409.2 works. Hope this is a valid info helping to find out what might have gone wrong.
The symptom: once Midi-capture-files menu is called with ALT-Bold-Play and a Midi track is played, there is no way to come back to other menus, like mixer or preset or others. As soon as a zynkey for another screen is pressed (either hardware button or onscreen touch (still losing their colour scheme after being touched), the keypad LEDs change, but the screen stays and zynthian locks up, midi playback stops after a short time, zynpot keeps on working if twisted to select another file, but as soon as an action is invoked pot-switch-4, these lock up as well and the Zynthian is completely frozen. No errors show up anywhere.
The lock-up can be unblocked by calling and saving UI prefs in webconf that normally would invoke a restart of zyntian-ui. After an unusual legthy time of waiting, the zynthian-ui reappears, and the cycle could be repeated. Iāve tried to define a restart-ui key (Alt-Long) in wiring, but no zynkey reacty any more, as soon as the first lock-up stage is reched, and also no more if zynpot is locked-up as well. Zynpot-switch redefinition has no effect in Midi-recorder.
The 2409.3 update introduced the Vangelis bug in the MIDI-recorder into Oram. Then The 2409.4 update did not resolve it.
So reimaged to zynthianos-last-stable.img.xz 2024-10-02 22:05, updated once to get the recent repository names, changed to Custom, all Vangelis except zynthian-ui left at HEAD detached 2409.4 it now works. This image Iām keeping as a backup.
Iāve also tried to update all the way from the clean image to Oram stable 2409.4, but then the error showed up again at 2409.3 and stayed in 2409.4.
The all Vangelis but zynthian-ui Oram 2409.4 works perfectly for now with the Vangelis features and the Midi-recorder works and the sound card levels menu works as well, as ever before.
The new Vangels zynthian-ui has the broken Midi-recorder. The sound card levels menu is over-complicating things with the forced categorisations of settings, leaving no way to categorise and order by hand, even trucating inputs or other settigns if one settinging is not understood, even though selected in the sub screen.
A suggestion, what about leaving the built-in audio level settigns sortable by webconf audio settings, as before, and polpulate the rest of the menu in categorised manner as hotplug devices appear, maybe even with the sorting inherited from the configured sorting for the builtin soundcardās settings.
Another idea: What about some sort of a freeze-switch to temporarily deactivate updates and get rid of the luring update-icon on the screen?
@jofemodo @riban @wyleu and all the many other devs a big Thank You for their excellent work.
1 Like
Please report your issues in the GitHub issue tracker.
Just tried this forced update, it did the thing but the restart logo is still there.
I have been avoiding reimaging for some time cause I registered Pianoteq on it and the device activation page on there sounds pretty hardass about redos.
After the update and a reboot I ran update in the webconf, this was the output, if it means anythingā¦
Checking 'zynthian-ui' for stable tag-releases ...
last release-tag: oram-2409.4
current branch: oram-2409.4
Checking 'zynthian-sys' for stable tag-releases ...
last release-tag: oram-2409.4
current branch: oram-2409.4
Checking 'zynthian-webconf' for stable tag-releases ...
last release-tag: oram-2409.3
current branch: oram-2409.3
Checking 'zynthian-data' for stable tag-releases ...
last release-tag: oram-2409.3
current branch: oram-2409.3
Checking 'zyncoder' for stable tag-releases ...
last release-tag: oram-2409.2
current branch: oram-2409.2
Updating System configuration...
SOUNDCARD_MIXER is OK
BOOT LOG DISABLED
OVERCLOCKING => Maximum
RBPI AUDIO ENABLED
OTG ENABLED
SOUNDCARD CONFIG => dtoverlay=hifiberry-dacplusadcpro\nforce_eeprom_read=0
DISPLAY CONFIG => display_lcd_rotate=2
CUSTOM CONFIG => dtoverlay=i2c-rtc,rv3028\n
Configuring X11 inverted display ...
Executing update recipes...
Current patch level: 20241222.1
END OF PATCHES
NO NEW PATCHES TO APPLY.
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 168 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
Updating zynthian-data...
Updated 0 paths from the index
Repository 'zynthian-data' frozen in tag release 'oram-2409.3'!
Updating System configuration...
SOUNDCARD_MIXER is OK
BOOT LOG DISABLED
OVERCLOCKING => Maximum
RBPI AUDIO ENABLED
OTG ENABLED
SOUNDCARD CONFIG => dtoverlay=hifiberry-dacplusadcpro\nforce_eeprom_read=0
DISPLAY CONFIG => display_lcd_rotate=2
CUSTOM CONFIG => dtoverlay=i2c-rtc,rv3028\n
Configuring X11 inverted display ...
Updating zyncoder...
Updated 0 paths from the index
Repository 'zyncoder' frozen in tag release 'oram-2409.2'!
/zynthian/zyncoder /zynthian/zyncoder
/zynthian/zyncoder/build /zynthian/zyncoder /zynthian/zyncoder
++ Defined MCP23017_ENCODERS
++ TPA6130 kernel driver LOADED. Omitting user space driver.
++ Building for Wiring Layout V5
-- Configuring done
-- Generating done
-- Build files have been written to: /zynthian/zyncoder/build
[ 68%] Built target zyncore
[ 89%] Built target tpa6130_set_volume
[100%] Built target zyncoder_test
/zynthian/zyncoder /zynthian/zyncoder
/zynthian/zyncoder
Updating zynthian-ui...
Updated 0 paths from the index
Repository 'zynthian-ui' frozen in tag release 'oram-2409.4'!
/zynthian/zynthian-ui/zynlibs/zynsmf /zynthian/zynthian-ui
/zynthian/zynthian-ui/zynlibs/zynsmf/build /zynthian/zynthian-ui/zynlibs/zynsmf /zynthian/zynthian-ui
-- Configuring done
-- Generating done
-- Build files have been written to: /zynthian/zynthian-ui/zynlibs/zynsmf/build
[100%] Built target zynsmf
/zynthian/zynthian-ui/zynlibs/zynsmf /zynthian/zynthian-ui
/zynthian/zynthian-ui
/zynthian/zynthian-ui/zynlibs/zynaudioplayer /zynthian/zynthian-ui
/zynthian/zynthian-ui/zynlibs/zynaudioplayer/build /zynthian/zynthian-ui/zynlibs/zynaudioplayer /zynthian/zynthian-ui
OSC disabled
-- Configuring done
-- Generating done
-- Build files have been written to: /zynthian/zynthian-ui/zynlibs/zynaudioplayer/build
[100%] Built target zynaudioplayer
/zynthian/zynthian-ui/zynlibs/zynaudioplayer /zynthian/zynthian-ui
/zynthian/zynthian-ui
/zynthian/zynthian-ui/zynlibs/zynmixer /zynthian/zynthian-ui
/zynthian/zynthian-ui/zynlibs/zynmixer/build /zynthian/zynthian-ui/zynlibs/zynmixer /zynthian/zynthian-ui
-- Configuring done
-- Generating done
-- Build files have been written to: /zynthian/zynthian-ui/zynlibs/zynmixer/build
[100%] Built target zynmixer
/zynthian/zynthian-ui/zynlibs/zynmixer /zynthian/zynthian-ui
/zynthian/zynthian-ui
/zynthian/zynthian-ui/zynlibs/zynseq /zynthian/zynthian-ui
/zynthian/zynthian-ui/zynlibs/zynseq/build /zynthian/zynthian-ui/zynlibs/zynseq /zynthian/zynthian-ui
-- Configuring done
-- Generating done
-- Build files have been written to: /zynthian/zynthian-ui/zynlibs/zynseq/build
[100%] Built target zynseq
/zynthian/zynthian-ui/zynlibs/zynseq /zynthian/zynthian-ui
/zynthian/zynthian-ui
Updating zynthian-webconf...
Updated 0 paths from the index
Repository 'zynthian-webconf' frozen in tag release 'oram-2409.3'!
Regenerating engines DB: engines ...
INFO:root:Command took 32s
Running Flag Actions from '/zynthian/zynthian-sys/scripts/update_zynthian.sh'...
Saving state...
Restarting zynthian service...
Restarting zynthian-webconf service...
Hi @jtode!
What do you mean by ārestart logoā?
Pianoteq licence is bound to the hardware so reinstalling the OS will not change the licence assignment. You will be able to reactivate Pianoteq on the device. Iāve done this many times.
1 Like
No just executed the update script again to stay on the stable release. The zynthian successfully boots up. Thank you.
Awesome, that being the case I suspect I have no issue at all. :>
Edit: but I meant the circular arrow thingy that indicates update available. I have updated many times in the last few hours. I got myself into a silly commitment a couple days ago that requires the zynthian to honor it. Media possibly incoming in the next day or two.
Hi All,
Am I the only one where a long press on the touch buttons on screen do not result in any action?
(after re-installing and updating from the beginning (starting with 2024-10-02 image))
error:
Jan 01 11:06:51 zynthian startx[1042]: ERROR:zynthian_gui.cuia_thread_task: CUIA āunknownā failed with params: [ā5ā, āPā]
Jan 01 11:06:51 zynthian startx[1042]: Traceback (most recent call last):
Jan 01 11:06:51 zynthian startx[1042]: File ā/zynthian/zynthian-ui/zyngui/zynthian_gui.pyā, line 2360, in cuia_thread_task
Jan 01 11:06:51 zynthian startx[1042]: zpi = zynthian_gui_config.zynpot2switch.index(i)
Jan 01 11:06:51 zynthian startx[1042]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jan 01 11:06:51 zynthian startx[1042]: ValueError: 5 is not in list
Andā¦
Have a FANTASTIC 2025!!!
The aeolus issues have been solved in vangelis and oram (staging) branches. It seems only aeolus was really affected. Any other issues should be due to other causes.
Regards
2 Likes
@maartmaart what ātouch buttons on screenā do you refer to?
Hi @riban,
Best wishes to you and your beloved ones!
I mean the ā@wanthalfā UI. The software buttons (Touch navigation) on the screen that replace the Zynthian hardware keypad.
They work OK except the long press functionality.
Cheers,
Maarten
Lately it stopped working for me as well (being on current vangelis). Does it only concern the touch keypad?
1 Like
AFAIK, yes. I didnāt try to reproduce, but hardware V5 buttons work for me.