Critical server error!

[olsonk]

Just got this "Server Boot Error" when loading up Sonic Pi for the first time on Windows 7. I'm on a Mac with Bootcamp and Win7. Here's the log:

Detailed Error Report:

GUI log

[GUI] - shutting down any old audio servers...
[GUI] - using default editor colours
[GUI] - booting live coding server
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - waiting for server to connect...
[GUI] - server failed to start with this error message:
> Server Exception:
Boot - Unable to connect to scsynth
[GUI] - critical error!

Server Errors

Could not load did_you_mean
Failed to start server: Boot - Unable to connect to scsynth
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:206:in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:223:inboot_server_windows'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:119:in boot' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:59:ininitialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:49:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:49:ininitialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:27:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:27:ininitialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/mods/sound.rb:106:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/mods/sound.rb:106:inblock (2 levels) in included'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:109:in new' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:109:in

'

Server Output

Device options:

• MME : Microsoft Sound Mapper - Input (device #0 with 2 ins 0 outs)
• MME : Microphone (Cirrus Logic CS4206 (device play_pads not stopping #1 with 2 ins 0 outs)
• MME : Digital Audio (S/PDIF) (Cirrus (device Thread sync/drift #2 with 2 ins 0 outs)
• MME : Microsoft Sound Mapper - Output (device Note lengths vs BPM #3 with 0 ins 2 outs)
• MME : Headphones (Cirrus Logic CS4206 (device Auto stop after about 4 minutes #4 with 0 ins 2 outs)
• MME : Digital Audio (S/PDIF) (Cirrus (device Removes binaries from source tree. #5 with 0 ins 2 outs)
• MME : Speakers (Cirrus Logic CS4206A (device Use $HOME rather than /home/pi #6 with 0 ins 2 outs)
• Windows DirectSound : Primary Sound Capture Driver (device Add facility to select sound output #7 with 2 ins 0 outs)
• Windows DirectSound : Microphone (Cirrus Logic CS4206A (AB 32)) (device current_tempo not working? #8 with 2 ins 0 outs)
• Windows DirectSound : Digital Audio (S/PDIF) (Cirrus Logic CS4206A (AB 32)) (device Ten possible development requests #9 with 2 ins 0 outs)
• Windows DirectSound : Primary Sound Driver (device Add modified play_pattern_timed command #10 with 0 ins 2 outs)
• Windows DirectSound : Headphones (Cirrus Logic CS4206A (AB 32)) (device Improve chord commands #11 with 0 ins 2 outs)
• Windows DirectSound : Digital Audio (S/PDIF) (Cirrus Logic CS4206A (AB 32)) (device Add tempo command to work with timed notes #12 with 0 ins 2 outs)
• Windows DirectSound : Speakers (Cirrus Logic CS4206A (AB 32)) (device Add global feature for with_synth command #13 with 0 ins 4 outs)

Booting with:
In: MME : Microphone (Cirrus Logic CS4206
Out: MME : Headphones (Cirrus Logic CS4206
Sample rate: 44100.000
Latency (in/out): 0.013 / 0.091 sec
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 64
SuperCollider 3 server ready.
Using protocol: udp
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)
An existing connection was forcibly closed by the remote host. - recvfrom(2)

[samaaron]

Wow, that doesn't look good.

Sonic Pi seems to have issues on certain combinations of OS/hardware - and it seems you're seeing one of these problems.

Unfortunately it's not easy for me to help you as I am unable to reproduce the problem here :-(

If you're interested in helping out - it would be useful to know whether or not you can get vanilla Supercollider working on your machine: http://supercollider.github.io

If you can get Supercollider to boot, then the problem is in Sonic Pi - if you can't, the problem is with Supercollider and your set up - both things would be useful to know!

[olsonk]

I'm at work right now and don't have access to my Bootcamp machine, but I'm
definitely interested in helping out and will try to get Supercollider
working when I get home.

I'll get back to you ASAP on the server error bug.

On Thu, Oct 29, 2015 at 2:46 AM, Sam Aaron notifications@github.com wrote:

Wow, that doesn't look good.

Sonic Pi seems to have issues on certain combinations of OS/hardware - and
it seems you're seeing one of these problems.

Unfortunately it's not easy for me to help you as I am unable to reproduce
the problem here :-(

If you're interested in helping out - it would be useful to know whether
or not you can get vanilla Supercollider working on your machine:
http://supercollider.github.io

If you can get Supercollider to boot, then the problem is in Sonic Pi - if
you can't, the problem is with Supercollider and your set up - both things
would be useful to know!

—
Reply to this email directly or view it on GitHub
#765 (comment).

Kevin Olson
olsonk@gmail.com
c: (408)201-4206

[xavriley]

Just to keep this issue up to date, we've discussed similar startup problems on Windows which are probably due to scsynth (the synthesis backend for Sonic Pi) taking longer than 10 seconds to boot on some machines. (See issue #711 for more discussion)

We've bumped the timeout up to 30 seconds for the next release which should be due out in a couple of weeks, but until then Windows users would need to kill any zombie scsynth processes and restart Sonic Pi, preferably on a machine that isn't competing for CPU with any other programs (i.e. not running Task Manager, video encoding) just whilst it's booting up. After that it should be ok in theory...

[anthonyharrison]

Same error for me (Windows 7). Tried SuperCollider and that worked.

Noticed that if your try and rerun Sonic PI,. you get a different critical error

Is Sonic Pi already running? Can't open UDP port 4558.

This is probably due to the fact that the process that opened the UDP port initially crashed (with server error) hasn't released the port.

HOWEVER, if I kill process scsynth (see issue #711), Sonic PI then starts!

[samaaron]

Hi there,

could you try this latest pre-release of v2.10 to see if resolves your issues:

http://sonic-pi.net/files/tmp/Sonic-Pi-2.10b1.msi

[samaaron]

Closing for now as this conversation appears to have stopped.

Please feel free to re-open if you're still having issues with v3.1.0 on Windows :-)