AppImage running on Raspberry Pi
I've been trying out the APPImage on a Pi5 running on a freshly installed Raspberry Pi OS and have noticed one or two problems with it. First off, it runs OK but the standard distro does not have pipewire-alsa installed and so you can't change the output, which goes to the default HDMI speaker, as alternatives eg bluetooth speaker are not listed, and if you install qpwgraph it doesn't see either an input or output connection from supersonic. Installing pipewire-alsa solves this, and it allows the built in output selection by right-clicking the OS volume control icon on the pi to work, and the volume control works. `This is easier that using the SP prefs as some of the names shown there can be confusing. It also means that you can make connections from Qsynth into SP using qpwgraph. However the other problem is that you only get two inputs and two outputs showing unless you also install pulse-audio regardless of the toml file settings, in which case you get a rather ungainly alsa plugin showing more than two inputs or outputs together with a large number of auxiliary i/o ports. I was able to utilise channels 3,4 input and different output ports from SP utilising these.
Initially I got several failures when starting the AppImage having made changes to the selected input or output, these seemed to be caused by the stored connections in the gui.ini file giving selection problems. The solution if this occured was to delete the audio in and out values in the file (just leaving an = with nothing following it). I have swithched to a later AppImage from the cl build of later commits, and I think this is solved now.
ON my owAppImage build (which didn't have bundled ruby so I had to run it with local ruby installed I still occasionally was getting input to the current buffer as if a key was held down. I had this with both a 1 and a 4 at different times. I was using vnc to control the Pi and it may have been a quirk of this connection.
Incidentally if you are doing your own appimage build what bundled ruby do you use (from where), and where do you place it before running the script?
Source: sonic-pi-net/sonic-pi