Closed JoBilert closed 2 years ago
Same problem here:
Detailed Error Report:
[GUI] - shutting down any old audio servers... [GUI] - booting live coding server [GUI] - using default editor colours [GUI] - starting UDP OSC Server on port 4558... [GUI] - UDP OSC Server ready and listening [GUI] - waiting for server to connect... [GUI] - critical error! [GUI] - server connection established
Non-critical error: Could not load did_you_mean This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::system_error' what(): Invalid argument
Unfortunately without any way to reproduce this locally it's going to be hard for me to fix this.
Could you try this dev version to see if it reports the same issues?
I've got a copy of Windows 10 now so I'll try to debug this weekend as well
Great, thanks! However, there are many reports of it working flawlessly on Windows 10 - so I wonder what's different here...
Another option would be to work backwards through the releases to see if any of them work...
I just tried your dev version. It shows the splash screen, and after a while it goes into "The program is not responding". No crash message here...
I just installed version 2.8, this version starts without an error
Haha, that's so curious. v2.8
caused many issues on Windows - v2.9
fixed most of those issues. It's super weird that you're seeing an inverse of this behaviour!
Is there a way that I can start the software to put out a more detailed log?
You just need to check the contents of ~/.sonic-pi/log
although these logs are mostly reproduced in the error window.
here's a more detailed error log:
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
Failed to start server: Input/output error - TerminateProcess
C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:850:in block in kill' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in
each'
C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in kill' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:244:in
rescue in boot_and_wait'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:240:in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:325:in
boot_server_windows'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:169:in boot' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:in
initialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:in
initialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:in
init_studio'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:37:in initialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:in
new'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:in block (2 levels) in included' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in
new'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in `
Tried 2.10 dev. Important difference.. my firewall (ESET) now prompts me if i want to allow traffic from Sonic Pi. Sadly there is a crash after that.
Sonic Pi Boot Error Report
GUI log
Server Errors
Non-critical error: Could not load did_you_mean
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
Server Output
Scsynth Output
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed
2016-02-06 13:20 GMT+01:00 LukiLeu notifications@github.com:
here's a more detailed error log:
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::system_error' what(): Invalid argument Failed to start server: Input/output error - TerminateProcess C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:850:in block in kill' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in each' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in kill' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:244:inrescue in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:240:in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:325:in boot_server_windows' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:169:in boot' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:ininitialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:ininitialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:ininit_studio' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:37:in initialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:innew' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:in block (2 levels) in included' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in new' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in ` '
— Reply to this email directly or view it on GitHub https://github.com/samaaron/sonic-pi/issues/959#issuecomment-180749650.
2.8 works neither
2016-02-06 13:45 GMT+01:00 Bilert bilert@gmail.com:
Tried 2.10 dev. Important difference.. my firewall (ESET) now prompts me if i want to allow traffic from Sonic Pi. Sadly there is a crash after that.
Sonic Pi Boot Error Report
GUI log
Server Errors
Non-critical error: Could not load did_you_mean
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
Server Output
Scsynth Output
Starting SuperCollider 2016-02-06 13:43:01
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed
2016-02-06 13:20 GMT+01:00 LukiLeu notifications@github.com:
here's a more detailed error log:
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::system_error' what(): Invalid argument Failed to start server: Input/output error - TerminateProcess C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:850:in block in kill' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in each' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in kill' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:244:inrescue in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:240:in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:325:in boot_server_windows' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:169:in boot' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:ininitialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:ininitialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:ininit_studio' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:37:in initialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:innew' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:in block (2 levels) in included' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in new' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in ` '
— Reply to this email directly or view it on GitHub https://github.com/samaaron/sonic-pi/issues/959#issuecomment-180749650.
Still got no improvement tried 2.8 and 2.7.
2016-02-06 14:26 GMT+01:00 Bilert bilert@gmail.com:
2.8 works neither
2016-02-06 13:45 GMT+01:00 Bilert bilert@gmail.com:
Tried 2.10 dev. Important difference.. my firewall (ESET) now prompts me if i want to allow traffic from Sonic Pi. Sadly there is a crash after that.
Sonic Pi Boot Error Report
GUI log
Server Errors
Non-critical error: Could not load did_you_mean
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
Server Output
Scsynth Output
Starting SuperCollider 2016-02-06 13:43:01
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed
2016-02-06 13:20 GMT+01:00 LukiLeu notifications@github.com:
here's a more detailed error log:
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::system_error' what(): Invalid argument Failed to start server: Input/output error - TerminateProcess C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:850:in block in kill' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in each' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in kill' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:244:inrescue in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:240:in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:325:in boot_server_windows' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:169:in boot' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:ininitialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:ininitialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:ininit_studio' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:37:in initialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:innew' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:in block (2 levels) in included' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in new' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in ` '
— Reply to this email directly or view it on GitHub https://github.com/samaaron/sonic-pi/issues/959#issuecomment-180749650 .
Could you try the latest v2.10
pre-release to see if you still get the same error:
Still an error:
[GUI] - using default editor colours [GUI] - shutting down any old audio servers... [GUI] - starting UDP OSC Server on port 4558... [GUI] - UDP OSC Server ready and listening [GUI] - booting live coding server [GUI] - waiting for server to boot... ............................................................ [GUI] - Critical error! Could not boot server.
C:\Users\xx\log\server-errors.log
C:\Users\xx\log\server-output.log
Oh, shame. That path seems odd though. I expected it to be C:\Users\xx\.sonic-pi\log
Also, do you get the same detailed log issue as above?
server-errors.log:
Non-critical error: Could not load did_you_mean
Received Exception!
Normalerweise darf jede Socketadresse (Protokoll, Netzwerkadresse oder Anschluss) nur jeweils einmal verwendet werden. - bind(2) for "127.0.0.1" port 4557
["C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/osc/Failed to start server: Input/output error - TerminateProcess
C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:850:in block in kill' C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in
each'
C:/Program Files (x86)/Sonic Pi/app/server/native/windows/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in kill' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:244:in
rescue in boot_and_wait'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:240:in boot_and_wait' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:325:in
boot_server_windows'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:169:in boot' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:in
initialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:73:in
initialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:in new' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:79:in
init_studio'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:37:in initialize' C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:in
new'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:110:in block (2 levels) in included' C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in
new'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:105:in `
scsynth.log:
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed
@jweather have you any idea what may be causing scsynth
on this machine to create the exception:
Exception in World_New: boost::interprocess::intermodule_singleton initialisation failed
I figured out why this was failing for me. In my case a registry entry was empty and so the shared memory region could not be created. Please check
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Common AppData
Make sure that this points to a valid folder where you have write access.
@llloret is this potentially a solution to some of the problems we're facing on Windows?
Might be. I thought it had to do with the Windows registry not having information about the boot event (which was sort of fixed), but this might be indeed an issue (and it might be the reason why sometimes it still fails, even when the event is there).
It is worth checking next time someone reports the error.
We had the observation about the missing registry key already back then when this issue (complex) surfaced. Unfortunately it only solves a small part of the cases. Once the entry is made, the underlying issue can still occur.
@bagong that's useful - thanks for letting us know :-)
I'm still getting the same error though the registry key is there (only in a bit of a different location) and points to a writable folder.
I'm posting about the same problem that has a few different related threads. Maybe we could link them all up?
============================ Welcome to SuperCollider 3.9.1. For help press Ctrl-D. file "C:\Users\christophe\AppData\Local\SuperCollider\Help\scdoc_version" does not exist. SCDoc: Indexing help-files... SCDoc: Indexed 1338 documents in 1.37 seconds
Could you try booting a server. Launching SuperCollider doesn’t do this automatically.
Sorry, so I boot a server and I got the error message booting server 'localhost' on address: 127.0.0.1:57110 Exception in World_New: boost::interprocess::intermodule_singleton initialization failed RESULT = -1073740791
Having the same issue on Fedora Linux.
# Starting SuperCollider 2018-04-16 16:55:55 Exception in World_New: Permission denied
Started having this issue today on Windows 10 with SC 3.9.0. Uninstalled and installed latest version, SC 3.9.3: still having the issue. (Installed on a second computer, and everything works fine, but I would still like to resolve the problem on my main computer if possible.)
Entering s.boot results in the following:
booting server 'localhost' on address: 127.0.0.1:57110 Exception in World_New: boost::interprocess::intermodule_singleton initialization failed RESULT = -1073740791
To debug more om Windows, the process monitor tool from Microsoft is very useful: https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
Capture file read/write and registry access events whilst reproducing the issue.
SuperCollider uses Boost for inter-process communication (IPC). Boost IPC creates a set of files under a temp directory. Boost appends the node's uptime to that directory's name, apparently to make it unique. The Windows implementation of the uptime lookup is brittle, it seems to search for events of type '6005' (logon) in the Windows event log. This apparently fails many different ways, possibly when the event log becomes too large. Here is a workaround that worked on Windows 10:
System Information Sonic Pi version: 3.1.0 OS: Windows 7 GUI Log C:\Users\Administrator.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: 4540 [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\Administrator.sonic-pi\log\server-errors.log
Server Output C:\Users\Administrator.sonic-pi\log\server-output.log
Sonic Pi server booting... Using protocol: udp Detecting port numbers... Send port: 4558 Listen port: 4557
Scsynth Output C:\Users\Administrator.sonic-pi\log\scsynth.log
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed
Process Log C:\Users\Administrator.sonic-pi\log\processes.log
No pids store found here: C:/Users/ADMINI~1/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids Exiting Creating pids store: C:/Users/ADMINI~1/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids Started [4540] [-] "C:\SonicPiPortable\App\Sonic Pi\app\gui\qt\release........\app\server\native\ruby\bin\ruby.exe" --enable-frozen-string-literal -E utf-8 "C:\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 [-] C:/Users/ADMINI~1/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids/4540
Is win7 unable to install this software, or because of my computer hardware is lack of
Could anyone still suffering from BOOST related issues such as those discussed here try the latest SuperCollider release 3.10.3-RC*
and see if the issue is still present there?
The test is to be able to boot the audio server or not directly from SuperCollider (not via Sonic Pi)
/Users/quintendewilde/.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 [Not Available]
[GUI] - Server incoming OSC cues port 4559
[GUI] - port: 4559 [Not Available]
[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: 65788
[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.
[GUI] - stopping UDP OSC Server...
/Users/quintendewilde/.sonic-pi/log/server-errors.log
/Users/quintendewilde/.sonic-pi/log/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?
/Users/quintendewilde/.sonic-pi/log/scsynth.log
/Users/quintendewilde/.sonic-pi/log/processes.log
Clearing pids: ["65747"]
Clearing [65747]
-- command /Applications/Sonic Pi.app/Contents/MacOS/../../app/server/native/ruby/bin/ruby --enable-frozen-string-literal -E utf-8 /Applications/Sonic Pi.app/Contents/MacOS/../../app/server/ruby/bin/sonic-pi-server.rb -u 4557 4558 4556 4556 4559 4560 4561 4562
-- removing /var/folders/b9/54q72k_j04b970szr542strr0000gn/T/sonic-pi-pids/65747
-- unable to get ProcTable info for: 65747
-- process: 65747 not running
Finished clearing pids
Started [65788] [-] /Applications/Sonic Pi.app/Contents/MacOS/../../app/server/native/ruby/bin/ruby --enable-frozen-string-literal -E utf-8 /Applications/Sonic Pi.app/Contents/MacOS/../../app/server/ruby/bin/sonic-pi-server.rb -u 4557 4558 4556 4556 4559 4560 4561 4562 [-] /var/folders/b9/54q72k_j04b970szr542strr0000gn/T/sonic-pi-pids/65788
`
I opened Sonic Pi Portable on that laptop before, and it worked. Now, less than 24h after, this happens :/
C:\Users\Michal\.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: 1684
[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
C:\Users\Michal\.sonic-pi\log\server-errors.log
C:\Users\Michal\.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 [7136] [-] "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/Michal/AppData/Local/Temp/sonic-pi-pids/7136
C:\Users\Michal\.sonic-pi\log\scsynth.log
# Starting SuperCollider 2019-10-25 17:31:36
Device options:
- MME : Mapowanie dźwięku Microsoft - Input (device #0 with 2 ins 0 outs)
- MME : Zestaw mikrofonów (Realtek High (device #1 with 2 ins 0 outs)
- MME : Mapowanie dźwięku Microsoft - Output (device #2 with 0 ins 2 outs)
- MME : Głośniki / Słuchawki (Realtek H (device #3 with 0 ins 2 outs)
- Windows DirectSound : Podstawowy sterownik przechwytywania dźwięku (device #4 with 2 ins 0 outs)
- Windows DirectSound : Zestaw mikrofonów (Realtek High Definition Audio) (device #5 with 2 ins 0 outs)
- Windows DirectSound : Podstawowy sterownik dźwięku (device #6 with 0 ins 2 outs)
- Windows DirectSound : Głośniki / Słuchawki (Realtek High Definition Audio) (device #7 with 0 ins 2 outs)
- Windows WASAPI : Głośniki / Słuchawki (Realtek High Definition Audio) (device #8 with 0 ins 2 outs)
- Windows WASAPI : Zestaw mikrofonów (Realtek High Definition Audio) (device #9 with 2 ins 0 outs)
- Windows WDM-KS : Speakers (Realtek HD Audio output) (device #10 with 0 ins 2 outs)
- Windows WDM-KS : Gniazdo mikrofonu (Realtek HD Audio Front Mic input) (device #11 with 2 ins 0 outs)
- Windows WDM-KS : Zestaw mikrofonów (Realtek HD Audio Mic Array input) (device #12 with 2 ins 0 outs)
- Windows WDM-KS : Miks stereo (Realtek HD Audio Stereo input) (device #13 with 2 ins 0 outs)
Booting with:
In: MME : Zestaw mikrofonów (Realtek High
Out: MME : Głośniki / Słuchawki (Realtek H
C:\Users\Michal\.sonic-pi\log\processes.log
Clearing pids: []
No pids to clear :-)
Started [1684] [-] "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/Michal/AppData/Local/Temp/sonic-pi-pids/1684
Started [7136] [-] "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/Michal/AppData/Local/Temp/sonic-pi-pids/7136
`
Okay... I found temporary solution of my problem. I need to run Windows with pendrive in my computer, then run sonic pi, remove pendrive and run it again
??? How odd! Do you happen to have any insight into why this might be the case?
Closing this now due to inactivity. Please feel free to reopen should there still be an issue.
Hi I am using Sonic Pi 2.9on Windows 10 64-bit, well actually would like to use it, but whenever I start the program I get a "Critical Server Error":
Server Errors
Non-critical error: Could not load did_you_mean
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::system_error' what(): Invalid argument
Then the program terminates.
I never see scsynth starting up.. and Ruby terminates when sonic-pi terminates. What can i do?