Sonic-pi scripting

[FOSSBOSS]

I havent gotten sonic-pi to compile from source yet so perhaps this is mute, but I would like to send command line arguments to sonic-pi for execution. something to the format $sonic-pi --run sample ebit_bass, "120","Cm",1, lpf: 100,amp: 5

live coding is great, but Im not sure how to implement sonic-pi in a scripting format, which is what I would be interested to do.

[rbnpi]

I find https://github.com/Widdershin/sonic-pi-cli useful for sending command line stuff to a running sonic-pi.

[rbnpi]

sonic-pi-cli needs upgrading to work with 4.0beta if you are using that.

[iamjonny]

sonic-pi-cli needs upgrading to work with 4.0beta if you are using that.

Hi, does anyone know what's involved to make this cli work with SP 4+?

I read that the cli (or maybe SP) has auto port assignment, looking at the breaking changes introduced into new sp vs cli code, I think the cli is hard -coded to expect sp on a port (4557) but don't know

• if simplest fix is to change port in cli code, or how, and whether rebuild is required
• if possible to update cli to detect assigned port (if dynamic)
• if any other changes are required to make it work, or how to peruse and test sp.api (used by cli and others) , from my research I believe everything is basically OSC.

It may be the simplest fix is to reassign sp to it's original osc port, but from the code I glanced at in q related commit I think it mentioned 4557 was n/a, or used for something else

Really appreciate any insights! Thanks

[rbnpi]

I wrote an update which you can install using gem install sonic-pi-cli4
Works the same as sonic-pi-cli but uses sonic_pi4 to invoke it rather than sonic_pi.
it seemed complex to include it on the original so I made it separate. Usual caveat. Uses unofficial access to log files which are not guaranteed to remain in the same format. Works with all versions from 4.0 onwards so far. NB on RPi need sudo to install the gem

[vomitHatSteve]

I wrote an update which you can install using gem install sonic-pi-cli4 Works the same as sonic-pi-cli but uses sonic_pi4 to invoke it rather than sonic_pi. it seemed complex to include it on the original so I made it separate. Usual caveat. Uses unofficial access to log files which are not guaranteed to remain in the same format. Works with all versions from 4.0 onwards so far. NB on RPi need sudo to install the gem

Are you accepting PRs for this somewhere? I've found a bug where subsequent launches of the daemon break your logic.

[samaaron]

Today I added an official (albeit very basic) command-line REPL to Sonic Pi. It'll be available in the next release as a bash/batch script which starts a Ruby script running in a terminal/cmd.exe window.

It's cute and somewhat usable - but its main function is to serve as a template for implementing other tools/GUIs with Sonic Pi as a backend.

In addition to the interactive REPL, you can also run the script with a path to a file and it will run the contents of the file immediately after boot (in addition to landing you into the REPL).

Code is:

• https://github.com/sonic-pi-net/sonic-pi/blob/dev/bin/sonic-pi-repl.sh
• https://github.com/sonic-pi-net/sonic-pi/blob/dev/app/server/ruby/bin/repl.rb

2024-07-29.20-00-04.mov

[ahussey-redhat]

I was thinking about something like this myself.
The ability to create repeatable songs, or Music as Code.

I am just spit balling here, but it would be great to add a player instance.
You can call player.<song-class-name>.

some psuedo code

song testSong:
  play:
    # the 'play' function contains the calls to; beat, chorus, method, versus functions, in the order they should be executed
    # functions that should continue running until told to stop should be called in a similar way to 'live-loop'
    live-loop:
      self.beat
    end
    self.first_verse
    self.chorus
    self.second_verse
    self.chorus
    self.third_verse
    self.bridge
    self.chorus
   beat:
     #<insert-beat-code-here>
   chorus:
     #<insert-chorus-code-here>
   bridge:
     #<insert-bridge-code-here>
   first_verse:
     #<insert-first-verse-code-here>
   second_verse:
     #<insert-second-verse-code-here>
   third_verse:
     #<insert-third-verse-code-here>

The advantages to this, is someone can upload their code to a git repo, people can fork it and use it as the basis for their music, or could create a PR with modifications that might improve the song.

It allows collaboration.

Just my 2c

• Alex

[samaaron]

I was thinking about something like this myself.
The ability to create repeatable songs, or Music as Code.

This one of the goals of Sonic Pi and is already achievable using the current language design. I'm not sure how this is related to running things from the terminal (which I think is the original intent of this discussion)

[FOSSBOSS]

I just learned about supercollider.... which the sonic-pi server is built off of. Anyway, sclang, (supercollider language) facilitates scripting.

[samaaron]

I havent gotten sonic-pi to compile from source yet so perhaps this is mute, but I would like to send command line arguments to sonic-pi for execution. something to the format $sonic-pi --run sample ebit_bass, "120","Cm",1, lpf: 100,amp: 5

For this to work nicely, you'd either need to have Sonic Pi running in the background or have started a background daemon process running all the Sonic Pi processes. Otherwise, you'd have to boot all these processes (taking a good few seconds) before the script could be executed.

Some sort of official CLI could still be on the cards for the future, but I'm still pretty unclear what the precise usecases are.

[jonnyhotchkiss]

clipboard use-case
Something I tried to achieve/prototype from SP Editor with a required clipboard gem, but I think I got a memory error.
Basically reducing the time and user-steps taken to listen to stuff, usually in the browser

One reason I had hoped to learn enough* about was to add drag drop between panels and from external applications , but I'm learning to adjust expectations much quicker than anything useful! CMake, VS et al remain my nemeses.
*Qt and the Beam, and all this cool new stuff in SP's innards

[rbnpi]

Hi SteveI haven’t got this set up in a public repository at present but if you want to send me details I’ll see what I can do. Unfortunately I am preparing to downsize and move house at the end of August spending all my time preparing for this , then I have some hospital treatment to look forward to after that so have very little free time at present. Sent from my iPhoneOn 28 Jul 2024, at 19:52, Steve ***@***.***> wrote: I wrote an update which you can install using gem install sonic-pi-cli4 Works the same as sonic-pi-cli but uses sonic_pi4 to invoke it rather than sonic_pi. it seemed complex to include it on the original so I made it separate. Usual caveat. Uses unofficial access to log files which are not guaranteed to remain in the same format. Works with all versions from 4.0 onwards so far. NB on RPi need sudo to install the gem Are you accepting PRs for this somewhere? I've found a bug where subsequent launches of the daemon break your logic. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[vomitHatSteve]

Sure. in bin/sonic_pi4, you parse spider.log from top to bottom, so if the user runs it multiple times without deleting the log, it will keep grabbing the same port and token from the first run.

So, I rewrote token and pvalue as:

def token #this functions reads from the spider-log
  #the dynamically allocated token value used in internal gui comms
  value='' #initialise variable
  #read spider.log
  f1 = File.open(ENV['HOME']+'/.sonic-pi/log/spider.log','r')
  token_line = f1.grep(/^Token:/)[-1]
  value = Integer(token_line.split(" ")[1])
  return value #return found port value
end

def pvalue
  value='' #initialise variable
  #read spider.log
  f1 = File.open(ENV['HOME']+'/.sonic-pi/log/spider.log','r')
  ports_line = f1.grep(/^Ports:/)[-1]
  ports = ports_line.split("{")[1].split("}")[0].split(", ").map{ |s| s.split("=>") }.to_h
  value = ports[":server_port"]
  return value #return found port value
end

Obviously, the split-chaining may not be to your liking, but the key takeaway is getting the last line that starts with "Token:" and "Ports:"

[samaaron]

Note that this won’t work in the next release of Sonic Pi. Instead you should be reading the ports and token from the stdout of the daemon process.