Win10: Sonic Pi does not start but only after displays the splash screen

Support, Help & Resources
1

When clicking on the splash screen it disapperas, but Sonic Pi does not start.

The suspected message is

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

Please help.

Here’s my logs:

scsynth.log

Starting SuperCollider 2019-04-24 14:00:35

Device options:

  • MME : Microsoft Soundmapper - Input (device #0 with 2 ins 0 outs)
  • MME : Microphone (Realtek High Defini (device #1 with 2 ins 0 outs)
  • MME : Microsoft Soundmapper - Output (device #2 with 0 ins 2 outs)
  • MME : VX248 (Intel(R) Display-Audio) (device #3 with 0 ins 2 outs)
  • Windows DirectSound : Primärer Soundaufnahmetreiber (device #4 with 2 ins 0 outs)
  • Windows DirectSound : Microphone (Realtek High Definition Audio) (device #5 with 2 ins 0 outs)
  • Windows DirectSound : Primärer Soundtreiber (device #6 with 0 ins 2 outs)
  • Windows DirectSound : VX248 (Intel(R) Display-Audio) (device #7 with 0 ins 2 outs)
  • Windows WASAPI : VX248 (Intel(R) Display-Audio) (device #8 with 0 ins 2 outs)
  • Windows WASAPI : Microphone (Realtek High Definition Audio) (device #9 with 2 ins 0 outs)
  • Windows WDM-KS : Mikrofon (Realtek HD Audio Mic input) (device #10 with 2 ins 0 outs)
  • Windows WDM-KS : Stereomix (Realtek HD Audio Stereo input) (device #11 with 2 ins 0 outs)
  • Windows WDM-KS : Headphones (Realtek HD Audio 2nd output) (device #12 with 0 ins 2 outs)
  • Windows WDM-KS : Speakers (Realtek HD Audio output) (device #13 with 0 ins 2 outs)
  • Windows WDM-KS : Output (Intel(R) Display-Audio - Ausgang 1.1) (device #14 with 0 ins 2 outs)
  • Windows WDM-KS : Lautsprecher () (device #15 with 0 ins 2 outs)

Booting with:
In: MME : Microphone (Realtek High Defini
Out: MME : VX248 (Intel(R) Display-Audio)
SC_PortAudioDriver: PortAudio failed at Pa_OpenStream with error: ‘Unanticipated host error’
could not initialize audio.

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: 17212
[GUI] - waiting for Sonic Pi Server to boot…
…
[GUI] - Critical error! Could not boot Sonic Pi Server.

1 Like
2

Apologies, this appears to be an issue with SuperCollider (the underlying audio synthesis engine) running on your version of Windows. We see this occasionally and currently there’s nothing we can do to fix it. Hopefully the upcoming release of SuperCollider will help with things.

So sorry there’s not much more I can do other than to ask you to raise your issue with the SuperCollider issue tracker: https://github.com/supercollider/supercollider/issues