-
-
Notifications
You must be signed in to change notification settings - Fork 923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonic Pi can't open on Windows 10. #1820
Comments
Sorry you’re having issues. Did the error window contain the error messages that you could paste into his conversation? |
I seem to experience similar problem on Win 10 Pro. I installed 3.1.0 (no previos install, tried both the portable version and the MSI-install). Sonic Pi Boot Error ReportSystem Information
GUI Log
Server Errors
Server Output
Scsynth Output
Process Log
|
@mats42 - for some reason, SuperCollider doesn't seem to be able to talk back to Sonic Pi during boot on your machine. Do you have any security software that might be running and blocking UDP communications between the SuperCollider process and Sonic Pi on port 4556? |
Same phenomenon here with Windows 10 Home (not Win 8). No special security software apart from Avira Free Antivirus. Also, I was able to successfully launch it yesterday. Anything I can do to help with diagnosis/debugging? Sonic Pi Boot Error ReportSystem Information
GUI Log
Server Errors
Server Output
Scsynth Output
Process Log
|
@mrolappe if you temporarily disable your antivirus software does that allow Sonic Pi to boot? |
@samaaron unfortunately not, even if temporarily disabling the firewall. But I rebooted twice and then SonicPi successfully launched after each reboot. Before trying to launch SonicPi the first time today the computer had been in energy saving mode. Maybe it was related to that. Thanks for your prompt response. Let me know if I can help with anything. |
Thanks for letting me know. I'm a bit lost as to how to continue debugging this. From the logs it looks as if SuperCollider and Sonic Pi are unable to talk. However, the fact that it works sometimes and not others makes me suspect that there might be a weird race condition somewhere in the code. Although, if this is the case, I'm surprised that more people haven't reported this issue and also curious to know why it only seems to affect Windows machines... |
Is there an easy means of checking SuperCollider reachability, like some script client to talking to SC? If the launch problem shows up again I could execute that script to see if the reachability is the problem. |
Reachability in this case is just sending it OSC messages to port 4556. In the logs, you can see that Sonic Pi is repeatedly sending the One option would be to implement a simple OSC piggy back process which bi-directionally forwards OSC messages so you can see whether or not SuperCollider is sending/receiving the message. |
As I lack the Ruby and OSC experience I don't know how to go about it. It's a good occasion to learn about it, though. ;-) |
If you were to try this, you wouldn't need to implement it in Ruby - any language that has an OSC library will do. Alternatively something like Wireshark might work too. |
Thanks, I will take a look at OSC resources/docs. |
Trying to launch SonicPi today after waking the computer from energy saving mode the error popped up again. Unfortunately, trying to build SonicPi following the instructions for building on Windows failed for me at the gem installation step. Something about ffi.h header file not found. |
There should be no need to rebuild Sonic Pi - the OSC router I was describing would be an entirely separate system. You would just need to configure Sonic Pi to send OSC messages to your OSC router and then your OSC router would send messages to SuperCollider and the same for returning packets :-) |
I know, I just want(ed) to be able to debug Sonic Pi OSC communication code if need be. Let's see what I can come up with regarding that OSC routing proxy. :-) |
If you're only changing Ruby code, then you should just be able to do that directly to the app's source files and either hit |
Good to know, thanks for the hint! 👍 |
Sorry for not being able to investigate on my side until now :-) My non-working setup is a desktop computer with latest Windows 10 version: I installed SuperCollider separately to check if that work but that also fails. The SC IDE starts up and when booting the server, its seems to be ok, responding with:
but when I try to get it to play something, like: It fails with:
even though the scsynth processs is running. I also tried with a super simple UDP client/server in nodejs to send commands to scsynth's port but get no response back. (Hard to tell why since its UDP). Sending UDP messages from one nodejs client to another nodejs server works well as expected (ie Windows does not seem to eat up UDP messages on localhost). I suppose this should be a bug report to SuperCollider, haven't found any matching issue there. |
@mats42 - in SuperCollider you need to manually boot a server. Could you try that? The menu is Server -> Boot Server :-) |
As for SuperCollider I did boot the server manually and it did not output any error. However it's not really ok, the last thing it prints after booting is: "SuperCollider 3 server ready." |
After updating my laptop to Windows latest "Fall Creators update" (1709) Sonic-Pi and SuperCollider still works well! So windows version could probably be ruled out. On the desktop I completely removed Avira and a couple of other suspects but still, neither Sonic-Pi nor SuperCollider works, same as before. I also tried the latest dev-build of SuperCollider but still not working. scsynth.exe seems to hang during boot. |
I was having the same problem with both Sonic Pi and SuperCollider. My initial thoughts were also that something was blocking communication with the server. It was, however, a problem with the audio device. My audio devices were listed with several device options (MME, DirectSound, ASIO, WDM-KS) and SuperCollider was defaulting to MME. Specifying the correct device option (ASIO for me) solved the problem. In the SuperCollider IDE you can test this with s.options.device_("Your device name"); and then try booting the server. In Sonic Pi, find scsynthexternal.rb and add "-H", "Your device name" to the boot and wait statement in boot_server_windows. |
"Sonic Pi Boot Error ReportSystem Information
GUI Log
Server Errors
Server Output
Scsynth Output
Process Log
" |
We have completely overhauled the building and booting systems in the recently released https://github.com/sonic-pi-net/sonic-pi/releases Please give that a try and feel free to create a new issue if you're still having problems. |
When I opened Sonic Pi, this message sent. "Critical error! - Could not boot Sonic Pi Server." I tried to open this some times, but this didn't open at all. I'm very sorry when you are so busy, but please enable to operate Sonic Pi normally.
The text was updated successfully, but these errors were encountered: