Due to a poor solder joint my zynth back button went beserk (now fixed) and with its random selections managed to start the audio recorder without me knowing. (+1 for wyleu’s previous request for indication of recording in status bar,) The /root partition filled which gave an error on next login. Luckily I could still log in, diagnose and fix the issue but similar conditions on other gnu/linux boxes have rendered the device fairly useless. I have noted advice from jofemodo and others to avoid recording to the internal sdcard (root partition) and I concur this should be avoided. Not only because of the risk of filling the disk but also to reduce wear on the flash media which has limited life. (I have had several uSD cards fail on me with fairly limited use.) What do you think of the idea to inhibit recording to internal storage and only record to USB connected storage? There may be use cases where recording to root partition is desirable and so maybe it could be a configurable option.
It should be the new “title auto-scrolling” feature. It’s also commited to master, so if you update your “Gorgona” based zynthians, it should be the same.
I note that zynthainOS github does not have issue tracking enabled. May I request that we include some audio device firmware in the image, e.g. midisport-firmware?
2019-05-10 nightly: After some preliminary configuration and reboots I have several issues:
The hostname changes to “root” so web-conf access changes to root.local.
zynthian-ui will not start
I changed the hostname back but still no joy. Was this build particularly broken?
Doh! I must have set hostname in the web-ui. That explains village fool 1.
I have configured for HDMI output and got it working so something wrong with my sainsmart18 config or maybe issue with stretch - TBC.
Doh! I misconfigured sainsmart18. That explains village fool 2.
I now have Aruk running - hoorah! (That was too painful!) I will report (actual) issues in github.
It would be advantageous to add sainsmart18 to the display configuration but I appreciate that this probably requires an overlay which I am finding challenging to source / create.
I find it a little bit disturbing, that jenkins shows the date of the start, but the image itself has the end date in the filename.
I don’t know, if everybody knows that. So you have to take the image + 1 day of the latest green build.
Done!
BTW, i fixed by hand the filenames from the 4 latest images and tomorrow’s image (and following) should have the correct timestamp, same than Jenkins build.
