@mzero Great write up! This is definitely something that we could include in our documentation.
What’s making it difficult to have a generic image for use with Pisound is the vast amount of options for the way you may want to make use of Pisound, and a lot of them are in conflict with one another.
It makes total sense to have MODEP as an image, as it has a single purpose to run the MOD software, and we don’t recommend using it for something else. What I do myself, is keep a few sd cards with specific images, and swap as needed. Adding Pure Data into MODEP would not be trivial, because MODEP uses JACK as the audio backend, so Pure Data has to be configured appropriately, and also having a GUI would make sense, for patch editing, so the image would grow significantly.
That’s easy to fix, the scripts for installing PD and SC are here, should we add --no-install-recomends to both and gem package to PD?
We are aware of this issue and the file will be renamed after the next update is released.
Clicking the button once searches for the first main.pd file it can find, looking in USB storage first, then in /usr/local/puredata-patches on the SD card.
As there is no real possible interaction to understand what’s going on and which patch you’re on, it makes sense to launch the first one found. So to switch between patches, you should be able to swap one USB stick with another one, containing a different patch. (double click the button to stop the patch and safely unmount the storage)
You may customize the button to launch patches based on the number of clicks (similar to MODEP loading a specific pedalboard layout), as @oootini did here: Adding more button clicks