tail log output visible in gui #3176
Replies: 10 comments
-
Hi, The log in the GUI is controller by OSC (open sound control) messages sent from the Ruby server. You can't tail it as such, but you could get a similar effect by setting up a program called If you're on a mac with homebrew install you can get
then running
BUT you won't be able to run the GUI at the same time. You'll have to run the ruby server directly like so
As you can see, this is getting a bit complicated but that's probably your best bet for now. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the help! Using vim as my editor so don't need the GUI as long as I can run the server directly. Trying to setup a buffer where I can see the output next to the file I am working on. |
Beta Was this translation helpful? Give feedback.
-
Cool maybe post a screenshot or something in here with any notes on what you needed to get it working. Also make sure you check out the |
Beta Was this translation helpful? Give feedback.
-
Will do! Have the cli working and running scripts from vim. When I get the output visible next to my working file I will share the solution. Thanks again! |
Beta Was this translation helpful? Give feedback.
-
Getting an error trying to start the server from cmd line on osx: $ ./app/server/bin/sonic-pi-server.rb Checked out the file and has to do with ruby version. Running ruby -v returns: However ruby version at path /Applications/Sonic Pi.app/app/server/rb-native/osx/ is 2.2.2p95 Anyway I can update to that version? |
Beta Was this translation helpful? Give feedback.
-
TLDR: Run it with the following command instead
Explanation: The
which is known as a "shebang" in the unix world. When you execute the file directly as you were doing, it uses this shebang as a hint for where to find the program it needs to use to interpret the file. In this case it was using whatever your default Ruby was set to (version 2.1.4). The way Sonic Pi loads the gems currently uses the Ruby version to find where the compiled gems live. Because of the difference between your default Ruby version and the one that ships with Sonic Pi, it couldn't find the right folders. By specifying the exact ruby version (in this case the one we ship with Sonic Pi) we can ignore the shebang line altogether and the correct version of Ruby will be used. That way the folder names will be right and it should load the gems without problems. |
Beta Was this translation helpful? Give feedback.
-
It looks like this set of tools might be the way to go here now https://github.com/lpil/sonic-pi-tools In any case I don't think this is going to be a built in feature for a while and it looks like there are tools to solve the problem in the meantime. Might be worth closing this issue. |
Beta Was this translation helpful? Give feedback.
-
I was able to get this working... I cloned the repo and followed the install from source instructions (for OSX) ignoring the QT GUI instructions since we are not using it. I used RVM to install Ruby 2.1.0 which seemed to solve all of the ruby version issues (would be nice if someone else could confirm that this works). After installing and linking SuperCollider and compiling the extensions per the instructions, I started the ocsdump Opened vim (after installing the vim plugin) and ran the code using the leader keys and voila!! |
Beta Was this translation helpful? Give feedback.
-
We definitely want to have a simple way of viewing the contents of the If someone wants to work on this, that would be ace :-) |
Beta Was this translation helpful? Give feedback.
-
Just a quick note to say that I have a rudimentary experimental version of a log viewer written in Elixir LiveView which I hope to make available in an upcoming BETA. |
Beta Was this translation helpful? Give feedback.
-
Hi! Is it possible to tail the output visible in the GUI? Tried each of the logs in /.sonic-pi/logs with no luck.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions