Sonic Pi can't open on Windows 10. #1820

Uchida16104 · 2018-02-07T08:30:16Z

When I opened Sonic Pi, this message sent. "Critical error! - Could not boot Sonic Pi Server." I tried to open this some times, but this didn't open at all. I'm very sorry when you are so busy, but please enable to operate Sonic Pi normally.

samaaron · 2018-02-07T08:36:58Z

Sorry you’re having issues.

Did the error window contain the error messages that you could paste into his conversation?

mats42 · 2018-02-09T11:18:44Z

I seem to experience similar problem on Win 10 Pro. I installed 3.1.0 (no previos install, tried both the portable version and the MSI-install).
When starting up Sonic Pi, the the splash screen shows for a while and then a server startup error dialog show. Hope the logs below can be of any help:

Sonic Pi Boot Error Report

System Information

Sonic Pi version: 3.1.0
OS: Windows 8 (which is wrong since I'm on Windows 10)

GUI Log

C:\Users\...\.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: 7824
[GUI] - waiting for Sonic Pi Server to boot...
................................
[GUI] - Sonic Pi Server failed to start with this error message: 
      > Server Exception:
 Boot - Unable to connect to SuperCollider
 ["C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:264:in `boot_and_wait'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:344:in `boot_server_windows'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:155:in `boot'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:37:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `new'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `new'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `init_scsynth'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:56:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `new'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `block (2 levels) in included'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'"]
[GUI] - UDP OSC Server no longer listening
............................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...

Server Errors

C:\Users\...\.sonic-pi\log\server-errors.log

Server Output

C:\Users\...\.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 [8836] [-] "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/.../AppData/Local/Temp/sonic-pi-pids/8836
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 - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Unable to connect to SuperCollider
Failed to start server: Boot - Unable to connect to SuperCollider
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:264:in `boot_and_wait'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:344:in `boot_server_windows'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:155:in `boot'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:37:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `init_scsynth'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:56:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `block (2 levels) in included'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'
Server is exiting.
Shutting down GUI...
Goodbye :-)

Scsynth Output

C:\Users\...\.sonic-pi\log\scsynth.log

# Starting SuperCollider 2018-02-09 11:33:49

Device options:
  - MME : Microsoft Sound Mapper - Input   (device #0 with 2 ins 0 outs)
  - MME : Microphone Array (ASUS Virtual    (device #1 with 2 ins 0 outs)
  - MME : Microsoft Sound Mapper - Output   (device #2 with 0 ins 2 outs)
  - MME : Speakers (High Definition Audio   (device #3 with 0 ins 8 outs)
  - MME : Digital Audio (S/PDIF) (High De   (device #4 with 0 ins 2 outs)
  - MME : Digital Audio (S/PDIF) (High De   (device #5 with 0 ins 2 outs)
  - Windows DirectSound : Primary Sound Capture Driver   (device #6 with 2 ins 0 outs)
  - Windows DirectSound : Microphone Array (ASUS Virtual Audio Device (Micphone))   (device #7 with 2 ins 0 outs)
  - Windows DirectSound : Primary Sound Driver   (device #8 with 0 ins 2 outs)
  - Windows DirectSound : Speakers (High Definition Audio Device)   (device #9 with 0 ins 8 outs)
  - Windows DirectSound : Digital Audio (S/PDIF) (High Definition Audio Device)   (device #10 with 0 ins 2 outs)
  - Windows DirectSound : Digital Audio (S/PDIF) (High Definition Audio Device)   (device #11 with 0 ins 2 outs)
  - Windows WASAPI : Digital Audio (S/PDIF) (High Definition Audio Device)   (device #12 with 0 ins 2 outs)
  - Windows WASAPI : Speakers (High Definition Audio Device)   (device #13 with 0 ins 2 outs)
  - Windows WASAPI : Digital Audio (S/PDIF) (High Definition Audio Device)   (device #14 with 0 ins 2 outs)
  - Windows WASAPI : Microphone Array (ASUS Virtual Audio Device (Micphone))   (device #15 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers (HD Audio Speaker)   (device #16 with 0 ins 8 outs)
  - Windows WDM-KS : SPDIF Out (HD Audio SPDIF out 2)   (device #17 with 0 ins 2 outs)
  - Windows WDM-KS : SPDIF Out (HD Audio SPDIF out)   (device #18 with 0 ins 2 outs)
  - Windows WDM-KS : Microphone Array (ASUSVAD Wave)   (device #19 with 2 ins 0 outs)

Booting with:
  In: MME : Microphone Array (ASUS Virtual 
  Out: MME : Speakers (High Definition Audio
  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\...\.sonic-pi\log\processes.log

Clearing pids: ["3972", "7696"]

Clearing [3972]
  -- command "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
  -- removing C:/Users/.../AppData/Local/Temp/sonic-pi-pids/3972
  -- unable to get ProcTable info for: 3972
  -- process: 3972 not running

Clearing [7696]
  -- command "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
  -- removing C:/Users/.../AppData/Local/Temp/sonic-pi-pids/7696
  -- unable to get ProcTable info for: 7696
  -- process: 7696 not running

Finished clearing pids

Started [7824] [-] "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/.../AppData/Local/Temp/sonic-pi-pids/7824
Started [8836] [-] "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/.../AppData/Local/Temp/sonic-pi-pids/8836

samaaron · 2018-02-16T23:59:36Z

@mats42 - for some reason, SuperCollider doesn't seem to be able to talk back to Sonic Pi during boot on your machine. Do you have any security software that might be running and blocking UDP communications between the SuperCollider process and Sonic Pi on port 4556?

mrolappe · 2018-02-21T20:03:37Z

Same phenomenon here with Windows 10 Home (not Win 8). No special security software apart from Avira Free Antivirus. Also, I was able to successfully launch it yesterday.

Anything I can do to help with diagnosis/debugging?

Sonic Pi Boot Error Report

System Information

Sonic Pi version: 3.1.0
OS: Windows 8

GUI Log

C:\Users\jMj\.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: 8436
[GUI] - waiting for Sonic Pi Server to boot...
.................................
[GUI] - Sonic Pi Server failed to start with this error message: 
      > Server Exception:
 Boot - Unable to connect to SuperCollider
 ["C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:264:in `boot_and_wait'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:344:in `boot_server_windows'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:155:in `boot'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:37:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `new'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `new'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `init_scsynth'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:56:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `new'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `block (2 levels) in included'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'"]
[GUI] - UDP OSC Server no longer listening
...........................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...

Server Errors

C:\Users\jMj\.sonic-pi\log\server-errors.log

Server Output

C:\Users\jMj\.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 [5240] [-] "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 [-] d:/tmp/jMj/sonic-pi-pids/5240
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 - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Sending /status to server: 127.0.0.1:4556
Boot - Unable to connect to SuperCollider
Failed to start server: Boot - Unable to connect to SuperCollider
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:264:in `boot_and_wait'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:344:in `boot_server_windows'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:155:in `boot'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:37:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:78:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:183:in `init_scsynth'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:56:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:125:in `block (2 levels) in included'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'
Server is exiting.
Shutting down GUI...
Goodbye :-)

Scsynth Output

C:\Users\jMj\.sonic-pi\log\scsynth.log

# Starting SuperCollider 2018-02-21 20:50:52

Device options:
  - MME : Microsoft Soundmapper - Input   (device #0 with 2 ins 0 outs)
  - MME : Mikrofon (HD Webcam C525)   (device #1 with 1 ins 0 outs)
  - MME : VoiceMeeter Output (VB-Audio Vo   (device #2 with 8 ins 0 outs)
  - MME : Line (Steinberg UR22)   (device #3 with 2 ins 0 outs)
  - MME : Microsoft Soundmapper - Output   (device #4 with 0 ins 2 outs)
  - MME : Line (Steinberg UR22)   (device #5 with 0 ins 2 outs)
  - MME : 1 - DELL U2515H (AMD High Defin   (device #6 with 0 ins 2 outs)
  - MME : VoiceMeeter Input (VB-Audio Voi   (device #7 with 0 ins 8 outs)
  - Windows DirectSound : Primärer Soundaufnahmetreiber   (device #8 with 2 ins 0 outs)
  - Windows DirectSound : Mikrofon (HD Webcam C525)   (device #9 with 1 ins 0 outs)
  - Windows DirectSound : VoiceMeeter Output (VB-Audio VoiceMeeter VAIO)   (device #10 with 8 ins 0 outs)
  - Windows DirectSound : Line (Steinberg UR22)   (device #11 with 2 ins 0 outs)
  - Windows DirectSound : Primärer Soundtreiber   (device #12 with 0 ins 2 outs)
  - Windows DirectSound : Line (Steinberg UR22)   (device #13 with 0 ins 2 outs)
  - Windows DirectSound : 1 - DELL U2515H (AMD High Definition Audio Device)   (device #14 with 0 ins 2 outs)
  - Windows DirectSound : VoiceMeeter Input (VB-Audio VoiceMeeter VAIO)   (device #15 with 0 ins 8 outs)
  - ASIO : Generic Low Latency ASIO Driver   (device #16 with 2 ins 2 outs)
  - ASIO : Voicemeeter Virtual ASIO   (device #17 with 8 ins 8 outs)
  - ASIO : Yamaha Steinberg USB ASIO   (device #18 with 2 ins 2 outs)
  - Windows WASAPI : 1 - DELL U2515H (AMD High Definition Audio Device)   (device #19 with 0 ins 2 outs)
  - Windows WASAPI : Line (Steinberg UR22)   (device #20 with 0 ins 2 outs)
  - Windows WASAPI : VoiceMeeter Input (VB-Audio VoiceMeeter VAIO)   (device #21 with 0 ins 2 outs)
  - Windows WASAPI : VoiceMeeter Output (VB-Audio VoiceMeeter VAIO)   (device #22 with 2 ins 0 outs)
  - Windows WASAPI : Line (Steinberg UR22)   (device #23 with 2 ins 0 outs)
  - Windows WASAPI : Mikrofon (HD Webcam C525)   (device #24 with 1 ins 0 outs)
  - Windows WDM-KS : Line (Steinberg UR22)   (device #25 with 2 ins 0 outs)
  - Windows WDM-KS : Line (Steinberg UR22)   (device #26 with 0 ins 2 outs)
  - Windows WDM-KS : Speakers (Realtek HD Audio output)   (device #27 with 0 ins 6 outs)
  - Windows WDM-KS : Eingang (Realtek HD Audio Line input)   (device #28 with 2 ins 0 outs)
  - Windows WDM-KS : Stereomix (Realtek HD Audio Stereo input)   (device #29 with 2 ins 0 outs)
  - Windows WDM-KS : Mikrofon (Realtek HD Audio Mic input)   (device #30 with 2 ins 0 outs)
  - Windows WDM-KS : FrontMic (Realtek HD Audio Front Mic input)   (device #31 with 2 ins 0 outs)
  - Windows WDM-KS : Output (AMD HD Audio HDMI out #0)   (device #32 with 0 ins 2 outs)
  - Windows WDM-KS : Mikrofon (HD Webcam C525)   (device #33 with 1 ins 0 outs)
  - Windows WDM-KS : VoiceMeeter Output (VoiceMeeter vaio)   (device #34 with 8 ins 0 outs)
  - Windows WDM-KS : Speakers (VoiceMeeter vaio)   (device #35 with 0 ins 8 outs)

Booting with:
  In: MME : Mikrofon (HD Webcam C525)
  Out: MME : Line (Steinberg UR22)
  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\jMj\.sonic-pi\log\processes.log



Clearing pids: []
No pids to clear :-)
Started [8436] [-] "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 [-] d:/tmp/jMj/sonic-pi-pids/8436
Started [5240] [-] "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 [-] d:/tmp/jMj/sonic-pi-pids/5240

samaaron · 2018-02-21T20:13:10Z

@mrolappe if you temporarily disable your antivirus software does that allow Sonic Pi to boot?

mrolappe · 2018-02-21T20:35:28Z

@samaaron unfortunately not, even if temporarily disabling the firewall.

But I rebooted twice and then SonicPi successfully launched after each reboot. Before trying to launch SonicPi the first time today the computer had been in energy saving mode. Maybe it was related to that.

Thanks for your prompt response. Let me know if I can help with anything.

samaaron · 2018-02-21T21:26:24Z

Thanks for letting me know.

I'm a bit lost as to how to continue debugging this. From the logs it looks as if SuperCollider and Sonic Pi are unable to talk. However, the fact that it works sometimes and not others makes me suspect that there might be a weird race condition somewhere in the code. Although, if this is the case, I'm surprised that more people haven't reported this issue and also curious to know why it only seems to affect Windows machines...

mrolappe · 2018-02-21T21:36:41Z

Is there an easy means of checking SuperCollider reachability, like some script client to talking to SC? If the launch problem shows up again I could execute that script to see if the reachability is the problem.

samaaron · 2018-02-21T21:40:09Z

Reachability in this case is just sending it OSC messages to port 4556. In the logs, you can see that Sonic Pi is repeatedly sending the /status message and hoping for a response which either isn't received, or is and isn't correctly registered as being received.

One option would be to implement a simple OSC piggy back process which bi-directionally forwards OSC messages so you can see whether or not SuperCollider is sending/receiving the message.

mrolappe · 2018-02-21T21:56:41Z

As I lack the Ruby and OSC experience I don't know how to go about it. It's a good occasion to learn about it, though. ;-)

samaaron · 2018-02-21T21:58:09Z

If you were to try this, you wouldn't need to implement it in Ruby - any language that has an OSC library will do. Alternatively something like Wireshark might work too.

mrolappe · 2018-02-21T22:07:39Z

Thanks, I will take a look at OSC resources/docs.

mrolappe · 2018-02-22T07:29:25Z

Trying to launch SonicPi today after waking the computer from energy saving mode the error popped up again.

Unfortunately, trying to build SonicPi following the instructions for building on Windows failed for me at the gem installation step. Something about ffi.h header file not found.

samaaron · 2018-02-22T09:56:18Z

There should be no need to rebuild Sonic Pi - the OSC router I was describing would be an entirely separate system. You would just need to configure Sonic Pi to send OSC messages to your OSC router and then your OSC router would send messages to SuperCollider and the same for returning packets :-)

mrolappe · 2018-02-22T10:16:48Z

I know, I just want(ed) to be able to debug Sonic Pi OSC communication code if need be. Let's see what I can come up with regarding that OSC routing proxy. :-)

samaaron · 2018-02-22T10:22:41Z

If you're only changing Ruby code, then you should just be able to do that directly to the app's source files and either hit F8 or if that doesn't work, restart the app :-)

mrolappe · 2018-02-22T10:56:01Z

Good to know, thanks for the hint! 👍

mats42 · 2018-02-22T21:22:09Z

Sorry for not being able to investigate on my side until now :-)
I have successfully installed and tested both Sonic Pi 3.1 and SuperCollider 3.9.1 on another Windows 10 Pro machine. That one is a an older laptop with a slightly older windows 10 version: Version: 1703 ("Creators Update")
On this laptop it worked without any problem. Also tried the SuperCollider IDE and managed to get sound from that as well!

My non-working setup is a desktop computer with latest Windows 10 version:
Version: 1709 "Fall Creators Update".
It also has Avira installed but disabling all protections including firewall makes no difference.
Sonic Pi consistently fails to start on this computer. It sends OSC /status to SuperCollider but never gets any response.

I installed SuperCollider separately to check if that work but that also fails. The SC IDE starts up and when booting the server, its seems to be ok, responding with:

Booting with:
  In: MME : Microphone Array (ASUS Virtual 
  Out: MME : Speakers (High Definition Audio
  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.

but when I try to get it to play something, like:
{ [SinOsc.ar(440, 0, 0.2), SinOsc.ar(442, 0, 0.2)] }.play;

It fails with:

WARNING: server 'localhost' not running.
-> nil

even though the scsynth processs is running.

I also tried with a super simple UDP client/server in nodejs to send commands to scsynth's port but get no response back. (Hard to tell why since its UDP).

Sending UDP messages from one nodejs client to another nodejs server works well as expected (ie Windows does not seem to eat up UDP messages on localhost).

I suppose this should be a bug report to SuperCollider, haven't found any matching issue there.
I don't know what the cause might be. Could be Windows Fall Creators Update/Avira/hardware/bad luck or anything else. I could try to update Windows on my laptop to see if it stops working there...

samaaron · 2018-02-22T21:23:47Z

@mats42 - in SuperCollider you need to manually boot a server. Could you try that? The menu is Server -> Boot Server :-)

mats42 · 2018-02-22T22:54:28Z

As for SuperCollider I did boot the server manually and it did not output any error. However it's not really ok, the last thing it prints after booting is: "SuperCollider 3 server ready."
I'm pretty sure that it did write some more lines after that on my laptop where SC does work.
Also the Server status line bottom right is yellow and shows all zeros while on my laptop it was green.
My laptop is currently installing windows updates now... tomorrow I will know if SC & Sonic Pi still works there or if the update killed SC... :-)

mats42 · 2018-02-23T12:33:00Z

After updating my laptop to Windows latest "Fall Creators update" (1709) Sonic-Pi and SuperCollider still works well! So windows version could probably be ruled out.

On the desktop I completely removed Avira and a couple of other suspects but still, neither Sonic-Pi nor SuperCollider works, same as before. I also tried the latest dev-build of SuperCollider but still not working. scsynth.exe seems to hang during boot.

apgades · 2018-04-24T16:41:21Z

I was having the same problem with both Sonic Pi and SuperCollider. My initial thoughts were also that something was blocking communication with the server. It was, however, a problem with the audio device. My audio devices were listed with several device options (MME, DirectSound, ASIO, WDM-KS) and SuperCollider was defaulting to MME. Specifying the correct device option (ASIO for me) solved the problem.

In the SuperCollider IDE you can test this with s.options.device_("Your device name"); and then try booting the server. In Sonic Pi, find scsynthexternal.rb and add "-H", "Your device name" to the boot and wait statement in boot_server_windows.

26F · 2021-09-28T06:30:17Z

"Sonic Pi Boot Error Report

System Information

Sonic Pi version: 3.3.1
OS: Windows 10 Version 2009

GUI Log

C:\Users\yukum\.sonic-pi\log\gui.log

[GUI] -                            
[GUI] -                            
[GUI] -                            
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {52f9a90b-7784-4fe3-ae06-1ec991958c07}
[GUI] - ui locale:  en-US
[GUI] - sys locale: en_NZ
[GUI] - translations available 
[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 server-osc-cues : 4560 : 4560
[GUI] - Port entry erlang-router : 51238 : 51238
[GUI] - Port entry websocket : 51239 : 51239
[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 51238
[GUI] -    port: 51238 [OK]
[GUI] - Websocket port 51239
[GUI] -    port: 51239 [OK]
[GUI] - All ports OK
[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] - launching Sonic Pi Runtime Server:[GUI] - starting UDP OSC Server on port 51236...

[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 5224
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[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

C:\Users\yukum\.sonic-pi\log\server-errors.log

Server Output

C:\Users\yukum\.sonic-pi\log\server-output.log

Sonic Pi server booting...
The time is 2021-09-28 06:21:30 +1300
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: 51238
  - OK
Websocket port: 4562
  - OK
Opening UDP Server to listen to GUI on port: 51235
ERROR: Unable to write information for PID 5404 to path C:/Users/yukum/AppData/Local/Temp/sonic-pi-pids/5404!
undefined method `cmdline' for nil:NilClass

Scsynth Output

C:\Users\yukum\.sonic-pi\log\scsynth.log

# Starting SuperCollider 2021-09-28 06:21:31

Device options:
  - MME : Microsoft Sound Mapper - Input   (device #0 with 2 ins 0 outs)
  - MME : Stereo Mix (Realtek(R) Audio)   (device #1 with 2 ins 0 outs)
  - MME : Microphone (Realtek(R) Audio)   (device #2 with 2 ins 0 outs)
  - MME : Microsoft Sound Mapper - Output   (device #3 with 0 ins 2 outs)
  - MME : Headphones (Realtek(R) Audio)   (device #4 with 0 ins 2 outs)
  - MME : Speakers (Realtek(R) Audio)   (device #5 with 0 ins 2 outs)
  - Windows DirectSound : Primary Sound Capture Driver   (device #6 with 2 ins 0 outs)
  - Windows DirectSound : Stereo Mix (Realtek(R) Audio)   (device #7 with 2 ins 0 outs)
  - Windows DirectSound : Microphone (Realtek(R) Audio)   (device #8 with 2 ins 0 outs)
  - Windows DirectSound : Primary Sound Driver   (device #9 with 0 ins 2 outs)
  - Windows DirectSound : Headphones (Realtek(R) Audio)   (device #10 with 0 ins 2 outs)
  - Windows DirectSound : Speakers (Realtek(R) Audio)   (device #11 with 0 ins 2 outs)
  - ASIO : Realtek ASIO   (device #12 with 2 ins 2 outs)
  - Windows WASAPI : Headphones (Realtek(R) Audio)   (device #13 with 0 ins 2 outs)
  - Windows WASAPI : Speakers (Realtek(R) Audio)   (device #14 with 0 ins 2 outs)
  - Windows WASAPI : Microphone (Realtek(R) Audio)   (device #15 with 2 ins 0 outs)
  - Windows WASAPI : Stereo Mix (Realtek(R) Audio)   (device #16 with 2 ins 0 outs)
  - Windows WDM-KS : Microphone (Realtek Digital Microphone)   (device #17 with 2 ins 0 outs)
  - Windows WDM-KS : Headphones (Realtek HD Audio 2nd output)   (device #18 with 0 ins 2 outs)
  - Windows WDM-KS : Microphone (Realtek HD Audio Mic input)   (device #19 with 2 ins 0 outs)
  - Windows WDM-KS : Stereo Mix (Realtek HD Audio Stereo input)   (device #20 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers 1 (Realtek HD Audio output with HAP)   (device #21 with 0 ins 2 outs)
  - Windows WDM-KS : Speakers 2 (Realtek HD Audio output with HAP)   (device #22 with 0 ins 2 outs)
  - Windows WDM-KS : PC Speaker (Realtek HD Audio output with HAP)   (device #23 with 2 ins 0 outs)
  - Windows WDM-KS : Output (@System32\drivers\bthhfenum.sys,#4;%1 Hands-Free HF Audio%0

;(OPPO AX7))   (device #24 with 0 ins 1 outs)
  - Windows WDM-KS : Input (@System32\drivers\bthhfenum.sys,#4;%1 Hands-Free HF Audio%0

;(OPPO AX7))   (device #25 with 1 ins 0 outs)
  - Windows WDM-KS : Line ()   (device #26 with 2 ins 0 outs)

Requested devices:
  In:
  - (default)
  Out:
  - (default)

Selecting default system input/output devices

Booting with:
  In: MME : Stereo Mix (Realtek(R) Audio)
  Out: MME : Headphones (Realtek(R) Audio)
SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: 'Unanticipated host error'
could not initialize audio.

Process Log

C:\Users\yukum\.sonic-pi\log\processes.log


	ask-clear.rb


Clearing pids: []
No pids to clear :-)
Started [5224] [-] "C:\Program Files\Sonic Pi\app\gui\qt\build\Release\..\..\..\..\..\app\server\native\ruby\bin\ruby.exe"  --enable-frozen-string-literal -E utf-8 "C:\Program Files\Sonic Pi\app\gui\qt\build\Release\..\..\..\..\..\app\server\ruby\bin\sonic-pi-server.rb" -u 51235 51236 51237 51237 4560 51238 51239 [-] C:/Users/yukum/AppData/Local/Temp/sonic-pi-pids/5224
ERROR: Unable to write information for PID 5404 to path C:/Users/yukum/AppData/Local/Temp/sonic-pi-pids/5404!
undefined method `cmdline' for nil:NilClass

"

samaaron · 2022-07-21T00:30:15Z

We have completely overhauled the building and booting systems in the recently released v4 of Sonic Pi:

https://github.com/sonic-pi-net/sonic-pi/releases

Please give that a try and feel free to create a new issue if you're still having problems.

samaaron added boot Windows labels Feb 19, 2018

samaaron closed this as completed Jul 21, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sonic Pi can't open on Windows 10. #1820

Sonic Pi can't open on Windows 10. #1820

Uchida16104 commented Feb 7, 2018

samaaron commented Feb 7, 2018

mats42 commented Feb 9, 2018

samaaron commented Feb 16, 2018

mrolappe commented Feb 21, 2018

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018 •

edited

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018

mrolappe commented Feb 22, 2018

samaaron commented Feb 22, 2018

mrolappe commented Feb 22, 2018

samaaron commented Feb 22, 2018

mrolappe commented Feb 22, 2018

mats42 commented Feb 22, 2018

samaaron commented Feb 22, 2018

mats42 commented Feb 22, 2018

mats42 commented Feb 23, 2018

apgades commented Apr 24, 2018

26F commented Sep 28, 2021

samaaron commented Jul 21, 2022

Sonic Pi can't open on Windows 10. #1820

Sonic Pi can't open on Windows 10. #1820

Comments

Uchida16104 commented Feb 7, 2018

samaaron commented Feb 7, 2018

mats42 commented Feb 9, 2018

Sonic Pi Boot Error Report

System Information

GUI Log

Server Errors

Server Output

Scsynth Output

Process Log

samaaron commented Feb 16, 2018

mrolappe commented Feb 21, 2018

Sonic Pi Boot Error Report

System Information

GUI Log

Server Errors

Server Output

Scsynth Output

Process Log

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018 • edited

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018

samaaron commented Feb 21, 2018

mrolappe commented Feb 21, 2018

mrolappe commented Feb 22, 2018

samaaron commented Feb 22, 2018

mrolappe commented Feb 22, 2018

samaaron commented Feb 22, 2018

mrolappe commented Feb 22, 2018

mats42 commented Feb 22, 2018

samaaron commented Feb 22, 2018

mats42 commented Feb 22, 2018

mats42 commented Feb 23, 2018

apgades commented Apr 24, 2018

26F commented Sep 28, 2021

"Sonic Pi Boot Error Report

System Information

GUI Log

Server Errors

Server Output

Scsynth Output

Process Log

samaaron commented Jul 21, 2022

mrolappe commented Feb 21, 2018 •

edited