search

sonic-pi-net / sonic-pi

Code. Music. Live.
https://sonic-pi.net
Other
10.75k stars 918 forks source link

Critical Error could not boot Sonic Pi Server - Sonic Pi for Win ver 3.1.0 #1881

Closed alexzuki closed 2 years ago

alexzuki commented 6 years ago

Error detail:

onic Pi Boot Error Report

System Information

GUI Log

C:\Users\User\.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: 5084
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - UDP OSC Server no longer listening

Server Errors

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

Server Output

C:\Users\User\.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 [7696] [-] "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/User/AppData/Local/Temp/sonic-pi-pids/7696

Scsynth Output

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

# Starting SuperCollider 2018-04-16 23:52:12

Device options:
  - MME : Mapeador de som da Microsoft - Input   (device #0 with 2 ins 0 outs)
  - MME : Entrada (Scarlett 18i20 USB)   (device #1 with 18 ins 0 outs)
  - MME : Mapeador de som da Microsoft - Output   (device #2 with 0 ins 2 outs)
  - MME : Saída de Linha (Scarlett 18i20    (device #3 with 0 ins 20 outs)
  - MME : Alto-falantes (Realtek High Def   (device #4 with 0 ins 8 outs)
  - Windows DirectSound : Driver de captura de som primário   (device #5 with 2 ins 0 outs)
  - Windows DirectSound : Entrada (Scarlett 18i20 USB)   (device #6 with 18 ins 0 outs)
  - Windows DirectSound : Driver de som primário   (device #7 with 0 ins 2 outs)
  - Windows DirectSound : Saída de Linha (Scarlett 18i20 USB)   (device #8 with 0 ins 20 outs)
  - Windows DirectSound : Alto-falantes (Realtek High Definition Audio)   (device #9 with 0 ins 8 outs)
  - ASIO : ASIO4ALL v2   (device #10 with 2 ins 8 outs)
  - ASIO : Focusrite USB 2.0 Audio Driver   (device #11 with 18 ins 20 outs)
  - Windows WASAPI : Saída de Linha (Scarlett 18i20 USB)   (device #12 with 0 ins 2 outs)
  - Windows WASAPI : Alto-falantes (Realtek High Definition Audio)   (device #13 with 0 ins 2 outs)
  - Windows WASAPI : Entrada (Scarlett 18i20 USB)   (device #14 with 2 ins 0 outs)
  - Windows WDM-KS : Mixagem estéreo (Realtek HD Audio Stereo input)   (device #15 with 2 ins 0 outs)
  - Windows WDM-KS : Microfone (Realtek HD Audio Mic input)   (device #16 with 2 ins 0 outs)
  - Windows WDM-KS : Entrada (Realtek HD Audio Line input)   (device #17 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers (Realtek HD Audio output)   (device #18 with 0 ins 8 outs)
  - Windows WDM-KS : Output (Scarlett 18i20 USB)   (device #19 with 0 ins 20 outs)
  - Windows WDM-KS : Input (Scarlett 18i20 USB)   (device #20 with 18 ins 0 outs)

Booting with:
  In: MME : Entrada (Scarlett 18i20 USB)
  Out: MME : Saída de Linha (Scarlett 18i20 
SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: 'Unanticipated host error'
could not initialize audio.

Process Log

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



Clearing pids: []
No pids to clear :-)
Started [5084] [-] "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/User/AppData/Local/Temp/sonic-pi-pids/5084
Started [7696] [-] "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/User/AppData/Local/Temp/sonic-pi-pids/7696
SunderB commented 6 years ago

SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: 'Unanticipated host error' could not initialize audio. hmm... Maybe Supercollider could be having an issue with some audio drivers?

Could you tell us more about your audio hardware (speakers, microphones, headsets, etc.), and could you tell us what Saída de Linha (Scarlett 18i20 is?

Maybe you're having a similar issue as https://github.com/samaaron/sonic-pi/issues/1362?

spookymattress commented 6 years ago

Same issue here. Windows 10, Sonic PI 3.1.0. Cannot load and crashes with error.

Logs

Sonic Pi Boot Error Report

System Information

GUI Log

C:\Users\tgu\.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: 15188
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - UDP OSC Server no longer listening

Server Errors

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

Server Output

C:\Users\tgu\.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

Scsynth Output

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

# Starting SuperCollider 2018-05-04 12:24:45

Device options:
  - MME : Microsoft Sound Mapper - Input   (device #0 with 2 ins 0 outs)
  - MME : Microphone Array (Realtek High    (device #1 with 2 ins 0 outs)
  - MME : Microsoft Sound Mapper - Output   (device #2 with 0 ins 2 outs)
  - MME : Højtaler/Hovedtelefoner (Realte   (device #3 with 0 ins 2 outs)
  - Windows DirectSound : Primary Sound Capture Driver   (device #4 with 2 ins 0 outs)
  - Windows DirectSound : Microphone Array (Realtek High Definition Audio)   (device #5 with 2 ins 0 outs)
  - Windows DirectSound : Primary Sound Driver   (device #6 with 0 ins 2 outs)
  - Windows DirectSound : Højtaler/Hovedtelefoner (Realtek High Definition Audio)   (device #7 with 0 ins 2 outs)
  - Windows WASAPI : Højtaler/Hovedtelefoner (Realtek High Definition Audio)   (device #8 with 0 ins 2 outs)
  - Windows WASAPI : Microphone Array (Realtek High Definition Audio)   (device #9 with 2 ins 0 outs)
  - Windows WDM-KS : Microphone Array (Realtek HD Audio Mic input)   (device #10 with 2 ins 0 outs)
  - Windows WDM-KS : Speakers (Realtek HD Audio output)   (device #11 with 0 ins 2 outs)

Booting with:
  In: MME : Microphone Array (Realtek High 
  Out: MME : Højtaler/Hovedtelefoner (Realte
**SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: 'Unanticipated host error'
could not initialize audio.**

Process Log

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


Clearing pids: []
No pids to clear :-)
Started [15188] [-] "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/tgu/AppData/Local/Temp/sonic-pi-pids/15188
samaaron commented 6 years ago

@spookymattress sorry about this - looks like a weird Windows/SuperCollider error. Is there any chance you could try to boot a vanilla SuperCollider server and chat with their devs over on http://github.com/supercollider/supercollider/issues

spookymattress commented 6 years ago

Some debugging info that might help.

I just tried installing SuperCollider as stand-alone. Got the exact same error message, when I selected "boot server".

After googling I came by this post (http://superdupercollider.blogspot.dk/2013/10/installing-supercollider-on-windows-7.html), and installed ASIO4ALL as suggested, and created the startup.scd file, and then I could boot the server in SuperCollider. Wuhhuuu...

So, my question is now, if I can change the same for Sonic PI?? Any config file that I can change for SuperCollider in Sonic PI maybe?

(I'm all new to this, btw :)

samaaron commented 6 years ago

ah, very interesting !

unfortunately, the config you're looking to modify isn't yet modifiable without editing the source. However if you are willing to try then you just need to edit your local version of this file:

https://github.com/samaaron/sonic-pi/blob/master/app/server/ruby/lib/sonicpi/scsynthexternal.rb#L344

And add the line: 

 "-H", "ASIO4ALL",

and then see if that fixes things :-)

spookymattress commented 6 years ago

Oh my, that did the trick!! :D - You are genius!

So, this could be the solution to the guy above!

So, if you experience an error like below

SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: 'Unanticipated host error' could not initialize audio.

try the following work-around:

  1. Install ASIO4ALL
  2. Add the line: "-H", "ASIO4ALL", to this file: https://github.com/samaaron/sonic-pi/blob/master/app/server/ruby/lib/sonicpi/scsynthexternal.rb#L344
samaaron commented 6 years ago

This is great to hear!

alexzuki commented 6 years ago

Hi Guys...

Tanks a lot to put me on picture. I’ll try this solution and later on I’ll report about the results

Regards,

Alex.

De: Sam Aaron notifications@github.com Enviada em: sexta-feira, 4 de maio de 2018 09:20 Para: samaaron/sonic-pi sonic-pi@noreply.github.com Cc: alexzuki azuchic@terra.com.br; Author author@noreply.github.com Assunto: Re: [samaaron/sonic-pi] Critical Error could not boot Sonic Pi Server - Sonic Pi for Win ver 3.1.0 (#1881)

This is great to hear!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/samaaron/sonic-pi/issues/1881#issuecomment-386584252 , or mute the thread https://github.com/notifications/unsubscribe-auth/AkqupKxWZ-fTzVxcKWMaelHAY08iOkTbks5tvEeMgaJpZM4TXkX5 . https://github.com/notifications/beacon/AkqupKXc9Q7AZllwb1jVD6X0VXabC3nsks5tvEeMgaJpZM4TXkX5.gif

Este email foi escaneado pelo Avast antivírus. https://www.avast.com/antivirus

landmammalalloy commented 5 years ago

Thanks a ton, this resolved the same issue for me \m/

dave7895 commented 3 years ago

It worked for me as well after putting it in the appropiate block. Found it locally at around ll. 370ff But: my usb-c headphones still don't work, probably due to drivers, the speakers are always default output.

git-oberoi commented 3 years ago

just make sure microphone is turned on..... i tackled this by just turning on the mic.

alexzuki commented 3 years ago

Right. I`ll try this. Appreciate> Tanks a lot. Alex.

Em 9 de dez de 2020, à(s) 20:45, shivoberoi notifications@github.com escreveu:

just make dure microphone is turned on..... i tackled this by just turning on the mic.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sonic-pi-net/sonic-pi/issues/1881#issuecomment-742134662, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJFK5JEG3G7YMUJSZHBBBDDSUAD25ANCNFSM4E26IX4Q.

g8tr1522 commented 2 years ago

Hi. I am having this issue also. I have already successfully gotten the latest version of supercollider to launch using the trick mentioned by @spookymattress

Some debugging info that might help.

I just tried installing SuperCollider as stand-alone. Got the exact same error message, when I selected "boot server".

After googling I came by this post (http://superdupercollider.blogspot.dk/2013/10/installing-supercollider-on-windows-7.html), and installed ASIO4ALL as suggested, and created the startup.scd file, and then I could boot the server in SuperCollider. Wuhhuuu...

So, my question is now, if I can change the same for Sonic PI?? Any config file that I can change for SuperCollider in Sonic PI maybe?

(I'm all new to this, btw :)

So I should be good to go with ASIO. But when I try inserting the new line "-H", "ASIO4ALL", Well I have ASIO4ALL v2. So I use this instead: "-H", "ASIO4ALL v2", I get an error message. Here's the relevant output from the GUI log:

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

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

C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:23:in `require_relative': C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:472: syntax error, unexpected ',', expecting end-of-input (SyntaxError)
 "-H", "ASIO4ALL v2",
     ^
    from C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/server.rb:23:in `<top (required)>'
    from C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:14:in `require_relative'
    from C:/Program Files/Sonic Pi/app/server/ruby/lib/sonicpi/studio.rb:14:in `<top (required)>'
    from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:20:in `require_relative'
    from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:20:in `<main>'

okay, so I guess I remove the comma? I did, and then I got this output:

CLICK ME

``` Sonic Pi Boot Error Report ================== System Information ---------------- * Sonic Pi version: 3.3.1 * OS: Windows 10 Version 2009 GUI Log ------- **`C:\Users\g8tr1\.sonic-pi\log\gui.log`** [GUI] - [GUI] - [GUI] - [GUI] - Welcome to the Sonic Pi GUI [GUI] - =========================== [GUI] - [GUI] - {bf49e59c-2a9d-403b-93a3-3db5ea179385} [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 : 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: 13616 [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\g8tr1\.sonic-pi\log\server-errors.log`** Server Output ------------- **`C:\Users\g8tr1\.sonic-pi\log\server-output.log`** Sonic Pi server booting... The time is 2022-02-11 18:54:41 -0500 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 14024 to path C:/Users/g8tr1/AppData/Local/Temp/sonic-pi-pids/14024! undefined method `cmdline' for nil:NilClass Scsynth Output -------------- **`C:\Users\g8tr1\.sonic-pi\log\scsynth.log`** # Starting SuperCollider 2022-02-11 18:54:42 Device options: - MME : Microsoft Sound Mapper - Input (device #0 with 2 ins 0 outs) - MME : Microphone Array (Realtek High (device #1 with 2 ins 0 outs) - MME : Microphone (DroidCam Virtual Au (device #2 with 1 ins 0 outs) - MME : Microsoft Sound Mapper - Output (device #3 with 0 ins 2 outs) - MME : Speakers (Realtek High Definiti (device #4 with 0 ins 6 outs) - MME : HF237H (Intel(R) Display Audio) (device #5 with 0 ins 2 outs) - Windows DirectSound : Primary Sound Capture Driver (device #6 with 2 ins 0 outs) - Windows DirectSound : Microphone Array (Realtek High Definition Audio(SST)) (device #7 with 2 ins 0 outs) - Windows DirectSound : Microphone (DroidCam Virtual Audio) (device #8 with 1 ins 0 outs) - Windows DirectSound : Primary Sound Driver (device #9 with 0 ins 2 outs) - Windows DirectSound : Speakers (Realtek High Definition Audio(SST)) (device #10 with 0 ins 6 outs) - Windows DirectSound : HF237H (Intel(R) Display Audio) (device #11 with 0 ins 2 outs) - ASIO : ASIO4ALL v2 (device #12 with 4 ins 12 outs) - Windows WASAPI : HF237H (Intel(R) Display Audio) (device #13 with 0 ins 2 outs) - Windows WASAPI : Speakers (Realtek High Definition Audio(SST)) (device #14 with 0 ins 2 outs) - Windows WASAPI : Microphone Array (Realtek High Definition Audio(SST)) (device #15 with 2 ins 0 outs) - Windows WASAPI : Microphone (DroidCam Virtual Audio) (device #16 with 1 ins 0 outs) - Windows WDM-KS : Microphone Array (Realtek HD Audio Mic Array input) (device #17 with 2 ins 0 outs) - Windows WDM-KS : Speakers 1 (Realtek HD Audio output with SST) (device #18 with 0 ins 2 outs) - Windows WDM-KS : Speakers 2 (Realtek HD Audio output with SST) (device #19 with 0 ins 6 outs) - Windows WDM-KS : PC Speaker (Realtek HD Audio output with SST) (device #20 with 2 ins 0 outs) - Windows WDM-KS : Headphones 1 (Realtek HD Audio 2nd output with SST) (device #21 with 0 ins 2 outs) - Windows WDM-KS : Headphones 2 (Realtek HD Audio 2nd output with SST) (device #22 with 0 ins 6 outs) - Windows WDM-KS : PC Speaker (Realtek HD Audio 2nd output with SST) (device #23 with 2 ins 0 outs) - Windows WDM-KS : Headset Microphone (Realtek HD Audio Mic input) (device #24 with 2 ins 0 outs) - Windows WDM-KS : Output (Intel(R) Display Audio Output 2.1) (device #25 with 0 ins 2 outs) - Windows WDM-KS : MIDI (DroidCam Audio) (device #26 with 1 ins 0 outs) - Windows WDM-KS : Output (DroidCam Audio) (device #27 with 0 ins 1 outs) Requested devices: In: - (default) Out: - (default) Selecting default system input/output devices Booting with: In: MME : Microphone Array (Realtek High Out: MME : Speakers (Realtek High Definiti SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: 'Unanticipated host error' could not initialize audio. Process Log -------------- **`C:\Users\g8tr1\.sonic-pi\log\processes.log`** ask-clear.rb Clearing pids: [] No pids to clear :-) Started [13616] [-] "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/g8tr1/AppData/Local/Temp/sonic-pi-pids/13616 ERROR: Unable to write information for PID 14024 to path C:/Users/g8tr1/AppData/Local/Temp/sonic-pi-pids/14024! undefined method `cmdline' for nil:NilClass ```

and now I am stumped.

ethancrawford commented 2 years ago

@g8tr1522 - much has changed in Sonic Pi since 2018. (Editing scsynthexternal.rb is no longer the correct solution).

To tell Sonic Pi to use ASIO4ALL, you now edit a different configuration file.

Here is an example of the new file: https://github.com/sonic-pi-net/sonic-pi/blob/85c0a7e169e84fd23bbde05665e7a1f1ca8d8168/app/config/user-examples/audio-settings.toml

This is where Sonic Pi now gets any audio device customisations from.

You would make a copy of this file and put it in your C:\Users\[you]\.sonic-pi\config folder. Then, edit the following line: https://github.com/sonic-pi-net/sonic-pi/blob/85c0a7e169e84fd23bbde05665e7a1f1ca8d8168/app/config/user-examples/audio-settings.toml#L89

...to remove the comment hash, and insert a string that would match a search by name for the desired audio device - in your case, ASIO4ALL.

This should hopefully allow Sonic Pi to connect to your ASIO device.

Have a go, and let us know if you have any further problems 👍 (probably best to do so in a new issue though if you need to 🙂)

samaaron commented 2 years ago

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

g8tr1522 commented 2 years ago

holy crap, you remembered AND emailed me...you're a damn hero! I don't have time today, but hopefully I can get to it this weekend.

On Tue, Jul 19, 2022 at 3:47 PM Sam Aaron @.***> wrote:

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

— Reply to this email directly, view it on GitHub https://github.com/sonic-pi-net/sonic-pi/issues/1881#issuecomment-1189486335, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHO72ZYTTB4KILERIW3WLLVU4A5PANCNFSM4E26IX4Q . You are receiving this because you were mentioned.Message ID: @.***>

-- William Prophet @.***

samaaron commented 2 years ago

I'm keeping my fingers crossed that things work for you. If not, I still really want to figure out what's going wrong for your setup.

g8tr1522 commented 1 year ago

Just tried it out. Worked right away! No reboot required either!

Thanks again so much for reaching out! People like you make my hobbies so much more fun.

Hey, since I got your attention, lemme ask a quick question. Are there any future plans for user-made GUI capabilities kinda like SuperCollider has? That's what ultimately made me move on from Sonic Pi. I had big plans for a program that would spit out generative melodies with midi. But I yearned for a GUI I could use to control the whole thing easily without external midi controllers, remembering how it even worked, etc. I think it would be a welcome addition. Not to mention that GUI experience would be excellent practice for young students learning how to code. I'm sure there are other ways to accomplish what I was trying to do, but having all your answers in the 'tutorial bar' is a very convenient way to learn. Ju

On Wed, Jul 20, 2022 at 8:15 PM Sam Aaron @.***> wrote:

I'm keeping my fingers crossed that things work for you. If not, I still really want to figure out what's going wrong for your setup.

— Reply to this email directly, view it on GitHub https://github.com/sonic-pi-net/sonic-pi/issues/1881#issuecomment-1190894980, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHO722WXQU35OWKRC4XYLDVVCJBBANCNFSM4E26IX4Q . You are receiving this because you were mentioned.Message ID: @.***>

-- William Prophet @.***