Install sonic pi 3.2 dev on ubuntu 18.04 LTS

do you mean that all your first paragraph operations are done by the ./unix-prebuild.sh and so on ?

to get to the commit mentionned by Robin

nlb@devbox:~/audio/testRepo/sonic-pi$ git reset --hard 3e587fc
HEAD is now at 3e587fc5f Translated using Weblate (Polish)

from the qt folder, the path seems to be

ln -s `which ruby` ../../server/ruby/bin/

Well too hard for me. don’t lose time to try explaining… I will wait.

OK. Are you building on a Pi4 or on ubuntu 18.04 LTS? If the latter, I tried this on a virtual machine today, and there are a significant number of problems there, particularly with rugged and aubio, which I haven’t solved. I think a later ubuntu version may be OK, and hope to try that.
If you are building on a Pi then it builds OK. Yes the prebuild does all the documentation stuff, and the config script builds the gui, so things are much simpler.

ah sorry as the subject is “on ubuntu 18.04” i was thinking it waf for ubuntu. so yes i try under 18.04.04. I will try tomorrow under pi buster.

I actually managed to build the latest 3.2dev on ubuntu 18.04 today. It required a bit fiddling to get going. I needed to change the rugged gem to an early version to that used in the Sonic Pi repro, and also to build SuperCollider and the sc3plugins for version 3.9.1. I was able to use the new cmake install process to do the build.
I won’t write anything up yet until 3.2 is released, as there are still changes taking place which may affect things. I built it on a virtual Ubuntu 18.04, and although everything including the new scope displays worked fine, I couldn’t check the audio properly as the virtual sound card is not up to handling it with copious Xruns from the jackd supercollider link.

Thanks. I also had to add
#include <mutex>
to scope.h to compile it for some reason.

I found out that if I modified the unix-prebuild.sh not to remove the ruby-aubio-prerelease gem and also to use the installed ruby directly I did not need to create the symlink and did not get any errors, but maybe there is a reason for deleting the gem. Anyway this unix-prebuild.sh works for me:

#!/bin/bash
set -e # Quit script on error
SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

echo "Translating tutorial..."
/usr/bin/env ruby "${SCRIPT_DIR}/../../server/ruby/bin/i18n-tool.rb" -t

echo "Generating docs for the Qt GUI..."
cp "${SCRIPT_DIR}/utils/ruby_help.tmpl" "${SCRIPT_DIR}/utils/ruby_help.h"
/usr/bin/env ruby "${SCRIPT_DIR}/../../server/ruby/bin/qt-doc.rb" -o "${SCRIPT_DIR}/utils/ruby_help.h"

echo "Updating GUI translation files..."
lrelease "${SCRIPT_DIR}"/lang/*.ts

i have tried today to install the latest commit version.
Can’t get the midi works.

Failed to load the fast_osc c-extension, falling back to pure Ruby version
Overriding fast_osc c-extension FastOsc::decode_single_message, falling back to pure Ruby version
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
OSC handler exception for address: /cue-port-external
Connection refused - send(2)
["/home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send'", "/home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send'", "/$
OSC handler exception for address: /cue-port-external
Connection refused - send(2)
["/home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send'", "/home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send'", "/$
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
/home/nlb/sonic-pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/linux/sys/proctable.rb:112: warning: constant ::Fixnum is deprecated
OSC handler exception for address: /exit
Connection refused - send(2)
["/home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send'", "/home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send'", "/$
/home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send': Connection refused - send(2) (Errno::ECONNREFUSED)
        from /home/nlb/sonic-pi/app/server/ruby/lib/sonicpi/osc/udp_client.rb:30:in `send'
        from /home/nlb/sonic-pi/app/gui/qt/build/../../../../app/server/ruby/bin/sonic-pi-server.rb:328:in `block in <main>'

if someone has an idea. I guess it’s something with osmid.

You are right about the changes to the prebuild script. I have already submitted a pr about this. The removal of the ruby-aubio-prerelease was to benefit the windows install, and it copied over to the unix script in error.

As regards midi have you built the erlang files? osc.erl to osc.beam and pi_server.erl to pi_server.beam? What do your log files show. Does the erlang log show it has started? Can you see o2m and m2o started in the server output log?

that’s the problem i didn’t and really don’t know how to proceed. if you could show me the way i would try but i can wait for the official release.

On RPi I installed (erlang-server) EDIT APOLIGIES THAT SHOULD BE erlang-base package. Then cd to erlang folder holding the two .erl files and do

erlc osc.erl
erlc pi_server.erl

This produces the two .beam files you need.

Hi, just to be clear, there will be no official v3.2 release for Linux. I don’t have the resources to support all platforms and without volunteer support (i.e. someone maintaining a release for their preferred distribution) I will have to wait until my financial income from Patreon is sufficient enough that I can pay both my own salary and the salary of someone else to do this work. I’m sadly quite a long way from achieving this.

Been trying compiling on Ubuntu 19.10 for last few days, challange so far. Anyone had a luck? I be happy to start looking into PPA repo? There must be easy way to get this on Linux distro.

P

Hi @cerw - things on the building-front have been in a pretty hectic state of flux these last few weeks.

Now that v3.2.0 is tagged, and once I’ve taken a bit of a break I’ll be able to start putting some polish into the build process (unless someone beats me to it). Currently the Windows build is incredibly easy, so the Linux build can’t be far behind :slight_smile:

hi @samaaron,

I had it build in January from master, but after I did pull I am having trouble with ruby_help files. I think its’ 90% using one of the script from forum here, I did tried to boot into Windows and Sonic PI runs great, but not my NodeJS Scripts. Thank you answering to me :slight_smile:

Will try play with it later tonight.

P

Hi,

as I am mainly a Linux user and intend to work with Sonic Pi installed on Linux I am very much interested in a way to compile 3.2 on my machine.

(I made a quick attempt with the script from this thread which worked a few weeks ago, but I did not really expect this to work anymore, which was a correct assuption :wink: .

I do not really have specific knowledge in building and compiling but some general experience with Linux. So I am willing to help with testing and feedback.

Right now I am not sure how to start and would appreciate some hints.

have you seen my post ?

But i’m pretty certain, a procedure to install under linux the latest is coming soon. I have tried but for the moment got stuck with osc but Robin (as usual) would certainly help us.

1 Like

Hi @nlb,

thanks for the hint! Looks promising. The erlang/osc issue seems solvable (I did this before). Anyhow, I am also sure that there will be a solution. I just wanted to say, I am very interested and will be available for testing.

Once the dust has settled from the 3.2 release I think that it will be time to look at Linux building again. There have been a large number of changes over the last few weeks which will have affected “current” scripts, so much so that Sam Aaron has moved them to an old folder. There has been a lot of work to move the builds to cmake scripts. On the Raspberry Pi for example the whole process is quick and easy, and it should be possible to streamline it even further. I have also done Ubuntu builds on a virtual machine. (But the sound output on the virtual machine is not up to using it although the build works)

2 Likes