Sonic Pi v5 swaps its audio engine so you can plug in headphones mid-jam

Since its first release, Sonic Pi produced its sound through SuperCollider — more precisely through the scsynth synthesis server. An engine of extraordinary power, built for audio synthesis research, and not really for beginners learning to code by making music.1

The project just shipped v5.0.0, on August 7, 2026, with a change that looks like nothing and changes everything: scsynth is replaced by SuperSonic, an in-house port Sam Aaron has been working on for about a year, and audio settings now live in the interface, on the fly.1 2

The gesture this change unlocks

The most telling benefit is a tiny gesture: plugging in your headphones mid-set, without restarting, without killing the loop that is running. With the old engine, that simple move was friction — you had to relaunch.1

v5 lets you change input, output, sample rate and buffer size directly in the GUI, without losing the music that is playing. It is the kind of technical decision users feel immediately, even if they cannot say why the experience changed.

Beyond the headphones

The rest of the release digs the same idea: letting code and performance co-exist, without interrupting the flow.

Link support streams live audio from other Ableton Link peers, and the tempo can lock to an incoming MIDI clock with use_bpm :midi. A game controller becomes an instrument, screen recording is built in, and the window can be sent into Syphon/Spout-compatible visuals software.1 3

The interface gets its share too: redesigned autocompletion with live previews, a rebuilt Docs pane with runnable examples and synth playgrounds, Quickstart Cards, Sets to save all ten buffers together, and wide accessibility work.1

What this says to tool makers

The choice is interesting because it is rare: rather than keeping to patch around a powerful but ill-suited engine, the author went as far as replacing it with a port dedicated to the use case. SuperSonic is described as a “friendly port” of scsynth, designed for the ergonomics and stability of an educational tool, not the intensity of a research lab.1

For a small team or an independent, it is a lesson in prioritisation: when inherited power costs users more friction than it returns, replacing it can be more honest than maintaining it forever.

And for teachers, the message is simple: when you design a tool to bring people into code, interruption is the enemy. If plugging in headphones required a restart, the tool had not finished its job.