like sonic pi said

[srini-pro]

Sonic Pi Boot Error Report

System Information

• Sonic Pi version: 3.2.2
• OS: Raspbian GNU/Linux 10 (buster)

GUI Log

/home/pi/.sonic-pi/log/gui.log

[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {dc7b3924-65ab-43f7-9d13-36937ccbd63f}
[GUI] - Discovering port numbers...
[GUI] - Port entry server-listen-to-gui : 51235 : 51235
[GUI] - Port entry gui-send-to-server : 51235 : 51235
[GUI] - Port entry gui-listen-to-server : 51236 : 51236
[GUI] - Port entry server-send-to-gui : 51236 : 51236
[GUI] - Port entry scsynth : 51237 : 51237
[GUI] - Port entry scsynth-send : 51237 : 51237
[GUI] - Port entry osc-midi-out : 51238 : 51238
[GUI] - Port entry osc-midi-in : 51239 : 51239
[GUI] - Port entry server-osc-cues : 4560 : 4560
[GUI] - Port entry erlang-router : 51240 : 51240
[GUI] - Port entry websocket : 51241 : 51241
[GUI] - Detecting port numbers...
[GUI] - GUI listen to server port 51236
[GUI] -    port: 51236 [OK]
[GUI] - Server listen to gui port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Server incoming OSC cues port 4560
[GUI] -    port: 4560 [OK]
[GUI] - Scsynth port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Server send to GUI port 51236
[GUI] -    port: 51236 [OK]
[GUI] - GUI send to server port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Scsynth send port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Erlang router port 51240
[GUI] -    port: 51240 [OK]
[GUI] - OSC MIDI out port 51238
[GUI] -    port: 51238 [OK]
[GUI] - OSC MIDI in port 51239
[GUI] -    port: 51239 [OK]
[GUI] - Websocket port 51241
[GUI] -    port: 51241 [OK]
[GUI] - All ports OK
[GUI] - launching Sonic Pi Runtime Server:
[GUI] - Ruby server pid registered: 10267
[GUI] - hiding main window
[GUI] - initialising toolbar icons
[GUI] - setting up window structure
[GUI] - restoring scope states 
[GUI] - creating status bar
[GUI] - creating info panel
[GUI] - creating shortcuts
[GUI] - creating tool bar
[GUI] - initialising documentation window
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
[GUI] - starting UDP OSC Server on port 51236...
[GUI] - UDP OSC Server ready and listening
..................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - Critical Error. Unable to connect to server..

Server Errors

/home/pi/.sonic-pi/log/server-errors.log

ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to playback-only mode
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
Cannot read socket fd = 6 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open SuperCollider client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
terminate called without an active exception

Server Output

/home/pi/.sonic-pi/log/server-output.log

compton not installed so transparency not available
sudo apt install compton     to remedy this
Sonic Pi server booting...
This is version 3.2.0 running on Ruby 2.5.5.
The time is 2021-03-30 08:59:20 +0530
Using primary protocol: udp
Detecting port numbers...
Listen port: 51235
  - OK
Scsynth port: 51237
  - OK
Scsynth send port: 51237
  - OK
OSC cues port: 4560
  - OK
Erlang port: 51240
  - OK
OSC MIDI out port: 51238
  - OK
OSC MIDI in port: 51239
  - OK
Websocket port: 51241
  - OK
Opening UDP Server to listen to GUI on port: 51235
Starting Server Runtime
Booting server...

Booting Sonic Pi
----------------

Booting on Raspberry Pi
Jackd not running on system. Starting...
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|2048|3|44100|0|2|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 2048 frames (46.4 ms), buffer = 3 periods
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 3 periods for playback
Started [10342] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/10342
Started [10342] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/10342
Boot - Starting the SuperCollider server...
Boot - scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 2 -o 2 -z 128 -c 128 -U /usr/lib/SuperCollider/plugins -b 4096 -B 127.0.0.1
Started [10392] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 2 -o 2 -z 128 -c 128 -U /usr/lib/SuperCollider/plugins -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/10392

Scsynth Output

/home/pi/.sonic-pi/log/scsynth.log

# Starting SuperCollider 2021-03-30 08:59:24
Found 0 LADSPA plugins
could not initialize audio.

Process Log

/home/pi/.sonic-pi/log/processes.log

Clearing pids: ["9994", "9923", "10044"]

Clearing [9994]
  -- command jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100
  -- removing /tmp/sonic-pi-pids/9994
  -- politely killing 9994
  -- politely killing 9994
  -- politely killing 9994
  -- force killing 9994
  -- force killing 9994
  -- force killing 9994
  -- force killing 9994
  -- force killing 9994
  -- unable to kill 9994

Clearing [9923]
  -- command /usr/bin/ruby --enable-frozen-string-literal -E utf-8 /opt/sonic-pi/app/gui/qt/build/../../../../app/server/ruby/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51240 51238 51239 51241
  -- removing /tmp/sonic-pi-pids/9923
  -- politely killing 9923
  -- killed 9923

Clearing [10044]
  -- command scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 2 -o 2 -z 128 -c 128 -U /usr/lib/SuperCollider/plugins -b 4096 -B 127.0.0.1
  -- removing /tmp/sonic-pi-pids/10044
  -- unable to get ProcTable info for: 10044
  -- process: 10044 not running

Finished clearing pids

Started [10267] [-] /usr/bin/ruby --enable-frozen-string-literal -E utf-8 /opt/sonic-pi/app/gui/qt/build/../../../../app/server/ruby/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51240 51238 51239 51241 [-] /tmp/sonic-pi-pids/10267
Started [10342] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/10342
Started [10342] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/10342
Started [10392] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 2 -o 2 -z 128 -c 128 -U /usr/lib/SuperCollider/plugins -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/10392

[ethancrawford]

@srini-pro - would you be willing to try the latest version of Sonic Pi? we are now at 3.3.1.

[srini-pro]

i was outdated all this time?

[ethancrawford]

To be fair, the version after 3.2.2 (which was 3.3.0) was only released in January - so it's not that old 🙂 Worth giving 3.3.1 a go if you are happy to - let us know how you get on 👍

[ethancrawford]

Note that 3.3.1 requires the latest release of Raspberry Pi OS from January this year.

[srini-pro]

defenetly