quite.spaceOne track, one shared moment: the host presses play — and everyone hears the same second.
A room is added to a post: composer → the 🎧 Listening room chip → a name and a file. The ready-made space preset for this is 🎧 Release space in the creation wizard (spaces).
How it works
The host is whoever pressed the button. Their commands (play, pause, seeking) are space events, signed and durable. Everything else is computed from the last command and the shared clock.
Hence a consequence that surprises at first and then turns out to be right: your pause is not a command. Press pause on your end — you have simply stopped following; you stopped no one and nothing twitched for anyone else. Press play — you catch up with the shared time again.
What the status line says
| line | what is happening |
|---|---|
session idle · host starts it |
the room exists, the host has not started yet |
Following |
you hear the same thing as everyone |
Following · approximate |
the same, but the shared clock is less precise (see below) |
Local pause · not following |
you paused on your end |
paused by <someone> |
the host paused for everyone |
host away · playing the last command |
the host is out of sight; the last command is playing |
track ended · host can restart |
the track is over |
On “calibrated” and “approximate”
Synchrony rests on shared time. The node honestly reports where it got it from:
- calibrated — the clock was checked against a shared relay. Only this earns that badge.
- approximate — the source is not shared; precision is lower.
- uncalibrated — no check happened at all.
The word “in sync” is not written where the grounds are weaker. Live, on a shared relay, the drift stays within tens of milliseconds.
Sound yields
Only one thing plays at a time. The listening room takes priority over a post’s atmosphere: if you open a post with sound during a session, the background will not start playing on top — it will honestly say why it is silent (atmosphere).