Downloading it!
Have I to be carefull with some engines in particular?
Is there some engines you want to be tried first?
MOD UI is OK to try? you talked about some freeze, just have to restart UI?
Just tell me if you want returns for a particular engine!
Today I spent a few hours trying to run it on a pi zero w. I’m using a pHAT DAC and a generic hdma monitor. Wiring set to dummies. I keep getting the Zynthian “Error” screen. Wifi broadcasts zynthianos and I have to enter the password two times before I can connect my iPhone to the network. Zynthian.local will not connect and times out. Prior to trying the Zero, I put the same sd card in a Rpi3 using the same configuration settings and same pHAT DAC and monitor. It boots and displays the Zynthian gui with no “Error” screen.The rpi3 broadcasts zynthianos and I can connect to the Zynthian configuration tool. I haven’t tested out all functions on the rpi3, but most of the things I’ve tried worked. As you mentioned sound fonts are missing and Mod Ui needs work. I tried to load the Pure Data Engine but it gets stuck in an endless loop and freezes the system. I will continue with further tests in the next few days to see if I can get Zynthian working on the Zero W.
Also - I’d suggest having the last two weeks available for download. It means if the last few builds fail there is still a usable nightly image.
BTW - I have started adding in CustomPiOS the option to export files from the build. This means I can export a realtimekernel.tar.gz . So we could have an image that can switch between the realtime kernel and a normal kernel.
Just copy the files to a public web folder, the Jenkins workspace is not best toto sharw from.
Example: http://unofficialpi.org/Distros/ZynthianOS/nightly/ (don’t use this, but you can take the apache theme).
Then add a Jenkins job that removes files older than two weeks.
OK! I already added a cron tab for deleting images older than 1 week. Server disk is only 100GB and image size will grow up when i add some sound fonts.
Don’t do this unless your are ok with perhaps bricking that zynthian build!
cd /
sudo wget http://unofficialpi.org/Distros/RealtimePi/nightly/2018-06-12_realtimepi-kernel-4.14.34.tar.gz
sudo tar xzf 2018-06-12_realtimepi-kernel-4.14.34.tar.gz
(Kernel works for both Rpi2, Rpi3 and zero)
Technically if you back up the kernel files and have them in a tar.gz, you could extract the kernel you need.
Another way is to give this kernel a different name and then in config.txt change to kernel=foo.bar. And it might need to handle different Pis.
We need it both kernels as different files and two bash scripts that are copying either one to the real location/name. I can build the switch in webconf.
sudo tar xzf 2018-06-12_realtimepi-kernel-4.14.34.tar.gz --directory=/
You can also extract the gz and only tar xf for speed
And the original kernel can be obtained by:
cd /tmp
wget http://unofficialpi.org/Distros/RealtimePi/nightly/2018-06-12_realtimepi-kernel-4.14.34.tar.gz
echo "" > /tmp/kernel_list
for i in $(tar zvft 2018-06-12_realtimepi-kernel-4.14.34.tar.gz | awk '{ print $6 }'); do if [ -f /"$i" ]; then echo /"$i" >> /tmp/kernel_list; fi; done
tar czf current_kernel.tar.gz --files-from=/tmp/kernel_list
I installed ZynthianOS today, but I’m having trouble accessing Zynthian via SSH. Even connected to the zynthian network (wifi-hotspot) I can not access the zynthian.
Another question, how can I enable and disable the hotspot?