sonic-pi hanging on startup

[ukscone]

Pi2 (original version), edimax wifi adapter and justboom DAC hat.
fresh install of raspbian (september image) plus a sudo apt-get update ; sudo apt-get upgrade to get to current latest version.

get an error on exit of sonic-pi
http://pastebin.com/QNR9UwTP

which seems to cause sonic-pi to hang at the splash image on later attempts to run.

debug.log is empty
pi@raspberrypi:~/.sonic-pi/log $ cat gui.log [GUI] - using default editor colours [GUI] - shutting down any old audio servers... [GUI] - starting UDP OSC Server on port 4558... [GUI] - unable to listen to UDP OSC messages on port 4558 [GUI] - booting live coding server [GUI] - waiting for server to boot... ........... [GUI] - server successfully booted. [GUI] - waiting for server to connect...

pi@raspberrypi:~/.sonic-pi/log $ cat server-errors.log jackd: no process found scsynth: no process found Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to playback-only mode Exception! Connection refused - send(2) ["/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/gui/qt/../../../app/server/bin/sonic-pi-server.rb:340:in block in

'"]
Exception!
Connection refused - send(2)
["/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/gui/qt/../../../app/server/bin/sonic-pi-server.rb:340:in block in <main>'"] Exception! Connection refused - send(2) ["/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/gui/qt/../../../app/server/bin/sonic-pi-server.rb:340:in block in '"]
Exception!
Connection refused - send(2)
["/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/gui/qt/../../../app/server/bin/sonic-pi-server.rb:340:in block in <main>'"] Exception! Connection refused - send(2) ["/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/server/sonicpi/lib/sonicpi/osc/udp_client.rb:33:in send'", "/opt/sonic-pi/app/gui/qt/../../../app/server/bin/sonic-pi-server.rb:340:in block in '"]
Jack main caught signal 15
/opt/sonic-pi/app/gui/qt/../../../app/server/bin/sonic-pi-server.rb:403:in join': Interrupt from /opt/sonic-pi/app/gui/qt/../../../app/server/bin/sonic-pi-server.rb:403:in '
JackEngine::XRun: client = SuperCollider was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 10 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = system notification = 1 val1 = 0 val2 = 0
pi@raspberrypi:~/.sonic-pi/log $`

pi@raspberrypi:~/.sonic-pi/log $ cat server-out*.log Sonic Pi server booting... Using protocol: udp jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. 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|2|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 This is Sonic Pi v2.10 running on raspberry with ruby api 2.1.0. Sonic Pi Server successfully booted. Released audio card Audio0 audio_reservation_finish Server is exiting. Shutting down GUI... Goodbye :-) pi@raspberrypi:~/.sonic-pi/log $

`pi@raspberrypi:~/.sonic-pi/log $ cat scs*

Starting SuperCollider 2016-11-15 15:45:00

Found 0 LADSPA plugins
JackDriver: client name is 'SuperCollider'
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 2048
SuperCollider 3 server ready.
JackDriver: max output latency 139.3 ms
pi@raspberrypi:~/.sonic-pi/log $`

[rbnpi]

just a thought. Have you added dtoverlay=i2s-mmap to your config.txt file in the boot folder? I think this may be needed for the DAC to work with Sonic Pi.
Is the DAC selected as the default card in Audio Device Settings or are you working with the built in card which is normally in slot 0?
IF you remove the DAC does Sonic Pi work OK then?

[ukscone]

1. not unless it's set as default in config.txt on a fresh install of raspbian and it's not mentioned in the justboom docs and the DAC is working ok elsewhere.
2. will have to check that, i believe so as I did try some other s/w before trying sonic pi but will double check.
3. eek it was hard enough to get it into the case, i really don't fancy taking it out. would just not "configuring" in config.txt be good enough for testing?

will removing the ~/.sonic-pi directory be good enough for causing sonic-pi to think that it is being run for the 1st time?

will report back after checking all the above in a while

[rbnpi]

The DAC will work OK with other software. Sonic Pi requires to connect to it via jackd and for this to work it needs realtime a memory mapped card. That is what this addition will enable. This was a problem with other doc cards such as the IQaudio card until this facility was added. Try adding the line to your config.txt You will need to do so from the command line using
sudo nano /boot/config.txt to access the card, as it requires root access. Alternatively you can edit it with the card plugged into a Mac or Windows Box where the boot partition will be visible. Yes if you remove the .sonic_pi folder it will start again from scratch and be recreated. Note you will lose any contents from the buffers.

On 16 Nov 2016, at 15:23, Russell Davis notifications@github.com wrote:

not unless it's set as default in config.txt on a fresh install of raspbian and it's not mentioned in the justboom docs and the DAC is working ok elsewhere.
will have to check that, i believe so as I did try some other s/w before trying sonic pi but will double check.
eek it was hard enough to get it into the case, i really don't fancy taking it out. would just not "configuring" in config.txt be good enough for testing?
will removing the ~/.sonic-pi directory be good enough for causing sonic-pi to think that it is being run for the 1st time?

will report back after checking all the above in a while

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #1472 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AFVDiedVs85ArPX4Irh7mF-JEO1_yq5Zks5q-x_xgaJpZM4KyroE.

[ukscone]

doing some more fiddling. no dtoverlay=i2s-mmap is not set in config.txt however it now seems to be all down to the illegal instruction on exit that is causing the problem. i suspect that error is causing a non-clean shutdown so that connections to the jackd server etc. are refused on next launch

[ukscone]

just read your comment above after i wrote my reply. have to go out out for a bit will try adding that line then and see what happens

[ukscone]

ok added the line to config.txt, rebooted, made sure the justboom DAC is selected as the device and same thing. illegal instruction on 1st run exit and then hang on restart

[rbnpi]

How are you running SP? Do you have the icon in Programming folder on Startup menu? Are you clicking on this, or trying to boot SP from a command line?

[ukscone]

both.

i first noticed it by running from the menu item and confirmed something was happening by running from the command line

[rbnpi]

try a fresh install by downloading to your desktop from
http://sonic-pi.net/files/releases/v2.10.0/

Sonic-Pi-for-RPi-Jessie-v2.10.0.tgz

extract the Sonic-Pi folder there and try running from sonic-pi-v2.10.0/bin/sonic-pi

[ukscone]

well that is the same version that's already in the raspbian jessie image/repos but did that and exactly the same. same illegal instruction error and same effects e.g. runs once then hangs at splash image on subsequent runs unless ~/.sonic-pi deleted

[rbnpi]

Are you able to select the built in audio using the audio devices preference panel or does the RAC disable it? If so does that work? Must select before booting SP. BTW the previous install was to eliminate any problems with your present version.

[ukscone]

i understand why to d/l the tarball, if i'd thought it through carefully i'd have done that earlier. yes can select the dac, hdmi or analogue from the panel app. it no longer seems to be the audio out device that is the problem (should have mentioned in passing earlier that output device makes no difference) it definitely seems to be the dirty exit due to illegal instruction error. only thing I haven't tried yet is run SP, exit, get the error message, reboot and run SP again which I will try now

[ukscone]

something interesting happened. my apt update script fired (due to it being wednesday and 3:30pm) and raspberrypi-ui* debs got updated and I didn't get the error message on exit and it seems to be starting up consistently. -- i'll do some testing but 6 runs and it seems to be running ok.

[shawaj]

Did you get this working ok in the end? If not, I think @francesco-vannini has it working

[francesco-vannini]

Yes, a part from the two lines needed for Raspbian to work correctly dtparam=audio=off dtoverlay=justboom-dac (or justboom-digi) You also need the following dtoverlay=i2s-mmap #To run jack server used by Sonic Pi

…

On 11 January 2017 at 20:34, Aaron Shaw ***@***.***> wrote: Did you get this working ok in the end? If not, I think @francesco-vannini <https://github.com/francesco-vannini> has it working — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1472 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APUu18jbjSBG37yn1armxE_OqAxbnPfyks5rRTzQgaJpZM4KyroE> .

-- Francesco Vannini <https://twitter.com/GarageTechTweet> <https://www.youtube.com/user/Happylotube> <https://uk.linkedin.com/in/garagetechlinkedin> <https://www.facebook.com/GarageTechBook/> <https://plus.google.com/+FrancescoVannini> <http://garagetech.tips/?feed=rss2>