Some things I would like to see.

[BoaThor]

Finally, I managed running PiSound, Sonic-PI, PureData and MODEP on a single pi, single installation. Yet, it was not that easy as it could be.

• First of all, the instruction on the PISOUND papersheet in the box is outdated. It was hard to obtain all the information needed. Thanks god, I found a the chat-support and a blog helping me to reverser engineer through the technology stack. (jackd, jackd2, qjackctl, supercollider, PiSOUND). Make this information, the recommended versions, the scripts, the commands more accessible.
• (PS: I made a case for the PI+PiSound from the Box the PISOUND was delivered in. Could provide photos so you can print the cutting directly to the box. It´s not perfect, but it does what it should.)
• My main problem is, that the profided rasbian based image is not really optimized for the use-case. It´s to heavy, 50% RAM load without any workload on the pi, sonic-pi by itself is not really optimized for the usecase, it eats the rest of the RAM. In 50% of the Cases Sonic-Pi 3.01 freezes the Pi on starting it up because it cannot obtain enough ram.
• (Optional would be adding support for more powerful Pi-like single-board computers like the asus tinkerboard or the Orange Pi) There are much leaner desktop-managers, while I would recommend off-loading the whole gui-workloud away from the pi to the client-side running a x-server (https://play.google.com/store/apps/details?id=x.org.server&hl=de).
• Second I would suggest to put a script on the desktop for switching from Sonic-Pi to MODEP or PureData vis versa by killing processes (jackd, supercollider), starting the corresponding processes, setting up the interface connections via cli-jackd commands. Adding a diagnostic script or simple testscript (like puredata) that checks the prerequisits and settings would also be very welcome.

[gtrainavicius]

Thank you very much for your feedback!

By the way, could you elaborate a bit on:

First of all, the instruction on the PISOUND papersheet in the box is outdated.

Which part in particular did you find outdated? (It's easier to see with a fresh set of eyes :))

(PS: I made a case for the PI+PiSound from the Box the PISOUND was delivered in. Could provide photos so you can print the cutting directly to the box. It´s not perfect, but it does what it should.

That'd be very interesting to see, you can share them by sending an e-mail to use at hello@blokas.io or share with the community at https://community.blokas.io :)

My main problem is, that the profided rasbian based image is not really optimized for the use-case. It´s to heavy, 50% RAM load without any workload on the pi, sonic-pi by itself is not really optimized for the usecase, it eats the rest of the RAM. In 50% of the Cases Sonic-Pi 3.01 freezes the Pi on starting it up because it cannot obtain enough ram.

Technically it's Raspberry's official image, we don't yet have a dedicated OS image for Pisound apart from MODEP, but we're looking into it building one. You can definitely share any ideas you already have on this topic. :)