Show time
—
Reliability
The interface is an Electron application; the audio engine is a small native binary in its own process, speaking a documented socket protocol. The interface can die or be replaced and the show keeps playing — the engine is the only thing that touches the device, the decoders and the mixer.
The nightly run
Every night, eight one-hour shards run the same generated show, a different seed each, driven against the engine's silent pacer: its real mixer and sample clock with no device attached. The show is hundreds of cues an hour — overlapping voices, fades, loops, seeks and routing changes. Each shard asserts:
- zero xruns — no device callback missed its deadline;
- zero stream underruns — no frames of silence while waiting for media;
- every cue starts within a stated tolerance of its scheduled time on the sample clock;
- the engine clock stays within a stated drift of the wall clock.
The tolerances are part of the result itself, so the claim can be checked against the numbers rather than taken on trust.
The kill tests
A show meets failures the desk did not plan for. These run on every pull request, and again in the nightly workflow:
- Renderer killed mid-show — the interface comes back with an explanation of what happened, and answers input again.
- Engine killed mid-show — a replacement engine takes over, the cue chain keeps its time across the change, the next cue's audio reaches the replacement, and the operator is told.
- Device taken away mid-show — the engine stops playing rather than pouring sound into a device that is no longer there, says why in its own words, and the show can go on when the rig comes back.
- A media reader that stalls mid-stream — the engine fills the silence, counts it, tells the operator, and carries on from where the show actually is; the cue keeps playing and the show clock keeps wall time.
- Malformed media at the cue list — the file is refused as unreadable, the cue that was playing is untouched, and the engine still plays the next cue.
Each of these asserts a defined behaviour — the show is silenced, or the operator is told, or playback resumes — not merely that the application did not crash.
Last run
The soak is nightly, and a result is shown here only while it stands for now: one dated at most 48 hours ago, and not ahead of this page's own clock, is rendered in full below. Past that, or with a date this page cannot read, it says it has no current result and names the date of the last run it holds, rather than presenting that run's numbers as the latest.
No nightly result published yet. The nightly soak writes soak-latest.json next
to this page when it finishes; until that file is here, this page reports no numbers.
—
Cues started
—
xruns
—
Stream underruns
—
Worst start delay
—
Worst clock drift
—
Shards
| Shard | Minutes | Cues started | Max start delay | Clock drift | xruns | Stream underruns | Result |
|---|