Sonic Pi Boot Error 3.3.1 Win10

Hi, I’m somewhat new to Sonic Pi, I’ve used it a few times on my mac book but for some reason whenever I try and run it on Windows 10 I’m prompted with this image_2021-09-22_065300

Also I don’t really know if this will help but when I click show details this is what comes up.

Sonic Pi Boot Error Report

System Information

  • Sonic Pi version: 3.3.1
  • OS: Windows 10 Version 2009

GUI Log

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

[GUI] -                            
[GUI] -                            
[GUI] -                            
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {609d688f-0fdc-41f3-8e70-4de84db344b0}
[GUI] - ui locale:  en-US
[GUI] - sys locale: en_US
[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 : 51238 : 51238
[GUI] - Port entry server-send-to-gui : 51238 : 51238
[GUI] - Port entry scsynth : 51239 : 51239
[GUI] - Port entry scsynth-send : 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 51238
[GUI] -    port: 51238 [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 51239
[GUI] -    port: 51239 [OK]
[GUI] - Server send to GUI port 51238
[GUI] -    port: 51238 [OK]
[GUI] - GUI send to server port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Scsynth send port 51239
[GUI] -    port: 51239 [OK]
[GUI] - Erlang router port 51240
[GUI] -    port: 51240 [OK]
[GUI] - Websocket port 51241
[GUI] -    port: 51241 [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] - starting UDP OSC Server on port 51238...[GUI] - launching Sonic Pi Runtime Server:

[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 10516
[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\ada\.sonic-pi\log\server-errors.log



Server Output

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

Sonic Pi server booting...
The time is 2021-09-22 06:54:55 -0700
Using primary protocol: udp
Detecting port numbers...
Listen port: 51235
  - OK
Scsynth port: 51239
  - OK
Scsynth send port: 51239
  - OK
OSC cues port: 4560
  - OK
Erlang port: 51240
  - OK
Websocket port: 4562
  - OK
Opening UDP Server to listen to GUI on port: 51235
ERROR: Unable to write information for PID 9088 to path C:/Users/ada/AppData/Local/Temp/sonic-pi-pids/9088!
undefined method `cmdline' for nil:NilClass

Scsynth Output

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

# Starting SuperCollider 2021-09-22 06:54:56

Device options:
  - MME : Microsoft Sound Mapper - Input   (device #0 with 2 ins 0 outs)
  - MME : Microphone Array (Realtek(R) Au   (device #1 with 2 ins 0 outs)
  - MME : Microsoft Sound Mapper - Output   (device #2 with 0 ins 2 outs)
  - MME : Speakers (Realtek(R) Audio)   (device #3 with 0 ins 6 outs)
  - Windows DirectSound : Primary Sound Capture Driver   (device #4 with 2 ins 0 outs)
  - Windows DirectSound : Microphone Array (Realtek(R) Audio)   (device #5 with 2 ins 0 outs)
  - Windows DirectSound : Primary Sound Driver   (device #6 with 0 ins 2 outs)
  - Windows DirectSound : Speakers (Realtek(R) Audio)   (device #7 with 0 ins 6 outs)
  - Windows WASAPI : Speakers (Realtek(R) Audio)   (device #8 with 0 ins 2 outs)
  - Windows WASAPI : Microphone Array (Realtek(R) Audio)   (device #9 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers 1 (Realtek HD Audio output with HAP)   (device #10 with 0 ins 2 outs)
  - Windows WDM-KS : Speakers 2 (Realtek HD Audio output with HAP)   (device #11 with 0 ins 6 outs)
  - Windows WDM-KS : PC Speaker (Realtek HD Audio output with HAP)   (device #12 with 2 ins 0 outs)
  - Windows WDM-KS : Stereo Mix (Realtek HD Audio Stereo input)   (device #13 with 2 ins 0 outs)
  - Windows WDM-KS : Microphone Array (Realtek HD Audio Mic input)   (device #14 with 2 ins 0 outs)

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

Selecting default system input/output devices

Booting with:
  In: MME : Microphone Array (Realtek(R) Au
  Out: MME : Speakers (Realtek(R) Audio)
SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: 'Unanticipated host error'
could not initialize audio.

Process Log

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


	ask-clear.rb


Clearing pids: ["7012"]

Clearing [7012]
  -- command "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 51237 51238 51238 4560 51239 51240
  -- removing C:/Users/ada/AppData/Local/Temp/sonic-pi-pids/7012
  -- force killing 7012
  -- killed 7012

Finished clearing pids

Started [10516] [-] "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 51238 51239 51239 4560 51240 51241 [-] C:/Users/ada/AppData/Local/Temp/sonic-pi-pids/10516
ERROR: Unable to write information for PID 9088 to path C:/Users/ada/AppData/Local/Temp/sonic-pi-pids/9088!
undefined method `cmdline' for nil:NilClass



Hi James :slightly_smiling_face:
Just a heads up - the ideal place for logging problems like this is our issue tracker at:
Issues · sonic-pi-net/sonic-pi · GitHub - it’s handy to keep track of things like this in one place! :slightly_smiling_face:

Having said that, there have been a handful of issues there with similar error messages:

etc…)
Maybe they might hold a few clues? Sometimes there are issues with the microphone not being enabled for example…