Unable to boot Sonic Pi on MacBook Pro

[tomhannen]

Installed Sonic Pi. Copied to Applications folder. When I tried to open, it froze on the splash screen. Then an error:

GUI was unable to connect to the Ruby server

Using a 2018 Intel MacBook Pro running MacOS 11.6

Error log below:

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

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

* Sonic Pi version: 3.3.1
* OS: macOS 11.6

GUI Log
-------

**`/Users/tom.hannen/.sonic-pi/log/gui.log`**

[GUI] -
[GUI] -
[GUI] -
[GUI] - Welcome to the Sonic Pi GUI [GUI] - =========================== [GUI] -
[GUI] - {8de32620-7455-499d-941b-fcba56fac5fc} [GUI] - ui locale: en-GB [GUI] - sys locale: en_GB [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] - launching Sonic Pi Runtime Server: [GUI] - starting UDP OSC Server on port 51236... [GUI] - UDP OSC Server ready and listening [GUI] - Ruby server pid registered: 18079 [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
-------------

**`/Users/tom.hannen/.sonic-pi/log/server-errors.log`**

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

**`/Users/tom.hannen/.sonic-pi/log/server-output.log`**

Sonic Pi server booting... The time is 2021-11-09 12:07:19 +0000 Using primary protocol: udp Detecting port numbers... Listen port: 51235

• OK Scsynth port: 51237
• OK Scsynth send port: 51237
• OK OSC cues port: 4560
• OK Erlang port: 51238
• OK Websocket port: 4562
• OK Opening UDP Server to listen to GUI on port: 51235

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

**`/Users/tom.hannen/.sonic-pi/log/scsynth.log`**

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

**`/Users/tom.hannen/.sonic-pi/log/processes.log`**

ask-clear.rb

Clearing pids: ["18003"]

Clearing [18003] -- command -- removing /var/folders/t7/jzw6ss6d6v90q7w4rmxck7r80000gp/T/sonic-pi-pids/18003 -- politely killing 18003 -- killed 18003

Finished clearing pids

Started [18079] [-] [-] /var/folders/t7/jzw6ss6d6v90q7w4rmxck7r80000gp/T/sonic-pi-pids/18079

[samaaron]

We have completely overhauled the process with which we boot the system, and it would still be really great to know if this has somehow not resolved your situation.

Therefore, please feel free to re-open if this is still an issue with the recently released v4 of Sonic Pi - https://github.com/sonic-pi-net/sonic-pi/releases

[tomhannen]

It works!

Audio didn't output when I first loaded (I'm on an M1 MacBook Pro using a Tascam US 2x2 USB audio interface).

To get it working, I checked "Invert Stereo", "Force Mono" and "Enable Audio Inputs" in the preferences, and restarted the app. This solved the problem, but I'm not sure which of these actions fixed it.