Closed bobhigham closed 6 years ago
samaaron
commented
9 years ago Hi there,
that's weird - your log file suggests that Ruby server is talking to SuperCollider just fine - yet you don't seem to get a connection between the GUI and the Ruby server.
Could you let us know the contents of the other log files in ~/.sonic-pi/log
bobhigham
commented
9 years ago Sam,
the output log is as follows:
*\ ERROR: open directory failed 'C:\Users\Bob\AppData\Local\SuperCollider\synthdefs'
Device options:
Booting with: In: MME : Microphone (Realtek High Defini Out: MME : Speakers (Realtek High Definiti Sample rate: 44100.000 Latency (in/out): 0.013 / 0.091 sec SC_AudioDriver: sample rate = 44100.000000, driver's block size = 64 SuperCollider 3 server ready. exception in GrafDef_Load: UGen 'Decimator' not installed. while reading file 'C:/Program Files (x86)/Sonic Pi/etc/synthdefs\sonic-pi-fx_bitcrusher.scsyndef' exception in GrafDef_Load: UGen 'Decimator' not installed. while reading file 'C:/Program Files (x86)/Sonic Pi/etc/synthdefs\sonic-pi-fx_replace_bitcrusher.scsyndef' An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) An existing connection was forcibly closed by the remote host. - recvfrom(2) saving: workspace_two.spi saving: workspace_three.spi saving: workspace_four.spi saving: workspace_five.spi saving: workspace_six.spi saving: workspace_seven.spi saving: workspace_eight.spi
The stdout log is as follows but at the time of failure I think that the line OSC Stopped and beyond had not been logged.......
Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... Waiting for server... OSC Stopped, releasing socket saving workspaces Asking server process to exit... Exiting...
...........There are now 2 additional lines to the debug log as follows..........
[2015-01-17 18:06:49] Exiting - shutting down scsynth server... [2015-01-17 18:06:49] Sending /quit command to server
.......and the error log is empty.
There is no directory "SuperCollider" directory in the path specified above.
Bob.
bobhigham
commented
9 years ago Sam,
not sure if this will be of any help and may be a complete red herring, but in trying to reproduce the failure I note the following.....
Shutting down sonic in a controlled way, ie. stop playing before closing the window does not result in restart failures. Sonic starts up quickly and correctly with all the workspaces etc etc.
Closing the window whilst playing (get lucky) leaves sonic running and any attempt to restart results in various error messages. I noticed that whilst in this state, task manager shows the process scsynth.exe is still running and using resources.
Killing the process scsynth.exe in task manager allows Sonic Pi to restart successfully and recover the workspaces.
Bob.
samaaron
commented
6 years ago Would it be possible to try v3.1 on Windows and see if this problem has been resolved for you?
If not, please feel free to re-open this issue.
Error message is:
"failed to start server".
STDOUT is repeatedly "waiting for server"
Debug log is:
[2015-01-17 17:50:21] booting server... [2015-01-17 17:50:21] [2015-01-17 17:50:21] [2015-01-17 17:50:21] Booting Sonic Pi [2015-01-17 17:50:21] ---------------- [2015-01-17 17:50:21] [2015-01-17 17:50:21] Booting on Windows [2015-01-17 17:50:21]
[2015-01-17 17:50:21] Starting the SuperCollider server... [2015-01-17 17:50:31] SRV info - Initialising comms... #Queue:0x2fbee70 [2015-01-17 17:50:31] SRV info - Clearing scsynth [2015-01-17 17:50:31] SRV grp f 00000 - Clear 0 [2015-01-17 17:50:31] OSC ~ /clearSched [] [2015-01-17 17:50:31] SRV info - Requesting notifications [2015-01-17 17:50:31] SRV info - Loading synthdefs from path: C:/Program Files (x86)/Sonic Pi/etc/synthdefs [2015-01-17 17:50:31] OSC ~ /g_freeAll [0] [2015-01-17 17:50:31] OSC ~ /notify [1] [2015-01-17 17:50:31] OSC ~ /d_loadDir ["C:/Program Files (x86)/Sonic Pi/etc/synthdefs"] [2015-01-17 17:50:31] incoming: /done, ["/notify", 0] [2015-01-17 17:50:31] OSC ~ /sync [1] [2015-01-17 17:50:33] incoming: /done, ["/d_loadDir"] [2015-01-17 17:50:33] incoming: /synced, [1] [2015-01-17 17:50:33] SRV info - Clearing scsynth [2015-01-17 17:50:33] SRV grp f 00000 - Clear 0 [2015-01-17 17:50:33] OSC ~ /clearSched [] [2015-01-17 17:50:33] SRV grp n 00002 - Create [STUDIO-MIXER:2] head 0 [2015-01-17 17:50:33] OSC ~ /g_freeAll [0] [2015-01-17 17:50:33] OSC ~ /g_new [2, 0, 0] [2015-01-17 17:50:33] incoming: /n_go, [2, 0, -1, -1, 1, -1, -1] [2015-01-17 17:50:33] SRV grp n 00003 - Create [STUDIO-FX:3] before [STUDIO-MIXER:2] [2015-01-17 17:50:33] OSC ~ /g_new [3, 2, 2] [2015-01-17 17:50:33] incoming: /n_go, [3, 0, -1, 2, 1, -1, -1] [2015-01-17 17:50:33] SRV grp n 00004 - Create [STUDIO-SYNTHS:4] before [STUDIO-FX:3] [2015-01-17 17:50:33] OSC ~ /g_new [4, 2, 3] [2015-01-17 17:50:33] incoming: /n_go, [4, 0, -1, 3, 1, -1, -1] [2015-01-17 17:50:33] SRV grp n 00005 - Create [STUDIO-RECORDING:5] after [STUDIO-MIXER:2] [2015-01-17 17:50:33] OSC ~ /g_new [5, 3, 2] [2015-01-17 17:50:33] incoming: /n_go, [5, 0, 2, -1, 1, -1, -1] [2015-01-17 17:50:33] SRV nde t 00006 - Trigger sonic-pi-mixer:6 head [STUDIO-MIXER:2] [2015-01-17 17:50:33] BDL -1.00000 ~ [-1:1421517033] /s_new ["sonic-pi-mixer", 6, 0, 2, "in_bus", 10] [2015-01-17 17:50:33] incoming: /n_go, [6, 2, -1, -1, 0]