I discovered something very weird.
This can be reproduced very easy with the Saffo Synth with Angry Sweep, but I have seen it also with FluidPianos/Electric Piano.
When I modify Osc0 and next Osc1 and then go back to Osc0, I see that the settings are changed also.
This also occurs with the other Osc’s. And it happens in both VNC viewer as with the touchscreen.
Also, when I repeatedly click the red cursor beam on Osc0, I can also see the settings changing.
Furthermore, the digital values do not correspond to the dials.
I cannot remember having seen this in previuos releases.
It sounds like the vnc gui error. A select is sent on click that activates the current control not the highlighted one.
Have you updated ?
I wouldn’t say this was a memory leak, unless you have some evidence for that. Perhaps a more appropriate title would be of greater benefit to other users.
[modified message]
I gave the item a more appropriate titel, however this phenomenon also pops up while only using the touch screen. I think i wrote that too. Since this is not limited to vnc, I still think there might be a memory leak.
The bug that @wyleu referred to also occurs with touchscreen. Ensure you are updated to latest patch to stable release and post your webconf main page here.
@riban@wyleu
I updated to the latest stable last night and did that also just while writing this post.
There is no difference in behaviour, as far as I can see.
Please note, that I do not really have a Zynscreen for wiring. I use an abelectronics IO PI Plus board to connect the rotary switches. https://www.kiwi-electronics.nl/nl/io-pi-plus-1739
Watched the video, it does seem like an odd one. Sorry for checking the basics, but could you burn a new SSD of stable and see if it persists? I would also be interested to see how it behaves with an hdmi screen and a mouse just to be sure if sensible things do happen.
Obviously you are in unknown territory with this one as there are two chips on the board. I would look hard at the interrupt set up as a starting point. and I don’t think I am revealing too many secrets when I acknowledge there are some edge cases around the parameter encoders. There is an encoder test set up in the zynthian code base but I’ve not used it in a fair while ( a couple of years at least).
You obviously have got the basic functionality ( I assume the press buttons on the encoder behave properly) working, can you see any other irregularities in behaviour?
@ wyleu
I checked and dubble checked the interrupts. I think they are ok.
The encoders just work fine, as do the buttons there on.
Please keep in mind that the phenomenae also occur through VNC.
Just tested with a keyboard and mouse, and the same happens.
For your further information, the folowwing synths are active:
1 FS/Fluidpianos/Plectric Piano
2 FS/Fluidstrings/Cello
3 JV/Raffo Synth/Angrysweep
4 FS/AVL Drumkits Perc/AVL Drumkits Percuss
5 JV/Red Zeppelin 5/Default
I will first burn an new SD and video the keyboard and mouse action.
Ok. It appears to be purely a GUI effect. The sound layers are well down the chain…
It would appear that:
When using VNC and Touchscreen to access the GUI, and only then.
Repeated presses on a highlighted list item, cycles the selected list element, but does not reflect this in the GUI display?
I think that’s what I’m seeing.
It does seem to be a similar effect to the bug we saw before but that was far more obvious, but I don’t think the original bug has been completely eradicated.
The VNC route is generally pretty seamless but the list element seems to fool it.
I can’t duplicate it on my vnc on zynthian-1820.local
A double press on a selected item doesn’t change the parameters.
I’m sure you would hve a specific snapshot you want to use the machine in ( Did I get a ?, frankly the paperwork round her is a couple of eons behind stable…)
But for the fault finding on this I would restrict yourself to just one layer with one good known engine. I use the yamahas grand from the GM fluidsynth preset but it doesn’t really matter.
@wyleu
It also happens while using keyboard and mouse.
I removed all layers and loaded only Fluidpianos Grand piano an now, it looks like we are okay again.
Nevertheles, just for te sake of testing, I will do some more testing with a new SD card.
root@zynthian:~# journalctl -u zynthian
– Logs begin at Thu 2019-02-14 10:11:58 GMT, end at Sat 2021-10-16 11:47:11 BST
Oct 15 22:46:55 zynthian systemd[1]: Started Zynthian User Interface.
Oct 15 22:46:55 zynthian startx[506]: X.Org X Server 1.20.4
Oct 15 22:46:55 zynthian startx[506]: X Protocol Version 11, Revision 0
Oct 15 22:46:55 zynthian startx[506]: Build Operating System: Linux 5.10.17-v8+
Oct 15 22:46:55 zynthian startx[506]: Current Operating System: Linux zynthian 5
Oct 15 22:46:55 zynthian startx[506]: Kernel command line: coherent_pool=1M 8250
Oct 15 22:46:55 zynthian startx[506]: Build Date: 19 April 2021 03:23:36PM
Oct 15 22:46:55 zynthian startx[506]: xorg-server 2:1.20.4-1+rpt3+deb10u3 (https
Oct 15 22:46:55 zynthian startx[506]: Current version of pixman: 0.36.0
Oct 15 22:46:55 zynthian startx[506]: Before reporting problems, check h
Oct 15 22:46:55 zynthian startx[506]: to make sure that you have the lat
Oct 15 22:46:55 zynthian startx[506]: Markers: (–) probed, () from config fil
Oct 15 22:46:55 zynthian startx[506]: (++) from command line, (!!) notic
Oct 15 22:46:55 zynthian startx[506]: (WW) warning, (EE) error, (NI) not
Oct 15 22:46:55 zynthian startx[506]: (==) Log file: “/var/log/Xorg.0.log”, Time
Oct 15 22:46:55 zynthian startx[506]: (==) Using config directory: "/etc/X11/xor
Oct 15 22:46:55 zynthian startx[506]: (==) Using system config directory "/usr/s
Oct 15 22:46:57 zynthian startx[506]: /zynthian/config/img/fb_zynthian_boot.png
Oct 15 22:46:57 zynthian startx[506]: Zooming image by 100%…done
Oct 15 22:46:57 zynthian startx[506]: Merging…didn’t find evidence of prior
Oct 15 22:46:57 zynthian startx[506]: done
Oct 15 22:46:57 zynthian startx[506]: Building XImage…done
lines 1-23
– Logs begin at Thu 2019-02-14 10:11:58 GMT, end at Sat 2021-10-16 11:47:11 BST. –
Oct 15 22:46:55 zynthian systemd[1]: Started Zynthian User Interface.
Oct 15 22:46:55 zynthian startx[506]: X.Org X Server 1.20.4
Oct 15 22:46:55 zynthian startx[506]: X Protocol Version 11, Revision 0
Oct 15 22:46:55 zynthian startx[506]: Build Operating System: Linux 5.10.17-v8+ aarch64 Raspbian
Oct 15 22:46:55 zynthian startx[506]: Current Operating System: Linux zynthian 5.10.60-v7l+ #1449 SMP Wed Aug 25 15:00:44 BST 2021 armv7l
Oct 15 22:46:55 zynthian startx[506]: Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.e
Oct 15 22:46:55 zynthian startx[506]: Build Date: 19 April 2021 03:23:36PM
Oct 15 22:46:55 zynthian startx[506]: xorg-server 2:1.20.4-1+rpt3+deb10u3 (Debian -- Support)
Oct 15 22:46:55 zynthian startx[506]: Current version of pixman: 0.36.0
Oct 15 22:46:55 zynthian startx[506]: Before reporting problems, check http://wiki.x.org
Oct 15 22:46:55 zynthian startx[506]: to make sure that you have the latest version.
Oct 15 22:46:55 zynthian startx[506]: Markers: (–) probed, () from config file, (==) default setting,
Oct 15 22:46:55 zynthian startx[506]: (++) from command line, (!!) notice, (II) informational,
Oct 15 22:46:55 zynthian startx[506]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Oct 15 22:46:55 zynthian startx[506]: (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Oct 15 22:46:55 2021
Oct 15 22:46:55 zynthian startx[506]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Oct 15 22:46:55 zynthian startx[506]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Oct 15 22:46:57 zynthian startx[506]: /zynthian/config/img/fb_zynthian_boot.png is 640x480 PNG image, color type GRAY, 8 bit
Oct 15 22:46:57 zynthian startx[506]: Zooming image by 100%…done
Oct 15 22:46:57 zynthian startx[506]: Merging…didn’t find evidence of prior run.
Oct 15 22:46:57 zynthian startx[506]: done
Oct 15 22:46:57 zynthian startx[506]: Building XImage…done
lines 1-23
– Logs begin at Thu 2019-02-14 10:11:58 GMT, end at Sat 2021-10-16 11:47:11 BST. –
Oct 15 22:46:55 zynthian systemd[1]: Started Zynthian User Interface.
Oct 15 22:46:55 zynthian startx[506]: X.Org X Server 1.20.4
Oct 15 22:46:55 zynthian startx[506]: X Protocol Version 11, Revision 0
Oct 15 22:46:55 zynthian startx[506]: Build Operating System: Linux 5.10.17-v8+ aarch64 Raspbian
Oct 15 22:46:55 zynthian startx[506]: Current Operating System: Linux zynthian 5.10.60-v7l+ #1449 SMP Wed Aug 25 15:00:44 BST 2021 armv7l
Oct 15 22:46:55 zynthian startx[506]: Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fb
Oct 15 22:46:55 zynthian startx[506]: Build Date: 19 April 2021 03:23:36PM
Oct 15 22:46:55 zynthian startx[506]: xorg-server 2:1.20.4-1+rpt3+deb10u3 (Debian -- Support)
Oct 15 22:46:55 zynthian startx[506]: Current version of pixman: 0.36.0
Oct 15 22:46:55 zynthian startx[506]: Before reporting problems, check http://wiki.x.org
Oct 15 22:46:55 zynthian startx[506]: to make sure that you have the latest version.
Oct 15 22:46:55 zynthian startx[506]: Markers: (–) probed, (**) from config file, (==) default setting,
Oct 15 22:46:55 zynthian startx[506]: (++) from command line, (!!) notice, (II) informational,
Oct 15 22:46:55 zynthian startx[506]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Oct 15 22:46:55 zynthian startx[506]: (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Oct 15 22:46:55 2021
Oct 15 22:46:55 zynthian startx[506]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Oct 15 22:46:55 zynthian startx[506]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Oct 15 22:46:57 zynthian startx[506]: /zynthian/config/img/fb_zynthian_boot.png is 640x480 PNG image, color type GRAY, 8 bit
Oct 15 22:46:57 zynthian startx[506]: Zooming image by 100%…done
Oct 15 22:46:57 zynthian startx[506]: Merging…didn’t find evidence of prior run.
Oct 15 22:46:57 zynthian startx[506]: done
Oct 15 22:46:57 zynthian startx[506]: Building XImage…done
I can confirm this behaviour. It is a display issue rather than values actually changing. I saw volume of Fluidsynth change to zero but actual volume remained unchanged. I have recorded this as a bug in the issue tracking system as issue #540.