Solutions for Common Issues
Here is a list of some solutions to a few common problems.
It seems like some of the ports that Sonic Pi needs are being used by other processes/programs. This could mean that processes relating to Sonic Pi is open, or other programs are using those ports.
The ports that Sonic Pi uses are ports 4556 to 4562:
- 4556 - Scsynth port
- 4556 - Scsynth send port
- 4557 - Server OSC listen port
- 4557 - GUI OSC out port
- 4558 - Server OSC out port
- 4558 - GUI OSC listen port
- 4559 - Server incoming OSC cues port
- 4560 - Erlang router port
- 4561 - OSC MIDI out port
- 4562 - OSC MIDI in port
Firstly, you can try to close Sonic Pi related processes:
Note: Be very careful what processes you close, make sure you don’t close any processes needed for your system to run.
On Raspbian, macOS and Linux, try opening the System Monitor... On Windows, try opening the Task Manager (press Win+r, type 'taskmgr', and press enter)...
and try closing the following processes:
- beam.smp
- Erlang
- Ruby interpreter
- Sonic Pi
- Sonic Pi Portable Launcher
- Supercollider
- scsynth
Or you can see what processes are using the ports and close those processes:
Note: Be very careful what processes you close, make sure you don’t close any processes needed for your system to run
On Raspbian, macOS or Linux: To find the processes that are using the ports, open the Terminal and type lsof -n -i:4556,4557,4558,4559,4560,4561,4562. Check what those processes are (make sure that they aren’t critical to the system), then if it’s safe to do so, you can stop those processes by typing kill [Process ID].
On Windows: Open the Command Prompt (press Win+r, type 'cmd' and press enter) and typing: netstat -a -b -n -o, then you can find the processes that are using the ports. Check what those processes are (make sure they aren’t critical to the system), then if it’s safe to do so, you can stop those processes from the Task Manager, or via. the Command Prompt by typing taskkill /PID [Process ID].
We hope this helps. 🙂
