I make instruments. Software you stop noticing and start playing. I feel the gap between what an interface is and what it should be the way you feel a splinter, and I close that gap by building.

Motivation

I make music, and every session ends the same way. I bounce the mix to a file, close the DAW, and listen to it the way a stranger would, with a notebook open, writing down what to fix next time. That process used to take three apps: one to play the track, one to read how loud it is, one to write in. Every switch between them broke my concentration.

So I set out to build the one window I kept wishing for: the whole pass in one place. I wanted the track playing, its loudness drawn across the screen, and my notes pinned to the moments they're about. The rule I held to was simple: nothing on the screen should distract me from listening.

One Window

This is the window. Everything from the old three-app routine now lives in one screen. The track plays. A line shows how loud it is from start to finish. And when I hear something worth fixing, I write it down right there, on the track itself.

Design Details

Everything happens where you are looking. Click anywhere on the plot and playback jumps there. Press Cmd+N and a note opens at the exact moment under the pointer, ready to type. Press Return and it settles onto the track as a dot. If it landed a beat early, drag it. A thought is written down in the time it takes to have it.

Tracks and Notes

Two sheets live under the window, and each is one key away. T lifts the tracks: every bounce from the session, in the order it arrived, with the playing one in orange. N lifts the notes as a list, each with the moment it belongs to, and a box to check when it's fixed. You don't have to open the list to finish a note, either. Pull its dot off the track and two targets appear beneath it. Drop it on the check and it's done.

Motivation

A rhythm is a return. Something happens, time passes, it happens again, and the distance between the two events is the whole of it. The sequencer I learned on drew a rhythm as a strip. That drawing is true about order, but it says nothing about coming back. When the playhead reached the right edge and leapt to the left, that leap was the most important thing in the music and the least visible thing on the screen.

Shape of the Return

I started with a small question: could the line just be wrapped into a circle? The leap disappears, because a circle has no edge to leap from. The return stops being the thing you can't see and becomes the shape itself. And a shape can be read the way a line can't. The distance between two hits is an arc now. Patterns I would have called different turn out to be the same shape, rotated a few steps. On a ring there is no first beat, only the one you start on.

The Stack

But a loop is rarely one element. A beat is a kick, a snare, a hat: three or four of them turning at once, each on its own ring. They just turn together. So I stacked them. They line up exactly, and the one you see is the one you are playing. The others are directly underneath, and all it takes to see them is a different angle.

Making It Real

A drawing can make the case, but an instrument has to be played. So I built Rings as an iPhone app, so that anyone could pick it up and try the idea with their own hands. That raised a second problem. Everything the instrument can do is a gesture on the rings, and there is nothing on the screen to explain a gesture. So the app teaches itself. It opens on two ways in, Play and Learn, and Learn walks through each move in turn, waiting for you to make the move before it goes on.