Boot error, from fresh install

image

So i have a fresh install of sonic PI, and i’ve tried installing more than once, and doing multiple reboots.

Is there something I’m doing wrong? or some configuration that needs modified?

Sonic Pi Boot Error Report
==================


System Information
----------------

* Sonic Pi version: 3.3.1
* OS: Windows 10 Version 2009


GUI Log
-------

**`C:\Users\jyoung\.sonic-pi\log\gui.log`**

[GUI] -                            
[GUI] -                            
[GUI] -                            
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {b1035d8e-7d29-4a7b-84d7-0b8d7e31c8d9}
[GUI] - ui locale:  en-US
[GUI] - sys locale: en_US
[GUI] - translations available 
[GUI] - Discovering port numbers...
[GUI] - Port entry server-listen-to-gui : 51235 : 51235
[GUI] - Port entry gui-send-to-server : 51235 : 51235
[GUI] - Port entry gui-listen-to-server : 51236 : 51236
[GUI] - Port entry server-send-to-gui : 51236 : 51236
[GUI] - Port entry scsynth : 51237 : 51237
[GUI] - Port entry scsynth-send : 51237 : 51237
[GUI] - Port entry server-osc-cues : 4560 : 4560
[GUI] - Port entry erlang-router : 51238 : 51238
[GUI] - Port entry websocket : 51239 : 51239
[GUI] - Detecting port numbers...
[GUI] - GUI listen to server port 51236
[GUI] -    port: 51236 [OK]
[GUI] - Server listen to gui port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Server incoming OSC cues port 4560
[GUI] -    port: 4560 [OK]
[GUI] - Scsynth port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Server send to GUI port 51236
[GUI] -    port: 51236 [OK]
[GUI] - GUI send to server port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Scsynth send port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Erlang router port 51238
[GUI] -    port: 51238 [OK]
[GUI] - Websocket port 51239
[GUI] -    port: 51239 [OK]
[GUI] - All ports OK
[GUI] - hiding main window
[GUI] - initialising toolbar icons
[GUI] - setting up window structure
[GUI] - restoring scope states 
[GUI] - creating status bar
[GUI] - creating info panel
[GUI] - creating shortcuts
[GUI] - creating tool bar
[GUI] - initialising documentation window
[GUI] - starting UDP OSC Server on port [GUI] - launching Sonic Pi Runtime Server:51236...

[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 28844
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - Critical Error. Unable to connect to server..
[GUI] - UDP OSC Server no longer listening


Server Errors
-------------

**`C:\Users\jyoung\.sonic-pi\log\server-errors.log`**

Unable to open log file J:/.sonic-pi/log/debug.log
#<NoMethodError: undefined method `log' for SonicPi::Util:Module
Did you mean?  look>
Unable to open process log file J:/.sonic-pi/log/processes.log
C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1415:in `initialize': No such file or directory @ rb_sysopen - J:/.sonic-pi/config/README.md (Errno::ENOENT)
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1415:in `open'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1415:in `block in copy_file'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1414:in `open'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1414:in `copy_file'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:514:in `copy_file'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:433:in `block in cp'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1597:in `block in fu_each_src_dest'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1613:in `fu_each_src_dest0'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1595:in `fu_each_src_dest'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:432:in `cp'
	from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:99:in `block in <main>'
	from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:95:in `each'
	from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:95:in `<main>'


Server Output
-------------

**`C:\Users\jyoung\.sonic-pi\log\server-output.log`**
Sonic Pi server booting...
The time is 2022-06-24 14:25:56 -0400




Scsynth Output
--------------

**`C:\Users\jyoung\.sonic-pi\log\scsynth.log`**

Process Log
--------------

**`C:\Users\jyoung\.sonic-pi\log\processes.log`**

I also got this error. At a new computer and at my old one too.

I can use this on my Raspberry Pi, but not on my Win10

from my .sonic-pi\log\servers-errors.log

Unable to open log file J:/.sonic-pi/log/debug.log
#<NoMethodError: undefined method `log' for SonicPi::Util:Module
Did you mean?  look>
Unable to open process log file J:/.sonic-pi/log/processes.log
C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1415:in `initialize': No such file or directory @ rb_sysopen - J:/.sonic-pi/config/README.md (Errno::ENOENT)
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1415:in `open'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1415:in `block in copy_file'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1414:in `open'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1414:in `copy_file'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:514:in `copy_file'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:433:in `block in cp'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1597:in `block in fu_each_src_dest'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1613:in `fu_each_src_dest0'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:1595:in `fu_each_src_dest'
	from C:/Program Files/Sonic Pi/app/server/native/ruby/lib/ruby/3.0.0/fileutils.rb:432:in `cp'
	from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:99:in `block in <main>'
	from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:95:in `each'
	from C:/Program Files/Sonic Pi/app/gui/qt/build/Release/../../../../../app/server/ruby/bin/sonic-pi-server.rb:95:in `<main>'

why would it be trying to get to a J:\ drive directory?
i don’t have a J drive

Hi

  1. Check the rate of input and output of your audio card : they should be the same.

  2. No Bluetooth, try wired devices

Hope it helps

no dice on this…

i’ve been using my PI, but would be nice to have it working on laptop too

Hi @jyoung4242,

Sonic Pi asks the host where the “home directory” of the current user is to figure out where to store logs, configs, and the code in the buffers. For the majority of users, this just seems to work - however for a handful of Windows users - it seems to point to an obscure/unused drive letter such as J:\ in your case.

We honestly don’t know what causes this - it could potentially be a variety of different things - perhaps specific configs or ENV vars on your system interfering in a strange and unexpected way.

However, there is a simple solution and that is to create a new environment variable called SONIC_PI_HOME and set it to a folder you have write access to that you’d like Sonic Pi to store all its stuff. Once that is set, you should be able to start Sonic Pi just fine :slight_smile:

I will try it, and let you all know…
thanks for getting back to me

works like a champ, thank you very much

1 Like

That’s fab news! So glad you’re up and running :slight_smile:

I still have problems, my error has nothing to do with the J drive

Hi @Miniontoby - unfortunately we can’t help you fix your issue without access to your log files. The best thing to do is to create a GitHub issue and we can help over there: Issues · sonic-pi-net/sonic-pi · GitHub

I havent gotten any time to upload it yet… i will try to get it today

1 Like