Sonic Pi Wont load past welcome screen

odul · October 11, 2018, 10:46pm

Hi all! I just got a new laptop and the freshly installed Sonic Pi 3.1.0. It shows the splash welcome screen for 5 to 10 seconds, then if I click the screen it disappears and sonic pi doesn’t load (if i don’t click the screen the welcome screen just stays there). If I try again it just does the same thing loading another instance of sonic pi in my task manager. I read other forums of this problem but didn’t see any solutions.

MSI laptop
Windows 10 PRO
16 gigs ram
nvidia 1060
8750 I7

I’ve ruled on resetting my computer, turning all antivirus off. I independently loaded supercollider. re-downloading and reinstalling sonic pi. Please help! This saddens me!

samaaron · October 12, 2018, 7:44am

This saddens me too!

Please could you let use know the errors in ~/.sonic-pi/log especially scsynth.log as this might point to the problem. (~ refers to your home directory).

odul · October 12, 2018, 6:33pm

I’m not as learned as other people might be. Can you explain to me how to access this log? where do I go?

odul · October 12, 2018, 6:35pm

got my trusty EE to help me find it.

Starting SuperCollider 2018-10-11 14:34:07

Device options:

MME : Microsoft Sound Mapper - Input (device #0 with 2 ins 0 outs)
MME : Microphone (Realtek® Audio) (device #1 with 2 ins 0 outs)
MME : Stereo Mix (Realtek® Audio) (device #2 with 2 ins 0 outs)
MME : Microsoft Sound Mapper - Output (device #3 with 0 ins 2 outs)
MME : Speakers (USB Audio Device) (device #4 with 0 ins 6 outs)
MME : Speakers (Realtek® Audio) (device #5 with 0 ins 2 outs)
Windows DirectSound : Primary Sound Capture Driver (device #6 with 2 ins 0 outs)
Windows DirectSound : Microphone (Realtek® Audio) (device #7 with 2 ins 0 outs)
Windows DirectSound : Stereo Mix (Realtek® Audio) (device #8 with 2 ins 0 outs)
Windows DirectSound : Primary Sound Driver (device #9 with 0 ins 2 outs)
Windows DirectSound : Speakers (USB Audio Device) (device #10 with 0 ins 6 outs)
Windows DirectSound : Speakers (Realtek® Audio) (device #11 with 0 ins 2 outs)
Windows WASAPI : Speakers (USB Audio Device) (device #12 with 0 ins 2 outs)
Windows WASAPI : Speakers (Realtek® Audio) (device #13 with 0 ins 2 outs)
Windows WASAPI : Microphone (Realtek® Audio) (device #14 with 2 ins 0 outs)
Windows WASAPI : Stereo Mix (Realtek® Audio) (device #15 with 2 ins 0 outs)
Windows WDM-KS : Speakers (Realtek HD Audio output) (device #16 with 0 ins 2 outs)
Windows WDM-KS : Stereo Mix (Realtek HD Audio Stereo input) (device #17 with 2 ins 0 outs)
Windows WDM-KS : Microphone (Realtek HD Audio Mic input) (device #18 with 2 ins 0 outs)
Windows WDM-KS : Speakers (USB Audio Device) (device #19 with 0 ins 6 outs)
Windows WDM-KS : Microphone (USB Audio Device) (device #20 with 2 ins 0 outs)

Booting with:
In: MME : Microphone (Realtek® Audio)
Out: MME : Speakers (USB Audio Device)
SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: ‘Unanticipated host error’
could not initialize audio.

odul · October 12, 2018, 7:09pm

got it!, I disabled unused audio devices. I guess this worked because its working now!

janewithoutbrain · May 13, 2019, 9:52am

Hello
I have the same problem, and, as I’ve checked, the log file has got no errors. Can you explain how did you start this SuperCollider thing, please? I know nothing about it, but wanna try to do the same to make SonicPi work

samaaron · May 13, 2019, 1:15pm

Hi @janewithoutbrain,

sorry you’re having issues too. Could you share the contents of the logs so we can have a closer look to see what might be going wrong for you?

janewithoutbrain · May 13, 2019, 7:10pm

@samaaron thanks for such a fast reply!
After two reboots of my laptop, Sonic Pi has finally loaded, yay!

But in case I have this problem again I’ll describe the details. Everything starts exactly as Odul described it above, but even after I press “End task” for all the copies of Sonic Pi process in the Task manager, the app notifies me that its another copy is still running. Then it tries to restart the process and I see the welcome screen again; nothing happens.

Regarding the log files - most of them, including scsynth.log, are just empty. This is all I’ve found:

server-output.log

Sonic Pi server booting…
Using protocol: udp
Detecting port numbers…
Send port: 4558
Listen port: 4557
Port 4557 unavailable. Perhaps Sonic Pi is already running?

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 [Not Available]
[GUI] - Server incoming OSC cues port 4559
[GUI] - port: 4559 [OK]
[GUI] - Scsynth port 4556
[GUI] - port: 4556 [Not Available]
[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 [Not Available]
[GUI] - OSC MIDI out port 4561
[GUI] - port: 4561 [Not Available]
[GUI] - OSC MIDI in port 4562
[GUI] - port: 4562 [Not Available]
[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: 2272
[GUI] - waiting for Sonic Pi Server to boot…
.
[GUI] - Sonic Pi Server failed to start with this error message:
> Port unavailable: 4557, is scsynth already running?
[GUI] - UDP OSC Server no longer listening
…
[GUI] - Critical error! Could not boot Sonic Pi Server.

processes.log

No pids store found here: D:/SonicPiPortable/Data/Temp/sonic-pi-pids
Exiting
Creating pids store: D:/SonicPiPortable/Data/Temp/sonic-pi-pids
Started [2272] [-] “D:\SonicPiPortable\App\Sonic Pi\app\gui\qt\release…\app\server\native\ruby\bin\ruby.exe” --enable-frozen-string-literal -E utf-8 “D:\SonicPiPortable\App\Sonic Pi\app\gui\qt\release…\app\server\ruby\bin\sonic-pi-server.rb” -u 4557 4558 4556 4556 4559 4560 4561 4562 [-] D:/SonicPiPortable/Data/Temp/sonic-pi-pids/2272

samaaron · May 13, 2019, 10:21pm

Looks like you already have a program that’s using port number 4557 running on your system. Perhaps the easiest way to possibly fix this is to reboot and try and start Sonic Pi again. Does that work?

janewithoutbrain · May 14, 2019, 6:37am

Yes, it does, but after a few reboots in a row.
Anyway, thanks a lot! The product itself is amazing.

loFicus · April 8, 2021, 11:25pm

Hi,

I’ve had no luck getting sonic pi to open on my Win 10 or Win 7 PC.

This is a GUI log on my Win 10 PC which shows an error:

[GUI] -
[GUI] -
[GUI] -
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -
[GUI] - {f8051c91-0ab6-4502-8ac1-c6b476e09573}
[GUI] - ui locale: en-GB
[GUI] - sys locale: en_AU
[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: 8356
[GUI] - wait for sync
[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/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:296:in boot_and_wait'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:397:in boot_server_windows’”, “C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:176:in boot'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:58:in initialize’”, “C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in new'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in initialize’”, “C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in new'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in init_scsynth’”, “C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:52:in initialize'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in new’”, “C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in block (2 levels) in included'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/ixi.rb:72:in block (2 levels) in included’”, “C:/Program Files/Sonic Pi/app/gui/qt/build/Release/…/…/…/…/…/app/server/ruby/bin/sonic-pi-server.rb:344:in new'", "C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:344:in '”]
[GUI] - UDP OSC Server no longer listening
…
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server…
[GUI] - Critical Error. Unable to connect to server…
[GUI] - Aborting. Sorry about this.
[GUI] - executing exit script

…and this is the server-output log:

Sonic Pi server booting…
The time is 2021-04-09 08:57:15 +1000
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 [7924] [-] “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/info/AppData/Local/Temp/sonic-pi-pids/7924
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 - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Unable to connect to SuperCollider
Failed to start server: Boot - Unable to connect to SuperCollider
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:296:in boot_and_wait' C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:397:in boot_server_windows’
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:176:in boot' C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:58:in initialize’
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in new' C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in initialize’
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in new' C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in init_scsynth’
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:52:in initialize' C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in new’
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in block (2 levels) in included' C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/ixi.rb:72:in block (2 levels) in included’
C:/Program Files/Sonic Pi/app/gui/qt/build/Release/…/…/…/…/…/app/server/ruby/bin/sonic-pi-server.rb:344:in new' C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:344:in ’

ethancrawford · April 9, 2021, 12:20am

@loFicus - just a heads up, the best place for help with errors when Sonic Pi fails to start up is on the GitHub issues page:

There is is quite possible that folks might have had similar issues, so there might already be clues if you search there for a similar problem. (Also, if not, it’s easier to track issues in one central location rather than spread between multiple websites).

Having said that, the two log files about the GUI and server output are just some of the logs. There are a couple of others that might be useful - particularly scsynth.log and server-errors.log - can we see those too? Usually when Sonic Pi fails to start up, a window appears that has a ‘show details’ button - clicking that reveals an error report collecting the logs together. If you see that, you can share it with us

loFicus · April 9, 2021, 12:28am

@ethancrawford Thanks for getting back to me.

I will pursue these on the github site in future, thanks for the tip

This is the log under the “show details” button BTW…

Sonic Pi Boot Error Report

System Information

Sonic Pi version: 3.3.1
OS: Windows 10 Version 2009

GUI Log

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

[GUI] -                            
[GUI] -                            
[GUI] -                            
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {6b10f15f-7a06-423d-b669-6aa8703eede0}
[GUI] - ui locale:  en-GB
[GUI] - sys locale: en_AU
[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: 448
[GUI] - wait for sync
[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/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:296:in `boot_and_wait'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:397:in `boot_server_windows'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:176:in `boot'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:58:in `initialize'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in `new'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in `initialize'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in `new'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in `init_scsynth'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:52:in `initialize'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `new'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `block (2 levels) in included'", "C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/ixi.rb:72:in `block (2 levels) in included'", "C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:344:in `new'", "C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:344:in `<main>'"]
[GUI] - UDP OSC Server no longer listening
...........................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - Critical Error. Unable to connect to server..

Server Errors

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

Server Output

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

Sonic Pi server booting...
The time is 2021-04-09 10:23:30 +1000
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 [4100] [-] "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/info/AppData/Local/Temp/sonic-pi-pids/4100
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 - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Unable to connect to SuperCollider
Failed to start server: Boot - Unable to connect to SuperCollider
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:296:in `boot_and_wait'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:397:in `boot_server_windows'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:176:in `boot'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:58:in `initialize'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in `new'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:80:in `initialize'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in `new'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:117:in `init_scsynth'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:52:in `initialize'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `new'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `block (2 levels) in included'
C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/lang/ixi.rb:72:in `block (2 levels) in included'
C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:344:in `new'
C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:344:in `<main>'

Scsynth Output

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

# Starting SuperCollider 2021-04-09 10:23:30

Device options:
  - MME : Microsoft Sound Mapper - Input   (device #0 with 2 ins 0 outs)
  - MME : Microphone (EpocCam Camera Audi   (device #1 with 2 ins 0 outs)
  - MME : Microphone (Iriun Webcam #2)   (device #2 with 2 ins 0 outs)
  - MME : Microphone (Iriun Webcam)   (device #3 with 2 ins 0 outs)
  - MME : Microphone Array (Realtek High    (device #4 with 2 ins 0 outs)
  - MME : Microsoft Sound Mapper - Output   (device #5 with 0 ins 2 outs)
  - MME : Headphones (Realtek High Defini   (device #6 with 0 ins 2 outs)
  - MME : Speakers (Realtek High Definiti   (device #7 with 0 ins 2 outs)
  - Windows DirectSound : Primary Sound Capture Driver   (device #8 with 2 ins 0 outs)
  - Windows DirectSound : Microphone (EpocCam Camera Audio)   (device #9 with 2 ins 0 outs)
  - Windows DirectSound : Microphone (Iriun Webcam #2)   (device #10 with 2 ins 0 outs)
  - Windows DirectSound : Microphone (Iriun Webcam)   (device #11 with 2 ins 0 outs)
  - Windows DirectSound : Microphone Array (Realtek High Definition Audio(SST))   (device #12 with 2 ins 0 outs)
  - Windows DirectSound : Primary Sound Driver   (device #13 with 0 ins 2 outs)
  - Windows DirectSound : Headphones (Realtek High Definition Audio(SST))   (device #14 with 0 ins 2 outs)
  - Windows DirectSound : Speakers (Realtek High Definition Audio(SST))   (device #15 with 0 ins 2 outs)
  - Windows WASAPI : Speakers (Realtek High Definition Audio(SST))   (device #16 with 0 ins 2 outs)
  - Windows WASAPI : Headphones (Realtek High Definition Audio(SST))   (device #17 with 0 ins 2 outs)
  - Windows WASAPI : Microphone (EpocCam Camera Audio)   (device #18 with 2 ins 0 outs)
  - Windows WASAPI : Microphone (Iriun Webcam #2)   (device #19 with 2 ins 0 outs)
  - Windows WASAPI : Microphone (Iriun Webcam)   (device #20 with 2 ins 0 outs)
  - Windows WASAPI : Microphone Array (Realtek High Definition Audio(SST))   (device #21 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers 1 (Realtek HD Audio output with SST)   (device #22 with 0 ins 2 outs)
  - Windows WDM-KS : Speakers 2 (Realtek HD Audio output with SST)   (device #23 with 0 ins 2 outs)
  - Windows WDM-KS : PC Speaker (Realtek HD Audio output with SST)   (device #24 with 2 ins 0 outs)
  - Windows WDM-KS : Headphones 1 (Realtek HD Audio 2nd output with SST)   (device #25 with 0 ins 2 outs)
  - Windows WDM-KS : Headphones 2 (Realtek HD Audio 2nd output with SST)   (device #26 with 0 ins 2 outs)
  - Windows WDM-KS : PC Speaker (Realtek HD Audio 2nd output with SST)   (device #27 with 2 ins 0 outs)
  - Windows WDM-KS : Microphone Array (Realtek HD Audio Mic Array input)   (device #28 with 2 ins 0 outs)
  - Windows WDM-KS : Headset Microphone (Realtek HD Audio Mic input)   (device #29 with 2 ins 0 outs)
  - Windows WDM-KS : MIDI (Iriun Webcam Audio #2)   (device #30 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers (Microsoft Docking Station Audio Device Device)   (device #31 with 0 ins 2 outs)
  - Windows WDM-KS : Microphone (Microsoft Docking Station Audio Device Device)   (device #32 with 2 ins 0 outs)
  - Windows WDM-KS : MIDI (Iriun Webcam Audio)   (device #33 with 2 ins 0 outs)
  - Windows WDM-KS : MIDI (EpocCam Audio)   (device #34 with 2 ins 0 outs)
  - Windows WDM-KS : Output (EpocCam Audio)   (device #35 with 0 ins 2 outs)

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

Selecting default system input/output devices

Booting with:
  In: MME : Microphone (EpocCam Camera Audi
  Out: MME : Headphones (Realtek High Defini
  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\info\.sonic-pi\log\processes.log


	ask-clear.rb


Clearing pids: []
No pids to clear :-)
Started [448] [-] "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/info/AppData/Local/Temp/sonic-pi-pids/448
Started [4100] [-] "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/info/AppData/Local/Temp/sonic-pi-pids/4100

ethancrawford · April 9, 2021, 12:48am

Ah yes, the good old Epoc camera audio driver…
This one seems to be an issue for a bunch of people. I’m not sure why exactly. There are a couple of things you can do.
See App fail to launch on Win10 · Issue #2734 · sonic-pi-net/sonic-pi · GitHub and the comments that follow it.
In short: selecting an alternate audio device within Sonic Pi’s configuration may help, or removing the Epoc driver.

loFicus · April 9, 2021, 12:54am

EpocCam has never been fun (unfortunately)- I uninstalled it and am up and running!

Thank you!!

ethancrawford · April 9, 2021, 12:55am

You’re welcome! It would be nice if there was a way to know what the exact problem with Epoc was and how to make them play nicely together, but in the meantime, glad you got it working

loFicus · April 9, 2021, 1:11am

The big issue I’ve had with EpocCam has been that the driver signing is never valid/trusted, so I’ve always had to run it with driver signing disabled.

I have better luck with iriun, drawback being that it is wireless only, and lower resolution available.

ethancrawford · April 9, 2021, 1:12am

Ah! I see, fair enough

Topic		Replies	Views
Sonic Pi Won't load past welcome screen windows 10 Support, Help & Resources	1	524	December 2, 2019
Sonic Pi will not load past welcome screen? Support, Help & Resources	6	2356	April 25, 2019
Win10: Sonic Pi does not start but only after displays the splash screen Support, Help & Resources	1	571	April 24, 2019
Help request - Sonic Pi not running in Windows 10 Support, Help & Resources	7	2203	June 14, 2019
Sonic Pi 3.1.0 not working anymore after Windows 10 Spring Creators Update [P] Patreon Support	4	2496	June 23, 2018