Vangelis and snapshots saved in ORAM

Software
1

Vangelis on V4 customized with RPi5 and after latest updates:

Loading snapshots prepared in Oram I have strange behaviours.

For example: my default snapshot (2 chains: Pianoteq + VirtualJV) generate this:
May 20 18:00:38 zynthian startx[1045]: Started zynmixer_bus
May 20 18:00:38 zynthian startx[1045]: Started libzynseq
May 20 18:00:38 zynthian startx[1045]: Started libzynsmf
May 20 18:00:39 zynthian startx[1045]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 1, delay: 38569.0us
May 20 18:00:39 zynthian startx[1045]: WARNING:zynthian_gui_brightness_config.init_ctrls: Can’t set display brightness!
May 20 18:00:46 zynthian startx[1045]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 2, delay: 23.0us
May 20 18:00:46 zynthian startx[1045]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 3, delay: 35.0us
May 20 18:00:46 zynthian startx[1045]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 4, delay: 25.0us
May 20 18:00:46 zynthian startx[1045]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 5, delay: 31.0us
May 20 18:00:48 zynthian startx[1045]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 6, delay: 23214.0us

sounds correct but after some minutes Zynthian gets stuck: impossible to operate with encoders or buttons and if I try rebooting by Webconf sometimes there is an Error on screen

other snapshots stuck Zynthianor sound different because load different presets

this example
002-American Boy 260513.zss (19.5 KB)
generates following warnings
May 20 18:19:46 zynthian startx[4139]: WARNING:zynthian_legacy_snapshot.version_3: ‘scenes’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynseq.refresh_state: Invalid zynseq - rebuilding default
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 5, delay: 46932.0us
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘REV1_WIDTH’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘DYN1_COMPRESS’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘DYN1_LIMITER’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘KEY1_LOW’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘KEY1_HIGH’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘REV1_WIDTH’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘DYN1_COMPRESS’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘DYN1_LIMITER’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘KEY1_LOW’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_processor.set_state: Invalid controller for processor 1#padthv1: ‘KEY1_HIGH’
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_engine_jalv.proc_parse_ctrl_value: Unknown controller symbol when parsing jalv output => DYN1_COMPRESS (86)
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_engine_jalv.proc_parse_ctrl_value: Unknown controller symbol when parsing jalv output => DYN1_LIMITER (87)
May 20 18:19:50 zynthian startx[4139]: WARNING:zynthian_engine_jalv.proc_parse_ctrl_value: Unknown controller symbol when parsing jalv output => REV1_WIDTH (85)

I read that Oram snapshots are compatible with Zynthian (is it true?)
I suspect also that all these warnings can be caused by other issues (see topic Vangelis: impossible get Webconf [solved] - #36 by riban)

2

Hi @piattica !

I can’t see nothing wrong in your logs. They are normal. Having “unknown controller symbols” warning is very frequent for most engines and it don’t cause any issue normally, so i wouldn’t be worried about this. My logs look very similar to yours.

The zynthian getting stuck is most probably due to a very different cause. You should try to “catch the logs” when it gets stuck.

BTW, what is your Pi5 temperature? How did you manage to keep fresh the Pi5 inside the V4 case?

Regards

1 Like
3

RPi5 has the active cooler with this configuration:
dtparam=fan_temp0=50000
dtparam=fan_temp0_hyst=5000
dtparam=fan_temp0_speed=150
dtparam=fan_temp1=60000
dtparam=fan_temp1_hyst=5000
dtparam=fan_temp1_speed=200
dtparam=fan_temp2=65000
dtparam=fan_temp2_hyst=5000
dtparam=fan_temp2_speed=225
dtparam=fan_temp3=70000
dtparam=fan_temp3_hyst=5000
dtparam=fan_temp3_speed=250

Not yet summer here but usually fan stays almost silent.

I’ll try to do it

4

And the temperature is fine?
Could you send some pictures of the modified V4? I’m curious…

Regards

5

Hi
I am loading all the snapshots prepared with Oram, for a concert: a snapshot for each song. It is a kind of personal reharsals. I would like to do the concert with Zynthian only but I see it is not stable with Vangelis.
In this way I examinated one by one and noted the issues.

Now Zynthian is stucked after loading
052-Il mio Canto Libero 250919.zss (7.7 KB)
and UI log is:
May 21 14:54:33 zynthian startx[6451]: WARNING:zynseq.update_state: No launcher info for sequence (7,32)
May 21 14:54:33 zynthian startx[6451]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 17, delay: 28879.0us
May 21 14:54:34 zynthian startx[6451]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 18, delay: 7.0us
May 21 14:54:34 zynthian startx[6451]: WARNING:zynthian_autoconnect.cb_jack_xrun: Jack Audio XRUN! =>count: 19, delay: 29333.0us

image
image871×572 70.1 KB

after rebooting and reloading this snapshot you can play without Zynthian issue so the issue is not connected with snapshot

sometimes after some snapshots loading if you shutdown, Zynthian goes in shotdown screen with error 114(1) and reboots

P.S. I did the same yesterday before latest 2 updates and was much much worse

1 Like