i am unable to open sonic-pi

[vardhan-cyber]

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] - {e258e49b-55b6-405b-ad07-5a4c78b18c5c}
[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: 1295
[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..
[GUI] - UDP OSC Server no longer listening

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 read socket fd = 6 err = Success
Cannot create new client
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-07-20 19:37:11 +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 [1377] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/1377
Started [1377] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/1377
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 [1437] [-] 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/1437

Scsynth Output

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

# Starting SuperCollider 2021-07-20 19:37:43
Found 0 LADSPA plugins
could not initialize audio.

Process Log

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

No pids store found here: /tmp/sonic-pi-pids
Exiting
Creating pids store: /tmp/sonic-pi-pids
Started [1295] [-] /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/1295
Started [1377] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/1377
Started [1377] [-] jackd -R -p 32 -d alsa -d hw:0 -n 3 -p 2048 -o2 -r 44100 [-] /tmp/sonic-pi-pids/1377
Started [1437] [-] 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/1437

[vardhan-cyber]

i am unable to open sonic-pi

[frizzlgrrb]

same issue using version 3.1.0

Sonic Pi Boot Error Report

System Information

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

GUI Log

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

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] -    port: 4558 [OK]
[GUI] - Server OSC listen port 4557
[GUI] -    port: 4557 [OK]
[GUI] - Server incoming OSC cues port 4559
[GUI] -    port: 4559 [OK]
[GUI] - Scsynth port 4556
[GUI] -    port: 4556 [OK]
[GUI] - Server OSC out port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Scsynth send port 4556
[GUI] - Erlang router port 4560
[GUI] -    port: 4560 [OK]
[GUI] - OSC MIDI out port 4561
[GUI] -    port: 4561 [OK]
[GUI] - OSC MIDI in port 4562
[GUI] -    port: 4562 [OK]
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 3644
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - UDP OSC Server no longer listening

Server Errors

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

Failed to load the fast_osc c-extension, falling back to pure Ruby version
Overriding fast_osc c-extension FastOsc::decode_single_message, falling back to pure Ruby version
ruby: No such file or directory -- /usr/app/server/ruby/bin/task-register.rb (LoadError)
ruby: No such file or directory -- /usr/app/server/ruby/bin/task-register.rb (LoadError)
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
����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client

Server Output

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

Sonic Pi server booting...
Using protocol: udp
Detecting port numbers...
Send port: 4558
Listen port: 4557
  - OK
Scsynth port: 4556
  - OK
Scsynth send port: 4556
  - OK
OSC cues port: 4559
  - OK
Erlang port: 4560
  - OK
OSC MIDI out port: 4561
  - OK
OSC MIDI in port: 4562
  - OK
Booting server...


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

Booting on Raspberry Pi
Jackd already running. Not starting another server...
Boot - Starting the SuperCollider server...
Boot - scsynth -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 2 -o 2 -z 128 -c 128 -U /usr/lib/SuperCollider/plugins:/usr/app/server/native/extra-ugens/ -b 4096 -B 127.0.0.1

Scsynth Output

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

# Starting SuperCollider 2021-07-25 23:35:05
Found 0 LADSPA plugins
*** ERROR: open directory failed '/usr/app/server/native/extra-ugens/': No such file or directory
could not initialize audio.

Process Log

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

[ethancrawford]

Hi there @frizzlgrrb,

Your issue is in fact due to a slightly different problem.
The version of Sonic Pi (v3.1) that is bundled with the Raspberry Pi (and provided in the Raspberry Pi software repository) is a version that was built outside of our control, and is partially broken.
You can get a working version of Sonic Pi running on your Raspberry Pi, but in order to do so, here's what you need to do:

• Uninstall the built-in Sonic Pi v3.1
• Download the latest version from our own website: https://sonic-pi.net
• Double click on the downloaded file to install it (and enter the Pi user's account password when prompted)
• Reboot your Raspberry Pi

This should then mean you have a fully up-to-date and working Sonic Pi 👍

[vardhan-cyber]

thankyou

…

On Mon, Jul 26, 2021 at 10:28 AM ethancrawford ***@***.***> wrote: Hi there @frizzlgrrb <https://github.com/frizzlgrrb>, Your issue is in fact due to a slightly different problem. The version of Sonic Pi (v3.1) that is bundled with the Raspberry Pi (and provided in the Raspberry Pi software repository) is a version that was built outside of our control, and is partially broken. You *can* get a working version of Sonic Pi running on your Raspberry Pi, but in order to do so, here's what you need to do: - Uninstall the built-in Sonic Pi v3.1 - Download the latest version from our own website: https://sonic-pi.net - Double click on the downloaded file to install it (and enter the Pi user's account password when prompted) - Reboot your Raspberry Pi This should then mean you have a fully up-to-date and working Sonic Pi 👍 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2803 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUJCPF5Z7Z7BO3P4AJXG333TZTTQXANCNFSM5AV4P2VA> .

[edmundlaugasson]

Same errors here. Did, what you suggested - apt purge for bundled SonicPi 3.1.0 in Raspberry Pi OS with desktop and recommended software, released May 7th 2021, kernel 5.10, which is Raspbian 10 (buster). Using Raspberry Pi 3 (a02082), the UK version. Then installed SonicPi 3.3.1 Beamer from here. Installation went smoothly, all dependenies were installed. So, all software are the greatest and latest currently available. Below are results of starting SonicPi 3.3.1 in Raspbian 10.

cat /proc/cpuinfo | grep 'Revision' | awk '{print $3}'
a02082

lscpu
Architecture:        armv7l
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
Vendor ID:           ARM
Model:               4
Model name:          Cortex-A53
Stepping:            r0p4
CPU max MHz:         1200,0000
CPU min MHz:         600,0000
BogoMIPS:            38.40
Flags:               half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva id

free -h
              total        used        free      shared  buff/cache   available
Mem:          923Mi       417Mi        70Mi       126Mi       435Mi       326Mi
Swap:          99Mi        99Mi       0,0Ki


cat /etc/os-release 
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Here are log files:
gui.log
processes.log
scsynth.log
server-output.log

[vardhan-cyber]

Ok, thanks.

…

On Sat, Jul 31, 2021, 2:57 PM Edmund Laugasson ***@***.***> wrote: Same errors here. Did, what you suggested - *apt purge* for bundled SonicPi 3.1.0 in Raspberry Pi OS with desktop and recommended software, released May 7th 2021, kernel 5.10 <https://downloads.raspberrypi.org/raspios_full_armhf/images/raspios_full_armhf-2021-05-28/2021-05-07-raspios-buster-armhf-full.zip>, which is Raspbian 10 (buster). Using Raspberry Pi 3 (a02082 <https://raspberry-projects.com/pi/command-line/detect-rpi-hardware-version>), the UK version. Then installed SonicPi 3.3.1 Beamer <https://sonic-pi.net/files/releases/v3.3.1/sonic-pi_3.3.1_1_armhf.deb> from here <https://github.com/sonic-pi-net/sonic-pi/releases>. Installation went smoothly, all dependenies were installed. Below are results of starting SonicPi 3.3.1 in Raspbian 10. cat /proc/cpuinfo | grep 'Revision' | awk '{print $3}' a02082 lscpu Architecture: armv7l Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Vendor ID: ARM Model: 4 Model name: Cortex-A53 Stepping: r0p4 CPU max MHz: 1200,0000 CPU min MHz: 600,0000 BogoMIPS: 38.40 Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva id free -h total used free shared buff/cache available Mem: 923Mi 417Mi 70Mi 126Mi 435Mi 326Mi Swap: 99Mi 99Mi 0,0Ki cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" Here are log files: gui.log <https://github.com/sonic-pi-net/sonic-pi/files/6910944/gui.log> processes.log <https://github.com/sonic-pi-net/sonic-pi/files/6910945/processes.log> scsynth.log <https://github.com/sonic-pi-net/sonic-pi/files/6910946/scsynth.log> server-output.log <https://github.com/sonic-pi-net/sonic-pi/files/6910947/server-output.log> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2803 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUJCPF6OXRXMVI4CE6EMKETT2O6Y5ANCNFSM5AV4P2VA> .

[ethancrawford]

@edmundlaugasson - was there any output in server-errors.log?

[edmundlaugasson]

I have two RP4 devices (Raspbian 10), where I tested. Installed OS in the end of July 2021 as wrote my first post in current thread.

One device:

cat server-errors.log 

Jack main caught signal 15
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = system notification = 1 val1 = 0 val2 = 0

Second device had no error output. I actually already downloaded *.deb file from here and installed manually and it works. But bundled version didn't work.

[ethancrawford]

Ok, so I'm a little confused - is the latest Sonic Pi deb from here working on both Pis? or are you having an issue with one as per the above messages?
(If you're still having problems, it might be handy to split your issue off into a ticket of its own to minimise spamming the original issue here 🙂 )

[edmundlaugasson]

As mentioned intially: bundled version doesn't work. This was removed. Then installed manually *.deb (newest, current version) - this works (both RP4). Where is confusion?