Sonic pi and windows 10 issues

Hello

Sonic pi ceased to work somewhere in June following a windows 10 update.

Did anybody find a workaround solution ?

Thanks

Hi there,

Sonic Pi has been working fine for me on Windows 10 despite installing all the recent updates. Could it be possible to let us know what issue you’re seeing? One thing that would really help is to share the contents of the log files in ~/.sonic-pi/log (where ~ means the location of your ‘home’ directory on your Windows machine).

Hi Samaaron

I appreciate your fast reaction

The msi-installed version hanged up , so i give a try to the portable version

here is a list /dump of log files: (sorted by alphabetic order of file names
debug.log is empty
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: 15768
[GUI] - waiting for Sonic Pi Server to boot…


osc_cues.log is empty

process.log:


No pids store found here: F:/TEMP/SonicPiPortableTemp/sonic-pi-pids
Exiting
Creating pids store: F:/TEMP/SonicPiPortableTemp/sonic-pi-pids
Started [15768] [-] “F:\Program Files (x86)\Nouveau dossier\SonicPiPortable\App\Sonic Pi\app\gui\qt\release…\app\server\native\ruby\bin\ruby.exe” --enable-frozen-string-literal -E utf-8 “F:\Program Files (x86)\Nouveau dossier\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 [-] F:/TEMP/SonicPiPortableTemp/sonic-pi-pids/15768
Started [14188] [-] “F:\Program Files (x86)\Nouveau dossier\SonicPiPortable\App\Sonic Pi\app\server\native\scsynth.exe” -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U “F:/Program Files (x86)/Nouveau dossier/SonicPiPortable/App/Sonic Pi/app/server/native/plugins/” -b 4096 -B 127.0.0.1 [-] F:/TEMP/SonicPiPortableTemp/sonic-pi-pids/14188

Clearing pids: [“14188”, “15768”]

Clearing [14188]
– command “F:\Program Files (x86)\Nouveau dossier\SonicPiPortable\App\Sonic Pi\app\server\native\scsynth.exe” -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U “F:/Program Files (x86)/Nouveau dossier/SonicPiPortable/App/Sonic Pi/app/server/native/plugins/” -b 4096 -B 127.0.0.1
– removing F:/TEMP/SonicPiPortableTemp/sonic-pi-pids/14188
– unable to get ProcTable info for: 14188
– process: 14188 not running

Clearing [15768]
– command “F:\Program Files (x86)\Nouveau dossier\SonicPiPortable\App\Sonic Pi\app\gui\qt\release…\app\server\native\ruby\bin\ruby.exe” --enable-frozen-string-literal -E utf-8 “F:\Program Files (x86)\Nouveau dossier\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
– removing F:/TEMP/SonicPiPortableTemp/sonic-pi-pids/15768
– force killing 15768
– killed 15768

Finished clearing pids


scsynth.log : (i think the issue is here?)


Starting SuperCollider 2019-08-24 16:40:17

Device options:

  • MME : Mappeur de sons Microsoft - Input (device #0 with 2 ins 0 outs)
  • MME : Ligne (XMOS XS1-L1 (ST)) (device #1 with 2 ins 0 outs)
  • MME : Microphone (ASUS Xonar Essence (device #2 with 2 ins 0 outs)
  • MME : Entrée ligne (ASUS Xonar Essenc (device #3 with 2 ins 0 outs)
  • MME : Aux (ASUS Xonar Essence STX Aud (device #4 with 2 ins 0 outs)
  • MME : Ligne (WsAudio_Device) (device #5 with 2 ins 0 outs)
  • MME : Mappeur de sons Microsoft - Output (device #6 with 0 ins 2 outs)
  • MME : Haut-parleurs (XMOS XS1-L1 (ST) (device #7 with 0 ins 2 outs)
  • MME : Haut-parleurs (ASUS Xonar Essen (device #8 with 0 ins 8 outs)
  • MME : S/PDIF Pass-through Device (ASU (device #9 with 0 ins 8 outs)
  • Windows DirectSound : Pilote de capture audio principal (device #10 with 2 ins 0 outs)
  • Windows DirectSound : Ligne (XMOS XS1-L1 (ST)) (device #11 with 2 ins 0 outs)
  • Windows DirectSound : Microphone (ASUS Xonar Essence STX Audio Device) (device #12 with 2 ins 0 outs)
  • Windows DirectSound : Entrée ligne (ASUS Xonar Essence STX Audio Device) (device #13 with 2 ins 0 outs)
  • Windows DirectSound : Aux (ASUS Xonar Essence STX Audio Device) (device #14 with 2 ins 0 outs)
  • Windows DirectSound : Ligne (WsAudio_Device) (device #15 with 2 ins 0 outs)
  • Windows DirectSound : Périphérique audio principal (device #16 with 0 ins 2 outs)
  • Windows DirectSound : Haut-parleurs (XMOS XS1-L1 (ST)) (device #17 with 0 ins 2 outs)
  • Windows DirectSound : Haut-parleurs (ASUS Xonar Essence STX Audio Device) (device #18 with 0 ins 8 outs)
  • Windows DirectSound : S/PDIF Pass-through Device (ASUS Xonar Essence STX Audio Device) (device #19 with 0 ins 8 outs)
  • ASIO : XMOS USB Audio 2.0 ST 2023 (device #20 with 2 ins 2 outs)
  • Windows WASAPI : Haut-parleurs (ASUS Xonar Essence STX Audio Device) (device #21 with 0 ins 2 outs)
  • Windows WASAPI : S/PDIF Pass-through Device (ASUS Xonar Essence STX Audio Device) (device #22 with 0 ins 2 outs)
  • Windows WASAPI : Haut-parleurs (XMOS XS1-L1 (ST)) (device #23 with 0 ins 2 outs)
  • Windows WASAPI : Microphone (ASUS Xonar Essence STX Audio Device) (device #24 with 2 ins 0 outs)
  • Windows WASAPI : Entrée ligne (ASUS Xonar Essence STX Audio Device) (device #25 with 2 ins 0 outs)
  • Windows WASAPI : Aux (ASUS Xonar Essence STX Audio Device) (device #26 with 2 ins 0 outs)
  • Windows WASAPI : Ligne (XMOS XS1-L1 (ST)) (device #27 with 2 ins 0 outs)
  • Windows WASAPI : Ligne (WsAudio_Device) (device #28 with 2 ins 0 outs)
  • Windows WDM-KS : Input (ASUS Xonar Essence STX Digital) (device #29 with 2 ins 0 outs)
  • Windows WDM-KS : SPDIF Out (ASUS Xonar Essence STX Digital) (device #30 with 0 ins 8 outs)
  • Windows WDM-KS : Wave (ASUS Xonar Essence STX Audio Wave In) (device #31 with 2 ins 0 outs)
  • Windows WDM-KS : Input (ASUS Xonar Essence STX Audio) (device #32 with 2 ins 0 outs)
  • Windows WDM-KS : Entrée ligne (ASUS Xonar Essence STX Audio) (device #33 with 2 ins 0 outs)
  • Windows WDM-KS : Aux (ASUS Xonar Essence STX Audio) (device #34 with 2 ins 0 outs)
  • Windows WDM-KS : Microphone (ASUS Xonar Essence STX Audio) (device #35 with 2 ins 0 outs)
  • Windows WDM-KS : Speakers (ASUS Xonar Essence STX Audio) (device #36 with 0 ins 8 outs)
  • Windows WDM-KS : Haut-parleurs (ATOLL Audio 2.0 Output) (device #37 with 0 ins 2 outs)
  • Windows WDM-KS : Ligne (ATOLL Audio 2.0 Input) (device #38 with 2 ins 0 outs)
  • Windows WDM-KS : Mixage stéréo (Realtek HD Audio Stereo input) (device #39 with 2 ins 0 outs)
  • Windows WDM-KS : Microphone (Realtek HD Audio Mic input) (device #40 with 2 ins 0 outs)
  • Windows WDM-KS : SPDIF Out (Realtek HDA SPDIF Out) (device #41 with 0 ins 2 outs)
  • Windows WDM-KS : Entrée ligne (Realtek HD Audio Line input) (device #42 with 2 ins 0 outs)
  • Windows WDM-KS : Speakers (Realtek HD Audio output) (device #43 with 0 ins 8 outs)
  • Windows WDM-KS : Output (NVIDIA High Definition Audio) (device #44 with 0 ins 2 outs)
  • Windows WDM-KS : MIDI (WsAudio_Device) (device #45 with 2 ins 0 outs)
  • Windows WDM-KS : Speakers (WsAudio_Device) (device #46 with 0 ins 2 outs)

Booting with:
In: MME : Ligne (XMOS XS1-L1 (ST))
Out: MME : Haut-parleurs (XMOS XS1-L1 (ST)
SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: ‘Unanticipated host error’
could not initialize audio.


servers-error.log :


AsioDrv::: CAsioDrv()…
AsioDrv::: InitWdmDrv()…


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 [14188] [-] “F:\Program Files (x86)\Nouveau dossier\SonicPiPortable\App\Sonic Pi\app\server\native\scsynth.exe” -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U “F:/Program Files (x86)/Nouveau dossier/SonicPiPortable/App/Sonic Pi/app/server/native/plugins/” -b 4096 -B 127.0.0.1 [-] F:/TEMP/SonicPiPortableTemp/sonic-pi-pids/14188

Clearing pids: [“14188”, “15768”]

Clearing [14188]
– command “F:\Program Files (x86)\Nouveau dossier\SonicPiPortable\App\Sonic Pi\app\server\native\scsynth.exe” -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U “F:/Program Files (x86)/Nouveau dossier/SonicPiPortable/App/Sonic Pi/app/server/native/plugins/” -b 4096 -B 127.0.0.1
– removing F:/TEMP/SonicPiPortableTemp/sonic-pi-pids/14188
– unable to get ProcTable info for: 14188
– process: 14188 not running

Clearing [15768]
– command “F:\Program Files (x86)\Nouveau dossier\SonicPiPortable\App\Sonic Pi\app\gui\qt\release…\app\server\native\ruby\bin\ruby.exe” --enable-frozen-string-literal -E utf-8 “F:\Program Files (x86)\Nouveau dossier\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
– removing F:/TEMP/SonicPiPortableTemp/sonic-pi-pids/15768
– force killing 15768
– killed 15768

Finished clearing pids


et voilà… (en français dans le texte) :slight_smile:

thanks for your time

Hi there,

yes, it certainly does look like a SuperCollider error. Unfortunately there’s not much I can do other than point you at their issues page to share the issue with them directly:

One thing you could do is try their latest beta release (3.10.3-rc1) and see if you can boot the server there:

If that works, then things should be fixed with the next release of Sonic Pi which I am planning to ship with this latest version of SuperCollider.

You could also try to change the default audio input and output settings in Windows to a different sound card and then try booting Sonic Pi.

Ok, i 'll try

I have installed the RC1 one of SC, but do I have to kill the older version of SC? I cannot locate it, anyway

SuperCollider is a totally separate and independent app when you install it yourself. You need to start it like a normal app (from the start menu or the shortcut). The version of SuperCollider included in Sonic Pi is bundled with Sonic Pi itself and therefore totally independent and will not collide :slight_smile: