The engine

Every threshold here was measured

Not one number in this document was chosen because it sounded right. Each came from testing against real footage, and where a measurement contradicted our assumption, the assumption lost.

8pipeline stages
4independent highlight signals
1 851segments in the reference VOD
24/24frames pixel-verified
Highlight detection

Four signals, weighted

A moment becomes a clip when several of these agree. Any one alone is weak.

S1

Laughter, from acoustics

A laugh has a physical signature: amplitude modulation between 4 and 8 Hz in the speech band. We band-pass 300–3000 Hz, take the envelope, and look for a peak in that range. This is far more reliable than hoping the transcriber writes "haha".

The catch we found the hard way: rhythmic speech modulates identically. Raw detection ranked repeated phrases highest — someone saying the same word four times looks exactly like laughter to a frequency analyser. So the signal is gated: a window only counts as laughter if the text there is empty, a laugh token, or low-confidence.

Reference distribution, non-zero points
percentilep50p85p95p98max
value0.0170.0390.0650.0920.195

A segment takes the maximum over 10–60 curve points, so it lands naturally high. Normalising against p85 made almost every segment saturate and the signal stopped discriminating. p98 is the working reference.

S2

Hype, as density

One exclamation means nothing. Four in fourteen seconds is the moment. Reaction words are therefore counted in a rolling twenty-second window rather than per line — the unit of excitement is a burst, not a word.

Why density and not keywords "no way" × 1 → noise · "no way" × 4 in 14 s → clip

Measured on the reference VOD: reaction words appeared 49 times across the whole stream, never more than once per line. Counted per line the signal is invisible; counted per window it is obvious.

S3

Game events

Openings, rare drops, boss kills, the reveal in a podcast — the moments an audience actively seeks out announce themselves in vocabulary. The word list is picked to match what is actually being recorded, automatically, because feeding one context's terms to another produces confident nonsense.

Clustering in the reference VOD
window75–80 min35–40 minrest of stream
event terms21150–2

These events happen in sessions, not moments. The density measure finds the session; a keyword match would scatter across it.

S4

Audio energy

The weakest of the four on its own, and deliberately weighted lowest. Loud is not the same as interesting — gunfire is loud. Energy is used to confirm the other three rather than to nominate moments by itself.

The check we run on every video the flattest routine chatter must score 0.00

Routine callouts and filler — the most common lines in any recording and the least interesting. If they score above zero, the detector is broken.

Speaker identity

Why we ask for two minutes alone

Getting this wrong is worse than not doing it, so the bar is deliberately high.

Window length is everythingMEASURED

Speaker embeddings need speech time to stabilise. We tested the same clean recording at three window lengths, with and without noise reduction.

audio3 s5 s8 s
raw0.5710.6580.730
noise-reduced0.5770.6650.736
Noise reduction is irrelevant — window length is the variable
Cohort normalisationWHY IT WORKS

With a single voice profile, "is this you?" has nothing to compare against, so the threshold alone decides and it fails in both directions. We build a cohort from the other voices in your own stream and ask a better question: does this resemble you more than anyone else in the room?

methodyour voiceothersseparation
threshold only0.5490.2080.341
cohort-normalised0.247−0.3120.559
Recall on own voice 95 % rose to 100 %
Cross-talk is the ceilingHONEST

When two people speak at once the embedding is a blend of both and matches neither cleanly. In a lively Discord call that is most of the stream. We would rather colour fewer lines correctly than colour many lines wrongly.

Lowering the threshold returns the wrong-person problem
More profiles, better resultsROADMAP

Each additional voice profile sharpens every other one, because the comparison moves from an anonymous cohort to a named rival. Profiles for your regular co-streamers is the single biggest accuracy gain available.

Two minutes of solo audio per person
Language

Vocabulary is a bias, not a hint

This is the mistake that cost us the most, and fixing it produced the single largest quality jump in the project.

01Wrong game's vocabulary
Feeding one game's terms into another stream actively pulls transcription off course. It does not degrade gracefully — it produces confident nonsense.
fixed
02Game detection first
Three short samples are transcribed with no bias at all; whichever domain's marker words appear most wins. Takes about thirty-five seconds.
35 s
03Confidence floor
Lines below a measured confidence threshold are dropped rather than shown. Band analysis of real output put the boundary at a specific value — above it the text is correct Swedish, below it is invented.
−2.0
04Prompt echo removal
On silent passages a transcriber will repeat its own instructions back as if someone said them. We compare output against the instruction and discard matches — and we write instructions that nobody would ever say aloud.
fixed
Result on the reference VOD
  • High-confidence lines: 81 % → 95 %
  • Lines below the confidence floor: 21.1 % → 7.6 %
  • Invented lines reaching the screen: 202 → 0
Channel safety

Two different problems

Masking a word and refusing a moment are not the same thing, and conflating them is how channels get struck.

Word level — mask and bleepCENSOR

Slurs are replaced in the subtitle and covered with a tone in the audio. Ordinary swearing is left alone — it is part of how people actually talk, and removing it makes the clip feel sanitised.

The tone is applied after noise reduction, or it gets erased
Moment level — never cut itGATE

If a passage reads as racist, no clip is made from it at all. A bleep does not save a clip that is about the joke — it just means your viewer hears a bleep in the middle of it.

Runs before selection, on word stems not whole words
Why stems and not whole words
  • Our first word list required full endings and therefore missed a truncated slur that sat in a delivered clip. A false positive costs one discarded moment; a miss costs the channel. We match stems and accept the occasional over-caution.
See it on your footage

The detector readout is free

Upload an hour and read what it measured. That is the whole argument.