redfrik / supercolliderstandalonerpi2 Goto Github PK

Running on a Raspberry Pi 3

Running scide in the terminal, the error I get:

scide warning: Failed to load fallback translation file

In the ide I get: Interpreter has quit. [Exit code: 0]

Attempting to rerun headless, the server is able to run, qjack shows connection, but no audio.

Any tips?

Dear redFrik,

I installed supercolliderStandaloneRPI2 on my Raspberry Pi 4B. It works very well.
Today I cloned the system SD card using "SD Card Copier" on the Raspberry Pi 4B.
Then, I booted a Raspberry Pi 3B+ using a cloned SD card.
I can run python, SuperCollider and Jack.
I can execute the following one-line command in a terminal window, which comes in the last line opened by typing "crontab -e" in a terminal window.
cd /home/pi/supercolliderStandaloneRPI2 && ./autostart.sh

However, this line is not executed on Raspberry Pi 3B+ when booting Raspberry Pi 3B+.

Using the same method, I copied the system from a Raspberry Pi 4B to another Raspberry 4B. Again, it worked well, and the command in "crontab -e" works well.

Why does it not automatically work when booting on Raspberry 3B+?
Is there a resolution to resolve the problem?
Thank you very much for your help!

Hey Fredrik!

I just tried following your instructions to build this standalone under the most recent version of raspbian, 2019-07-10-raspbian-buster-lite.zip, and have run across a missing file issue that prevents SC from starting. When I tried to run SC with xvfb-run --auto-servernum ./sclang -a -l ~/supercolliderStandaloneRPI2/sclang.yaml I got the following error:

./sclang: error while loading shared libraries: libQt5OpenGL.so.5: cannot open shared object file: No such file or directory

I am afraid I do not have time at the moment to research this more thoroughly, as I need to roll back to a version of raspbian that I know works with this standalone in order to finish prepping for a workshop I have to run this week, but wanted to let you know about this in the meantime.

I do see some discussion of this particular missing file/library being an issue in Debian Buster generally...if I have some time over the weekend I will poke around and see if I can find a simple fix.