Trouble Starting Sonic Pi 2.11.1 on Windows 10

[mbbackus]

I have installed Sonic Pi on 32 Windows 10 machines in my lab using the .msi installer via

msiexec.exe -i Sonic-Pi-for-Win-v2.11.1.msi /passive

. Only a couple of them actually start the program when I click on it. The rest just hang. I had the same problem with v2.11.0 (botht the .msi and portable versions). Here are the contents of my log files for the machines that hang:

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Server OSC listen port 4557
[GUI] - Server OSC out port 4558
[GUI] - Server incoming OSC cues port 4559
[GUI] - Scsynth port 4556
[GUI] - Scsynth send port 4556
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - unable to listen to UDP OSC messages on port 4558
[GUI] - Ruby server pid registered: 4704
[GUI] - waiting for Sonic Pi Server to boot...
...
[GUI] - Sonic Pi Server successfully booted.
[GUI] - waiting for Sonic Pi Server to respond...
............................................................
[GUI] - Critical error! Could not connect to Sonic Pi Server.

and

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
Booting server...


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

Booting on Windows
Boot - Starting the SuperCollider server...
Boot - SuperCollider booted successfully.
Boot - Connecting to the SuperCollider server...
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Receiving ack from scsynth
Boot - Server connection established
This is Sonic Pi v2.11.1 running on windows with ruby api 2.3.0.
Sonic Pi Server successfully booted.

What baffles me is that it works for some, but not all. I did the exact same thing on every machines. Students use these machines so there are differences in their profiles, but all system wide stuff should be identical. Any ideas? Any help you can provide would be greatly appreciated.

[samaaron]

So sorry you're still having issues. We will do everything we can to get things working for you. Boot stability on Windows is a very high priority for us.

Just to make sure, are these the only log files in ~/.sonic-pi/log that you can see with a hung process? You should be able to see these files:

gui.log
processes.log
scsynth.log
server-errors.log
server-output.log

Can you confirm that these other log files aren't present?

[samaaron]

One line of the log that stands out is this:

unable to listen to UDP OSC messages on port 4558

This suggests that port 4558 is unavailable on your machine. Do you possibly have anything running on that port already? This might help: http://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-port-on-windows

[mbbackus]

I took a screen shot of the ports my computer is listening to. It has sonic-pi listed for 4558.

As for the log files, I only see 3:
gui
server-errors (empty)
server-output

Here's the output from those files this time around:
gui

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Server OSC listen port 4557
[GUI] - Server OSC out port 4558
[GUI] - Server incoming OSC cues port 4559
[GUI] - Scsynth port 4556
[GUI] - Scsynth send port 4556
[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: 796
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.

server-output

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
Booting server...


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

Booting on Windows
Boot - Starting the SuperCollider server...
Boot - SuperCollider booted successfully.
Boot - Connecting to the SuperCollider server...
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Receiving ack from scsynth
Boot - Server connection established
This is Sonic Pi v2.11.1 running on windows with ruby api 2.3.0.
Sonic Pi Server successfully booted.

Thanks for helping me with this. It looks like a pretty cool way to hook kids interested in music.

[samaaron]

Could you restart the machine and try again?

[Brackmann]

Any solution? I am having the same issue
It shows the splash screen and nothing else :(

[mbbackus]

Sadly no. I simply cannot get this software to work consistently enough in my lab to use it with my students. The weird part is the machines are virtually identical. I have no idea what is causing some to work and others to hang. I had our network guys come in and look at what was happening on the network using Wireshark, and they couldn't see any reason why some were hanging either.

Can you share some details about your setup? Are you guys behind a proxy or firewall? What kinds of computers are you running? What OS?

[Brackmann]

How sad :-(
I have to present the software in teacher's continuing education sessions and I am almost already giving up.
I tried on two computers, both with Windows 10: Dell Inspiron 14 5000 and a gamer computer with a Sound Blaster X-Fi Titanium HD sound card.

[samaaron]

Very strange to see you're having issues. Prior to v2.11.1 it was very common to see boot issues for Windows users but since then they have pretty much all been resolved.

Sonic Pi is a very complicated piece of software under the hood with many moving pieces. This is compounded with Windows as it has such a heterogeneous hardware install base.

Please could you post the contents of the logs for he machines that fail? That way I can see what might be going by wrong with them.

[samaaron]

@Brackmann it could very well be that your problem is not the same as the one @mbbackus is facing. The are many reasons it won't boot :-)

It's currently Easter break for me and I'm also on paternity leave (having just had my third child) so I may not be able to get things working for you in time for your continuing education sessions. However, I really would like to help you get things working if you're able to help out :-)

[samaaron]

@mbbackus I'd love to help you fix your issue - but it's going to be hard as I can't reproduce it locally and I've seen pretty much all the similar issues dry up with the user base.

It really looks to me that port 4558 on your machine is blocked or otherwise unavailable. Your logs should look like this:

[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]

In your previous log printout it doesn't say port: 4558 [OK] which suggests that Sonic Pi isn't able to bind to it. Do you have any other services running on that port?

[Brackmann]

Hi Sam! Thanks for your support!
Congrats for your third child! You are brave!! :-)

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] - port: 4558 [Not Available]
[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 0
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - unable to listen to UDP OSC messages on port 4558
[GUI] - Ruby server pid registered: 14788
[GUI] - waiting for Sonic Pi Server to boot...

The port 4558 is not in use and is allowed by the system:

[Brackmann]

One more thing, inside "server-errors.log":

internal:gem_prelude:4:in require': cannot load such file -- rubygems.rb (LoadError) from <internal:gem_prelude>:4:in internal:gem_prelude'

[francescosoave]

Is there any news about this issue?

[Brackmann]

I fully disabled my antivirus and firewall to fix the issue ;-)

[francescosoave]

cool, thanks..with Zonealarm I have to literally shutdown the whole thing. Excluding SonicPi from firewall only doesn't work..however it works although it's more of a workaround than a proper solution..

[samaaron]

Hi there @Brackmann and @francescosoave,

it's really frustrating that you have to disable your firewall and antivirus to get Sonic Pi to work. That's definitely not an acceptable solution :-(

Could you try with v3.1 and see if that has eased the problems at all?

[Brackmann]

I am sorry to inform that the new version of Sonic Pi is detected as (many) false positive. :(
Thanks for trying.

[samaaron]

Hmm, that’s unfortunate.

Please could you report this to your virus protection software vendor. Hopefully this is something they can look into :)

[Brackmann]

Good news! I tested today using the complete install (non-portable) and it worked fine. It appears to be a problem with "PortableApps" application. Thanks for your support and the great software you develop ;-)

[samaaron]

Great that the standard msi works :-)

I'd still definitely submit an issue request about the Portable version - I'm pretty sure that's something that the software vendor should be able to resolve at their end

[francescosoave]

Hi, sorry to re open this but..msi not working on my Windows10. I'm getting the following error. Interestingly it says "Windows 7".
I tried to run as admin but got the same result.
I also tried to completely disable my antivirus and firewall but still throwing the error

Sonic Pi Boot Error Report
==================


System Information
----------------

* Sonic Pi version: 3.1.0
* OS: Windows 7


GUI Log
-------

**`C:\Users\Fran\.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: 2792
[GUI] - waiting for Sonic Pi Server to boot...
..........
[GUI] - Sonic Pi Server successfully booted.
[GUI] - waiting for Sonic Pi Server to respond...
............................................................
[GUI] - Critical error! Could not connect to Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - UDP OSC Server no longer listening




Server Errors
-------------

**`C:\Users\Fran\.sonic-pi\log\server-errors.log`**




Server Output
-------------

**`C:\Users\Fran\.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
Started [8548] [-] "C:\Program Files (x86)\Sonic Pi\app\server\native\scsynth.exe" -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U "C:/Program Files (x86)/Sonic Pi/app/server/native/plugins/" -b 4096 -B 127.0.0.1 [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/8548
Started [1900] [-] "C:/Program Files (x86)/Sonic Pi/app/server/native/erlang/bin/erl.exe" -noshell -pz "C:/Program Files (x86)/Sonic Pi/app/server/erlang" -s pi_server start 4560 [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/1900
Started [8364] [-] 'C:/Program Files (x86)/Sonic Pi/app/server/native/osmid/o2m' -L -b -i 4561 -O 4562 -m 6 [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/8364
Started [704] [-] 'C:/Program Files (x86)/Sonic Pi/app/server/native/osmid/m2o' -b -o 4562 -m 6 'Sonic Pi' [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/704
Booting server...


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

Booting on Windows
Boot - Starting the SuperCollider server...
Boot - C:/Program Files (x86)/Sonic Pi/app/server/native/scsynth.exe -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U C:/Program Files (x86)/Sonic Pi/app/server/native/plugins/ -b 4096 -B 127.0.0.1
Boot - SuperCollider booted successfully.
Boot - Connecting to the SuperCollider server...
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Receiving ack from scsynth
Boot - Server connection established
Studio - Initialised SuperCollider Audio Server v3.9.0
Studio - Resetting server
Studio - Studio - clearing scsynth
Studio - Studio - allocating audio bus
Studio - Studio - Create Base Synth Groups
Studio - Starting mixer
Studio - Starting scope
"C:/Program Files (x86)/Sonic Pi/app/server/native/erlang/bin/erl.exe" -noshell -pz "C:/Program Files (x86)/Sonic Pi/app/server/erlang" -s pi_server start 4560
Studio - Spawning o2m with:
    'C:/Program Files (x86)/Sonic Pi/app/server/native/osmid/o2m' -L -b -i 4561 -O 4562 -m 6
Studio - Spawning m2o with:
    'C:/Program Files (x86)/Sonic Pi/app/server/native/osmid/m2o' -b -o 4562 -m 6 'Sonic Pi'
Studio - Initialised MIDI subsystems
This is Sonic Pi v3.1 running on windows with ruby api 2.3.0.
Sonic Pi Server successfully booted.




Scsynth Output
--------------

**`C:\Users\Fran\.sonic-pi\log\scsynth.log`**

# Starting SuperCollider 2018-03-30 23:57:51

Device options:
  - MME : Microsoft Sound Mapper - Input   (device #0 with 2 ins 0 outs)
  - MME : Microfono (Realtek High Definit   (device #1 with 2 ins 0 outs)
  - MME : Microsoft Sound Mapper - Output   (device #2 with 0 ins 2 outs)
  - MME : Altoparlanti (EDIFIER R1280DB S   (device #3 with 0 ins 2 outs)
  - MME : Altoparlanti (Realtek High Defi   (device #4 with 0 ins 2 outs)
  - MME : Realtek Digital Output (Realtek   (device #5 with 0 ins 2 outs)
  - Windows DirectSound : Primary Sound Capture Driver   (device #6 with 2 ins 0 outs)
  - Windows DirectSound : Microfono (Realtek High Definition Audio)   (device #7 with 2 ins 0 outs)
  - Windows DirectSound : Primary Sound Driver   (device #8 with 0 ins 2 outs)
  - Windows DirectSound : Altoparlanti (EDIFIER R1280DB Stereo)   (device #9 with 0 ins 2 outs)
  - Windows DirectSound : Altoparlanti (Realtek High Definition Audio)   (device #10 with 0 ins 2 outs)
  - Windows DirectSound : Realtek Digital Output (Realtek High Definition Audio)   (device #11 with 0 ins 2 outs)
  - ASIO : ASIO4ALL v2   (device #12 with 2 ins 2 outs)
  - ASIO : FL Studio ASIO   (device #13 with 2 ins 2 outs)
  - Windows WASAPI : Altoparlanti (EDIFIER R1280DB Stereo)   (device #14 with 0 ins 2 outs)
  - Windows WASAPI : Altoparlanti (Realtek High Definition Audio)   (device #15 with 0 ins 2 outs)
  - Windows WASAPI : Realtek Digital Output (Realtek High Definition Audio)   (device #16 with 0 ins 2 outs)
  - Windows WASAPI : Microfono (Realtek High Definition Audio)   (device #17 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers (Realtek HD Audio output)   (device #18 with 0 ins 2 outs)
  - Windows WDM-KS : Missaggio stereo (Realtek HD Audio Stereo input)   (device #19 with 2 ins 0 outs)
  - Windows WDM-KS : Microfono (Realtek HD Audio Mic input)   (device #20 with 2 ins 0 outs)
  - Windows WDM-KS : SPDIF Out (Realtek HDA SPDIF Out)   (device #21 with 0 ins 2 outs)
  - Windows WDM-KS : Altoparlanti ()   (device #22 with 0 ins 2 outs)

Booting with:
  In: MME : Microfono (Realtek High Definit
  Out: MME : Altoparlanti (EDIFIER R1280DB S
  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.




Process Log
--------------

**`C:\Users\Fran\.sonic-pi\log\processes.log`**

No pids store found here: C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids
Exiting
Creating pids store: C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids
Started [2792] [-] "C:\Program Files (x86)\Sonic Pi\app\gui\qt\release\..\..\..\..\app\server\native\ruby\bin\ruby.exe"  --enable-frozen-string-literal -E utf-8 "C:\Program Files (x86)\Sonic Pi\app\gui\qt\release\..\..\..\..\app\server\ruby\bin\sonic-pi-server.rb" -u 4557 4558 4556 4556 4559 4560 4561 4562 [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/2792
Started [8548] [-] "C:\Program Files (x86)\Sonic Pi\app\server\native\scsynth.exe" -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U "C:/Program Files (x86)/Sonic Pi/app/server/native/plugins/" -b 4096 -B 127.0.0.1 [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/8548
Started [1900] [-] "C:/Program Files (x86)/Sonic Pi/app/server/native/erlang/bin/erl.exe" -noshell -pz "C:/Program Files (x86)/Sonic Pi/app/server/erlang" -s pi_server start 4560 [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/1900
Started [8364] [-] 'C:/Program Files (x86)/Sonic Pi/app/server/native/osmid/o2m' -L -b -i 4561 -O 4562 -m 6 [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/8364
Started [704] [-] 'C:/Program Files (x86)/Sonic Pi/app/server/native/osmid/m2o' -b -o 4562 -m 6 'Sonic Pi' [-] C:/Users/Fran/AppData/Local/Temp/sonic-pi-pids/704