Unable to start sonic Pi #3395
Comments
|
You must copy and paste the messages. |
|
Hi, could you try the recently released v4.5.1 and let me know if that helps things? https://github.com/sonic-pi-net/sonic-pi/releases/tag/v4.5.1 |
|
Sorry, Sonic Pi is having issues booting: System Information Exiting - shutting down scsynth server... Sending /quit command to scsynth Stopping OSC server... Stopped OSC server... daemon.log [2024-05-22 09:48:09] [ruby] Exiting - shutting down scsynth server... [2024-05-22 09:48:09] [ruby] Sending /quit command to scsynth [2024-05-22 09:48:09] [ruby] Stopping OSC server... [2024-05-22 09:48:09] [ruby] Stopped OSC server... tau.log Number of detected peers: Current tempo: 09:47:58.703 [info] Detected MIDI input ports: Detected MIDI output ports: 09:47:58.703 [info] OSC cue forwarding to {127, 0, 0, 1} 09:47:58.704 [info] +--------------------------------------+ 09:47:58.706 [info] Running TauWeb.Endpoint with cowboy 2.10.0 at 0.0.0.0:38604 (http) scsynth.log Device options:
;(Swapnil's S20 FE)) (device #22 with 0 ins 1 outs)
;(Swapnil's S20 FE)) (device #23 with 1 ins 0 outs) Requested devices:
Selecting default system output device Booting with: gui.log |
Sonic Pi Boot Error ReportTLDR: Supercollider was missing (when installed with 'sudo apt install sonic-pi'), but even installing that doesn't change much System Information
GUI Log
Server Errors
Server Output
Scsynth Output
Process Log
|
|
Hi (in reply to Aera23) Some of these problems are because you don't have Real Time Priortiy enabled To fix this the easiest way (probably) is to open a terminal and run
and it should ask if you wish to enable Real Time Priority Y/N Answer yes But you also need to be a member of the audio group To do that
You will need to logout and login again for that change to take effect, you might need to reboot to get the RT Priority enabled, so probably best to reboot anyway Enabling RT Priority creates a file: /etc/security/limits.d/audio.conf and adds 3 lines to give RT to members of the audio group I would suggest you edit that and remove the # at the start of the "nice" line, too NB I am assuming Peppermint OS is similar to Linux Mint |
|
Thanks
…On Friday, May 24th, 2024 at 6:58 AM, idommason ***@***.***> wrote:
Hi
Some of these problems are because you don't have Real Time Priortiy enabled
Cannot use real-time scheduling (RR/10) (1: Operation not permitted)
AcquireSelfRealTime error
Cannot use real-time scheduling (RR/5) (1: Operation not permitted)
JackClient::AcquireSelfRealTime error
To fix this the easiest way (probably) is to open a terminal and run
sudo dpkg-reconfigure jackd2
and it should ask if you wish to enable Real Time Priority Y/N
Answer yes
But you also need to be a member of the audio group
To do that
sudo usermod -aG audio $USER
You will need to logout and login again for that change to take effect, you might need to reboot to get the RT Priority enabled, so probably best to reboot anyway
Enabling RT Priority creates a file:
/etc/security/limit.d/audio.conf
and adds 3 lines to give RT to members of the audio group
# Provided by the jackd package.
#
# Changes to this file will be preserved.
#
# If you want to enable/disable realtime permissions, run
#
# dpkg-reconfigure -p high jackd2
@Audio - rtprio 95
@Audio - memlock unlimited
***@***.*** - nice -19
I would suggest you edit that and remove the # at the start of the "nice" line, too
NB I am assuming Peppermint OS is similar to Linux Mint
Also I'm not in anyway connected to Sonic Pi other than an interested user
—
Reply to this email directly, [view it on GitHub](#3395 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A7C7TGK2IXRAOPWDARHKDLLZDZNRRAVCNFSM6AAAAABGP6Y4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRYGA2DQMBSGQ).
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Did that work? I've done a walkthru on building Sonic Pi v 4.51 on Linux Mint that has a lot of explanations of the issues I run Sonic Pi 3.3.1without problem on this laptop, as I am not prepared to switch all over to pipewire at this point. I use this laptop in gigs, and for rosegarden and I just haven't tested all of those against pipewire vs pulseaudio yet As far as I recall the only issue for 3.3.1 was that I was not a member of the audio group (by default) and you have to enable Realtime Priority, and once I worked that out Sonic Pi 3.3.1 worked. But I already had jackctl set up and configured as I was already using Rosegarden and Qsynth. The walkthru for building v 4.50 / 4.51 should work for any recent debian / ubuntu based distro. There are slight differences in some of the package names, but my long explanation does detail those. |
Sonic Pi Boot Error ReportI wish. I logged out/in, then also restarted, then even installed "supercollider" manually, and same issue. PS: Peppermint OS is based on Debian, tho technically, yes, Linux Mint (mint's based on ubuntu, which is based on debian) also uses apt, systemd, and similar. System Information
GUI Log
Server Errors
Server Output
Scsynth Output
Process Log
|
|
OK, so one problem is fixed, and what we can now see is that scsynth code is broken in 3.2.2 when this tries to run:
I think I might have had the same issue, but then I found a download for sonic-pi 3.3.1 from this page: https://in-thread.sonic-pi.net/t/binary-deb-for-ubuntu-20-04-and-20-1-for-sp-3-3-1/5141 and installed that I think I had to get apt to fix missing packages / dependencies after that ie
But you would still have had to do RT priority and add yourself to the audio group with this version. 3.3.1 definitely runs on Linux Mint with pulseaudio, whereas the 4.50 versions require a change to pipewire, which I just haven't done yet on my main laptop |
|
oh yes, that worked. (initially it appeared not to, then I ran as sudo, but that was silent.... and my next run as normal user worked) |
I'm trying to install Sonic PI and I'm getting the following error.
The text was updated successfully, but these errors were encountered: