segno Source

Open source · GPLv3

A live looper you play with your feet.

Segno is a live looping appliance: a floor console with ten footswitches and two screens, a native C audio engine, and a Flutter interface on a Raspberry Pi 5. The software, firmware, hardware and interface designs are public, in three repositories.

The Segno console seen from above at an angle: ten footswitches with light bars, an encoder with a light ring, a small screen showing a waveform, and a large screen showing four tracks.
Render of the console design from Autodesk Fusion. This is not a photo.

Status: in active development. The software runs on the appliance today with the console board on the bench. The enclosure exists as a CAD design, so every picture of the console on this page is a render. The devlog has progress notes as the work merges.

What it does

Record a phrase, let it repeat, and add another part over it, without taking your hands off the instrument.

Record and layer

Eight tracks in two banks of four. Record, overdub, play, stop, and undo or redo each layer. Every track follows one master loop clock, and a track can run for a whole multiple of the first loop's length.

Foot control

Ten footswitches, an encoder with an LED ring, and a light bar above each switch that shows its state. Two jacks take an expression pedal or an extra footswitch. DIN MIDI in and out, and USB MIDI controllers through a mapping layer.

Tempo or free time

Loop against a tempo with a click and count-in, or switch to free mode and set the loop length by playing. Latency is measured with a loopback cable and compensated when recording.

Effects and routing

Built-in effects on live inputs, on recorded tracks, and on outputs. Each input can be heard dry on one set of outputs and with effects on another at the same time.

Sessions and recordings

Save a loop session as WAV stems and a manifest, and open it again later. Record a whole performance and export it as an Ableton Live 12 project.

Updates

The appliance installs signed system updates into a second partition and boots into it on trial. A failed boot falls back to the previous system.

The interface

The large screen shows the tracks and the mixer. The interface is a Flutter app that runs directly on the display hardware, one Flutter engine per screen.

The Tracks view: four tracks named GUITAR, BOOM, RC20 and VOX with level meters, a timer and a BPM readout.
Tracks view.
The mixer view: each track has mute and solo buttons, a pan control, a level in decibels and stereo meters.
Mixer view.

Both images are captures from the app's UI tests, with simulated track state.

Hardware

A wedge-shaped folded sheet-metal console, 850 mm wide, with the top sloping toward the player. The ten footswitches are built into the chassis and wired inside it.

Renders of the console design from Autodesk Fusion. Not photos.

Inside the console

  • ComputerRaspberry Pi 5, booting from NVMe
  • Screens15.6-inch main touch screen and a 7-inch readout, both over HDMI
  • ControlsTen footswitches, an encoder with a 35-pixel LED ring, 80 LED pixels in ten light bars
  • Console boardRaspberry Pi Pico 2 (RP2350), linked to the Pi over UART
  • Ring boardSeeed XIAO RP2350 driving the encoder and its ring
  • PowerUSB-C Power Delivery at 20 V, negotiated by an STUSB4500
  • AudioA USB audio interface, driven directly through ALSA
The console board v3: a purple circuit board with a Raspberry Pi Pico 2 in the middle, a 40-pin header for the Raspberry Pi, and labelled connectors for each footswitch, MIDI, the CTRL jacks, the LED pills and the ring board.
Console board v3, KiCad 3D view. Through-hole parts, designed to be soldered by hand.

Architecture

The console board reports what your feet do. The app decides what that means. The engine does the audio.

Audio engine

  • The audio thread never allocates, locks or makes system calls. Commands reach it through a single-producer, single-consumer ring.
  • One master loop clock keeps every track phase-locked.
  • Each track holds up to eight lanes. A lane records one input into its own buffer and has its own effects chain.
  • Tests drive the engine without an audio device, sample by sample.

App

  • Separate Dart packages for the engine interface, looper, pedal link, MIDI, sessions, performance recording, WAV encoding and DAW export.
  • Presentation depends on repositories, and repositories on data clients, never the other way round.
  • The engine's typed Dart interface is the test seam, so app tests run against fakes.

Appliance image

  • A Yocto build that boots the Raspberry Pi 5 from NVMe.
  • Flutter draws straight to both HDMI outputs over DRM/KMS through ivi-homescreen. No compositor, no desktop.
  • Audio goes through ALSA with no sound server in between.
  • Updates are signed RAUC bundles installed A/B with the Pi firmware's trial boot.

In the repository

The software, firmware and hardware designs are public under the GNU General Public License v3.

lib/The Flutter app
packages/The audio engine (segno_engine) and the Dart packages the app is built from
firmware/Firmware for the console board and the ring board
segno-hardwareKiCad board generators, the parametric enclosure, 3D-printed parts and the manufacturing package
segno-designSnapshots of the Penpot design file, the frozen Pencil file and the design studies
deploy/The Yocto image and the build for the Raspberry Pi
docs/Design notes, plans and build instructions