Critical error booting Sonic Pi 3.3.1 on Windows 10 #2738

confusedTurtl3 · 2021-03-29T11:54:33Z

I've seen many reports that look similar to this one and tried some of the solutions suggested. I tried installing asio4all and modifying the scsynthexternal.rb file but it didn't work (I'm not sure I did it right, anyway). I suspect the problem is somehow connected to using bluetooth headphones, although once it appears for the first time I have no chance to open the program again, no matter what audio device I'm using.

Sonic Pi Boot Error Report

System Information

Sonic Pi version: 3.3.1
OS: Windows 10 Version 1909

GUI Log

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

[GUI] -                            
[GUI] -                            
[GUI] -                            
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {a6fd485a-3744-4414-8a0a-17778fd8b4ed}
[GUI] - ui locale:  es-ES
[GUI] - sys locale: es_ES
[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] - starting UDP OSC Server on port 51236...
[GUI] - launching Sonic Pi Runtime Server:
[GUI] - unable to listen to UDP OSC messages[GUI] - Ruby server pid registered: 16132
[GUI] - w[GUI] - Ruby server pid registered: 7628
[GUI] - wait for syn...
[GUI] - Sonic Pi Server failed to start with this error message: 
      > Port unavailable: 51235, is Sonic Pi already running?
[GUI] - UDP OSC Server no longer listening
....
[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] - Critical Error. Unable to connect to server..

The text was updated successfully, but these errors were encountered:

ethancrawford · 2021-03-29T12:18:16Z

@confusedTurtl3 - notice the following line in the log:

Port unavailable: 51235, is Sonic Pi already running?

This means you may need to close whatever is using that port. (Provided it is not system-critical of course).

confusedTurtl3 · 2021-03-29T12:34:30Z

@ethancrawford The port doesn't seem to be under use right now, but if I try to launch Sonic Pi now, the critical error window doesn't appear either. The program appears to be opened in the task bar, but when I click on it, nothing happens. The preview when setting the mouse over it is just a blank page.

ethancrawford · 2021-03-29T12:38:03Z

Sure. It's worth using task manager to close Ruby (assuming you don't have any other critical apps running that are using it), Sonic Pi, and scsynth. Then try again.

Hopefully then it will either start successfully, or at least produce an error report window.
If the error report window appears, then you can click 'Show details' to reveal the report, and paste it here.

confusedTurtl3 · 2021-03-29T12:53:29Z

None of those processes appeared in task manager so I couldn't close them manually. I restarted the computer and got an error window again. I don't know why it shows so little info now...

Sonic Pi Boot Error Report

System Information

Sonic Pi version: 3.3.1
OS: Windows 10 Version 1909

GUI Log

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

ethancrawford · 2021-03-29T13:00:46Z

Confusing indeed!
If you're up for troubleshooting this a little longer, could you try removing your sound configuration customisations and seeing if the error report becomes more useful?

confusedTurtl3 · 2021-03-29T13:08:16Z

Sure I'm up to it, but I'd need you to explain me what those sound configs are and how to change them. I'm sorry, I'm a bit lost...

ethancrawford · 2021-03-29T13:17:44Z

oh sure, no problem. You mentioned you had attempted to alter scsynthexternal for example. There is now an easier way to tell scsynth about your preferred sound settings - there is an audio-settings.toml file, where you can specify the name of your preferred sound device, change the sampling rate, etc etc. If necessary, we can get to that later. For the moment, I would at least:

undo any changes you made to scsynthexternal and any other files in the app
leave the bluetooth headphones unconnected
attempt to boot Sonic Pi up again
If that doesn't produce a more helpful error report, then I'll have to put another thinking cap on...

confusedTurtl3 · 2021-03-29T14:05:21Z

Thanks very much.

When I opened this thread all changes to the app files had already been undone. Also, all reported attempts were done without the headphones connected. Now I just can't get the error report but get the blank page again, despite no ruby, sonicpi or scsynth processes opened (at least nothing appears in task manager). I also tried restarting the computer again and still didn't get any report. Maybe I should uninstall and install again?

ethancrawford · 2021-03-29T14:09:14Z

Not quite - it's worth quickly checking to see if there are any log file messages at all, in C:\Users\Fernando\.sonic-pi\log\ - particularly server-errors.log, server-output.log, or scsynth.log. If there's nothing (or nothing useful) there, then you could try reinstalling.

confusedTurtl3 · 2021-03-29T15:52:24Z

This is what I found in server-output.log:

Sonic Pi server booting...
The time is 2021-03-29 16:00:19 +0200
Warning, you have an older init.rb file in C:/Users/Fernando/.sonic-pi/init.rb which is now being ignored as your newer config/init.rb file is being used instead. Consider deleting your old init.rb (perhaps copying anything useful across first).
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
Started [11292] [-] "C:\Program Files\Sonic Pi\app\server\native\scsynth.exe" -u 51237 -a 1024 -m 131072 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 -U "C:/Program Files/Sonic Pi/app/server/native/plugins/" [-] C:/Users/Fernando/AppData/Local/Temp/sonic-pi-pids/11292
Starting Server Runtime
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:51237
Boot - Receiving ack from scsynth
Boot - Server connection established
Studio - Initialised SuperCollider Audio Server v3.11.2
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/Sonic Pi/app/server/native/erlang/bin/erl.exe" +C multi_time_warp -noshell -pz "C:/Program Files/Sonic Pi/app/server/erlang/sonic_pi_server/ebin" -sonic_pi_server api_port 51238 in_port 4560 cue_port 51235 enabled false -s pi_server start
Server Runtime Initialised

This is Sonic Pi v3.3.1 running on windows with ruby version 3.0.0 with api 3.0.0.
Sonic Pi Server successfully booted.

Started [6900] [-] "C:/Program Files/Sonic Pi/app/server/native/erlang/bin/erl.exe" +C multi_time_warp -noshell -pz "C:/Program Files/Sonic Pi/app/server/erlang/sonic_pi_server/ebin" -sonic_pi_server api_port 51238 in_port 4560 cue_port 51235 enabled false -s pi_server start [-] C:/Users/Fernando/AppData/Local/Temp/sonic-pi-pids/6900
Received /ping, sending /ack to GUI
Received /ping, sending /ack to GUI
Server is exiting.
Shutting down GUI...
Goodbye :-)
Exiting - shutting down scsynth server...
Sending /quit command to scsynth
Stopping OSC server...
Stopped OSC server...

And this is what I found in scsynth.log:

Starting SuperCollider 2021-03-29 16:00:20

Device options:

MME : Asignador de sonido Microsoft - Input (device #0 with 2 ins 0 outs)
MME : Micrófono (Conexant SmartAudio (device play_pads not stopping #1 with 2 ins 0 outs)
MME : Asignador de sonido Microsoft - Output (device Thread sync/drift #2 with 0 ins 2 outs)
MME : Altavoces (Conexant SmartAudio (device Note lengths vs BPM #3 with 0 ins 2 outs)
Windows DirectSound : Controlador primario de captura de sonido (device Auto stop after about 4 minutes #4 with 2 ins 0 outs)
Windows DirectSound : Micrófono (Conexant SmartAudio HD) (device Removes binaries from source tree. #5 with 2 ins 0 outs)
Windows DirectSound : Controlador primario de sonido (device Use $HOME rather than /home/pi #6 with 0 ins 2 outs)
Windows DirectSound : Altavoces (Conexant SmartAudio HD) (device Add facility to select sound output #7 with 0 ins 2 outs)
ASIO : ASIO4ALL v2 (device current_tempo not working? #8 with 2 ins 2 outs)
ASIO : FL Studio ASIO (device Ten possible development requests #9 with 2 ins 2 outs)
Windows WASAPI : Altavoces (Conexant SmartAudio HD) (device Add modified play_pattern_timed command #10 with 0 ins 2 outs)
Windows WASAPI : Micrófono (Conexant SmartAudio HD) (device Improve chord commands #11 with 2 ins 0 outs)
Windows WDM-KS : Speakers (Conexant HD Audio output) (device Add tempo command to work with timed notes #12 with 0 ins 2 outs)
Windows WDM-KS : Micrófono (Conexant HD Audio capture) (device Add global feature for with_synth command #13 with 2 ins 0 outs)

Requested devices:
In:

(default)
Out:
(default)

Selecting default system input/output devices

Booting with:
In: MME : Micrófono (Conexant SmartAudio
Out: MME : Altavoces (Conexant SmartAudio
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.

The server-errors file is empty.

ethancrawford · 2021-03-30T03:36:19Z

Ok! Two things come to mind:

You could try to tell scsynth to start up using a different device with the new audio-settings.toml file.
- make a copy of https://github.com/sonic-pi-net/sonic-pi/blob/main/app/config/user-examples/audio-settings.toml and place it in C:\Users\Fernando\.sonic-pi\config\
- uncomment the sound_card_name = "" line and change it to something like: sound_card_name = "WASAPI" or sound_card_name = "ASIO4ALL"
- Then see if Sonic Pi boots up successfully
If that doesn't work, then it's possibly an issue to do with the unicode character in the Conexant input device name Micrófono. This was a bug in SuperCollider's scsynth sound engine that was supposedly resolved, but perhaps is still happening somehow...

ethancrawford · 2021-03-30T03:37:20Z

(Having said that, re the second point about the old bug, it seems from the logs that scsynth starts up successfully, so not sure that's the issue here).

confusedTurtl3 · 2021-03-30T09:13:08Z

That didn't work either :/. When I set the sound card name as ASIO4ALL and I try to launch Sonic Pi I get a notification from asio4all.exe saying "ASIO4ALL v2 - Scsynth 512 Samples at @44100 Hz", but after that I get the same blank page again.

ethancrawford · 2021-03-30T09:26:15Z

Ok. What do the logs say at that point?

confusedTurtl3 · 2021-03-30T09:31:14Z

Scsynth:

Starting SuperCollider 2021-03-30 11:10:35

Device options:

MME : Asignador de sonido Microsoft - Input (device #0 with 2 ins 0 outs)
MME : Micrófono (Conexant SmartAudio (device play_pads not stopping #1 with 2 ins 0 outs)
MME : Asignador de sonido Microsoft - Output (device Thread sync/drift #2 with 0 ins 2 outs)
MME : Altavoces (Conexant SmartAudio (device Note lengths vs BPM #3 with 0 ins 2 outs)
Windows DirectSound : Controlador primario de captura de sonido (device Auto stop after about 4 minutes #4 with 2 ins 0 outs)
Windows DirectSound : Micrófono (Conexant SmartAudio HD) (device Removes binaries from source tree. #5 with 2 ins 0 outs)
Windows DirectSound : Controlador primario de sonido (device Use $HOME rather than /home/pi #6 with 0 ins 2 outs)
Windows DirectSound : Altavoces (Conexant SmartAudio HD) (device Add facility to select sound output #7 with 0 ins 2 outs)
ASIO : ASIO4ALL v2 (device current_tempo not working? #8 with 2 ins 2 outs)
ASIO : FL Studio ASIO (device Ten possible development requests #9 with 2 ins 2 outs)
Windows WASAPI : Altavoces (Conexant SmartAudio HD) (device Add modified play_pattern_timed command #10 with 0 ins 2 outs)
Windows WASAPI : Micrófono (Conexant SmartAudio HD) (device Improve chord commands #11 with 2 ins 0 outs)
Windows WDM-KS : Speakers (Conexant HD Audio output) (device Add tempo command to work with timed notes #12 with 0 ins 2 outs)
Windows WDM-KS : Micrófono (Conexant HD Audio capture) (device Add global feature for with_synth command #13 with 2 ins 0 outs)

Requested devices:
In (matching device found):

ASIO4ALL
Out (matching device found):
ASIO4ALL

Booting with:
In: ASIO : ASIO4ALL v2
Out: ASIO : ASIO4ALL v2
Sample rate: 44100.000
Latency (in/out): 0.016 / 0.016 sec
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 64
SuperCollider 3 server ready.

Server output:

Sonic Pi server booting...
The time is 2021-03-30 11:10:34 +0200
Warning, you have an older init.rb file in C:/Users/Fernando/.sonic-pi/init.rb which is now being ignored as your newer config/init.rb file is being used instead. Consider deleting your old init.rb (perhaps copying anything useful across first).
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
Starting Server Runtime
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:51237
Boot - Receiving ack from scsynth
Boot - Server connection established
Studio - Initialised SuperCollider Audio Server v3.11.2
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/Sonic Pi/app/server/native/erlang/bin/erl.exe" +C multi_time_warp -noshell -pz "C:/Program Files/Sonic Pi/app/server/erlang/sonic_pi_server/ebin" -sonic_pi_server api_port 51238 in_port 4560 cue_port 51235 enabled false -s pi_server start
Server Runtime Initialised

This is Sonic Pi v3.3.1 running on windows with ruby version 3.0.0 with api 3.0.0.
Sonic Pi Server successfully booted.

Started [6844] [-] "C:\Program Files\Sonic Pi\app\server\native\scsynth.exe" -u 51237 -a 1024 -m 131072 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 -U "C:/Program Files/Sonic Pi/app/server/native/plugins/" -H ASIO4ALL [-] C:/Users/Fernando/AppData/Local/Temp/sonic-pi-pids/6844
Started [16236] [-] "C:/Program Files/Sonic Pi/app/server/native/erlang/bin/erl.exe" +C multi_time_warp -noshell -pz "C:/Program Files/Sonic Pi/app/server/erlang/sonic_pi_server/ebin" -sonic_pi_server api_port 51238 in_port 4560 cue_port 51235 enabled false -s pi_server start [-] C:/Users/Fernando/AppData/Local/Temp/sonic-pi-pids/16236
Received /ping, sending /ack to GUI
Received /ping, sending /ack to GUI
Server is exiting.
Shutting down GUI...
Goodbye :-)
Exiting - shutting down scsynth server...
Sending /quit command to scsynth
Stopping OSC server...
Stopped OSC server...

Server errors is still empty

ethancrawford · 2021-03-30T09:35:50Z

Hmm.... I can't see anything obviously wrong in all that. What does the GUI log file say?

confusedTurtl3 · 2021-03-30T09:39:01Z

[GUI] -
[GUI] -
[GUI] -
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -
[GUI] - {fbafaaad-d0aa-48c9-89de-a609fb5be070}
[GUI] - ui locale: es-ES
[GUI] - sys locale: es_ES
[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: 328
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
......
[GUI] - Sonic Pi Server successfully booted.
[GUI] - waiting for Sonic Pi Server to respond...
..
[GUI] - Sonic Pi Server connection established
[GUI] - honour prefs
[GUI] - asking OSC server to start
[GUI] - cue port in external mode
[GUI] - update prefs icon
[GUI] - toggle icons
[GUI] - full screen
[GUI] - load workspaces
[GUI] - loading workspaces
[GUI] - load request Version
[GUI] Change Volume to 80
[GUI] - boot sequence completed.
[GUI] - asking OSC server to start
[GUI] - cue port in external mode
[GUI] - writing settings
[GUI] - stopping OSC server
[GUI] - stopping UDP OSC Server...
[GUI] - saving workspaces
[GUI] - UDP OSC Server no longer listening
[GUI] - asking server process to exit...
[GUI] - executing exit script
[GUI] - exiting. Cheerio :-)

ethancrawford · 2021-03-30T09:40:48Z

Yeah, as I suspected, nothing obvious there either. I might have to defer to @samaaron on this one, apologies 😬
Hopefully someone can help you get to the bottom of this... 🤞

confusedTurtl3 · 2021-03-30T09:47:24Z

Well, thank you very much nonetheless.

kineze420 · 2022-02-20T13:06:02Z

I LOVE SONIC PI but at the same time I fucking hate this thing!!

worked just long enough to hook me and now I am just wasting my days trying to find some help to get ti working.
It didnt put out any audio, then when closed and opened again it started pushing "could not boot errors" its frustrating...reinstalling doesnt work. help please, I would love to work with this but it is eating up my nerves more that the coding I do for work....

samaaron · 2022-02-20T18:51:33Z

HI @kineze420 - whilst I appreciate you are frustrated, please try and keep to using a polite tone.

Sonic Pi is a free piece of software and whilst we try our best to make sure it runs smoothly on as many machines as possible, this is actually a very hard task without a dedicated team of testers and maintenance developers - which of course we do not have. Instead, we rely on the kind support from the community.

Also, whilst you have a boot error, it's not necessarily going to be a duplicate issue to the one in this thread, so should really warrant its own issue with a full log output so we can see what might be going wrong. It would also be useful to know which version you're trying and on which platform.

ethancrawford · 2022-02-21T03:01:10Z

@kineze420 - I second everything that Sam says above...
I have replied on your original post in the discussion forum 👍

samaaron · 2022-07-19T16:22:52Z

We have completely overhauled the process with which we boot the system, and it would still be really great to know if this has somehow not resolved your situation.

Therefore, please feel free to re-open if this is still an issue with the recently released v4 of Sonic Pi - https://github.com/sonic-pi-net/sonic-pi/releases

confusedTurtl3 changed the title ~~Critical error booting Sonic Pi~~ Critical error booting Sonic Pi 3.3.1 on Windows 10 Mar 29, 2021

ethancrawford added boot Windows labels Mar 30, 2021

samaaron closed this as completed Jul 19, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Critical error booting Sonic Pi 3.3.1 on Windows 10 #2738

Critical error booting Sonic Pi 3.3.1 on Windows 10 #2738

confusedTurtl3 commented Mar 29, 2021 •

edited

Loading

ethancrawford commented Mar 29, 2021

confusedTurtl3 commented Mar 29, 2021 •

edited

Loading

ethancrawford commented Mar 29, 2021 •

edited

Loading

confusedTurtl3 commented Mar 29, 2021 •

edited

Loading

ethancrawford commented Mar 29, 2021

confusedTurtl3 commented Mar 29, 2021

ethancrawford commented Mar 29, 2021

confusedTurtl3 commented Mar 29, 2021

ethancrawford commented Mar 29, 2021 •

edited

Loading

confusedTurtl3 commented Mar 29, 2021

ethancrawford commented Mar 30, 2021

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

kineze420 commented Feb 20, 2022

samaaron commented Feb 20, 2022

ethancrawford commented Feb 21, 2022

samaaron commented Jul 19, 2022

Critical error booting Sonic Pi 3.3.1 on Windows 10 #2738

Critical error booting Sonic Pi 3.3.1 on Windows 10 #2738

Comments

confusedTurtl3 commented Mar 29, 2021 • edited Loading

Sonic Pi Boot Error Report

System Information

GUI Log

ethancrawford commented Mar 29, 2021

confusedTurtl3 commented Mar 29, 2021 • edited Loading

ethancrawford commented Mar 29, 2021 • edited Loading

confusedTurtl3 commented Mar 29, 2021 • edited Loading

Sonic Pi Boot Error Report

System Information

GUI Log

ethancrawford commented Mar 29, 2021

confusedTurtl3 commented Mar 29, 2021

ethancrawford commented Mar 29, 2021

confusedTurtl3 commented Mar 29, 2021

ethancrawford commented Mar 29, 2021 • edited Loading

confusedTurtl3 commented Mar 29, 2021

Booting Sonic Pi

This is Sonic Pi v3.3.1 running on windows with ruby version 3.0.0 with api 3.0.0. Sonic Pi Server successfully booted.

Starting SuperCollider 2021-03-29 16:00:20

ethancrawford commented Mar 30, 2021

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

Starting SuperCollider 2021-03-30 11:10:35

Booting Sonic Pi

This is Sonic Pi v3.3.1 running on windows with ruby version 3.0.0 with api 3.0.0. Sonic Pi Server successfully booted.

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

ethancrawford commented Mar 30, 2021

confusedTurtl3 commented Mar 30, 2021

kineze420 commented Feb 20, 2022

samaaron commented Feb 20, 2022

ethancrawford commented Feb 21, 2022

samaaron commented Jul 19, 2022

confusedTurtl3 commented Mar 29, 2021 •

edited

Loading

confusedTurtl3 commented Mar 29, 2021 •

edited

Loading

ethancrawford commented Mar 29, 2021 •

edited

Loading

confusedTurtl3 commented Mar 29, 2021 •

edited

Loading

ethancrawford commented Mar 29, 2021 •

edited

Loading

This is Sonic Pi v3.3.1 running on windows with ruby version 3.0.0 with api 3.0.0.
Sonic Pi Server successfully booted.

This is Sonic Pi v3.3.1 running on windows with ruby version 3.0.0 with api 3.0.0.
Sonic Pi Server successfully booted.