MANUAL · 16
The things people ask most about how SUB/WAVE behaves — how it copes with an empty room, what it needs from a model, and what the moving parts behind the DJ actually do.
AN EMPTY ROOM
By default, nothing changes: the station broadcasts the same whether anyone is tuned in or not. But there is an optional setting, Pause when empty, that changes this. With it on, the moment the listener count hits zero the DJ stops doing AI work: no track-picking, no spoken links, no station IDs. The music keeps flowing from a fallback playlist so the stream never goes silent, and the DJ wakes straight back up the instant someone tunes in. It exists to save tokens, and money on a paid model, when there is no one there to hear the DJ anyway. See Models & Tokens.
MODEST HARDWARE
Yes. Start with Track Shortlist: the controller finds the eligible tracks and the model makes one structured choice, so it does not need to support a chain of tool calls. Direct request matching and the direct segments-and-skills runtime can also be selected independently to keep the work within a smaller model’s comfort zone. Larger or cloud-hosted models can use Agentic Tools where that suits the station. Track selection lives under Settings → Music Selection; direct segments and skills remain under Settings → DJ Behaviour. More model guidance is on the Models & Tokens page.
A TAGGED LIBRARY
Every track in the library can carry a mood: a label like calm, energetic or reflective. The station tags the library in the background, and the DJ leans on those tags to pick music that fits the moment: the time of day, the weather, the show that is on. A well-tagged library gives the DJ a far richer palette to choose from. You can watch the tagger’s progress on the Library page in the admin console. Untagged tracks still play; they just don’t get matched by feel.
OPERATOR TOOLING
These are two helper skills bundled with the project for whoever runs the station, used through Claude Code. subwave-deploy handles installing and updating: a first-time setup from a fresh checkout, or pulling the latest code and rebuilding only the parts that actually changed. subwave-control is lighter: it simply starts or stops the station in development or production mode, with no builds. Day to day you reach for control; after a code change you reach for deploy. The hands-on steps they automate are written out in the setup guide.
CHOOSING THE NEXT SONG
They are two selectable ways to choose the next song. Track Shortlist has the station prepare a varied list of eligible tracks, then asks the model to choose one. Agentic Tools lets a tool-capable model search the library itself before it decides. Both respect the same show, recency and artist rules; neither is presented as the more musical choice.
Which one suits you comes down to your model, hardware and token budget. The full comparison is on Concepts; the model side is on Models & Tokens.
WHEN SOMETHING’S OFF
The admin console’s Debug page is a live snapshot of the station’s inner workings: the most recent AI calls and whether they succeeded, the audio mixer’s status, and the latest log lines. You don’t need it day to day, but it is the first place to look when something is off: the stream stalls, the DJ goes quiet, or a voice sounds wrong. It turns a vague “something’s broken” into a specific, visible cause. More on it in Admin & Settings.
For a deeper look there is also subwave-log-analysis, a bundled skill used through Claude Code. Where the Debug page shows the live moment, this reads the station’s full event log over time and reports back on how it has been behaving: how often it calls the music library, why the picker keeps favouring certain artists, whether the library pool is too narrow, and any runtime anomalies. It is the tool for “the station works, but something feels off” rather than an outright break.
MUSIC LICENSING
Maybe — it depends on what you stream and who can hear it. SUB/WAVE is software; it grants no rights to any music. Listening privately to music you own is one thing. Broadcasting it where other people can tune in can count as public performance, which is licensed in most countries. Whether you need a licence is on you, the operator. (Not legal advice.)
WHO’S RESPONSIBLE
No. It’s a broadcast tool, like the Liquidsoap and Icecast it runs on. It doesn’t clear, pay, or report anything to any rights body. If your station needs a licence, arranging it is the operator’s responsibility.
THE TWO RIGHTS
Usually two: the composition (songwriting) and the sound recording. In the UK that’s PRS for Music and PPL. In the US it’s ASCAP/BMI/SESAC for compositions and SoundExchange for recordings. Other countries have their own bodies. A public station can touch both.
SMALL AND PRIVATE
Non-commercial and small doesn’t automatically mean licence-free; public performance rules don’t always care whether money changes hands. A private stream only you can reach is lower risk than a public URL you’ve shared around. (Not legal advice — check your local rules.)
THE SAFE SIDE
Keep it private to people you intend, or build it from music that’s cleared for this: your own recordings, Creative Commons, royalty-free libraries, or public domain. SUB/WAVE saves hourly archives, which is the kind of record-keeping a licensed station usually wants if you go that route.