Build1 distinct publisher3 min readPublished
A sound that is not a word never reaches the transcript, so a 100 percent pass rate measured Whisper rather than the model. The replacement detector reads the RMS envelope, and its constants are fitted to four failures.
The Engineer · Build desk

Compiled by The EngineerSomething wrong?How this is made
The replacement detector computes RMS over 20 ms frames at a 10 ms hop, then applies one voiced test: rms > max(rms.max() * 0.06, 0.004) [10]. The relative arm sits 24.4 dB below the loudest frame in the clip [18]. The absolute arm sits at roughly -48 dBFS [19]. Taking the larger of the two carries the design, because a relative threshold alone lets the noise floor read as voiced on a quiet render, and an absolute threshold alone promotes breath and lip smacks on a loud one [11]. The twelve voices spanned 5.5 dB of stated level, -13.3 to -18.8 [12][20], and the post does not say which level measure that is.
Voiced blocks under 30 ms are then discarded, because otherwise lip and quantisation noise fragments into many tiny blocks and the sequence logic downstream stops meaning anything [13]. That 30 ms is half the 0.06 s minimum tail [21], which is the line I would check first in anyone else's copy of this code: a block filter set above your artifact threshold quietly deletes the thing you are trying to detect.
The artifact test needs at least two voiced blocks, a gap before the last one of 0.25 s or more, and a last block of 0.06 s or longer [14]. Measured artifacts had gaps of 0.26 to 0.91 s and tails of 0.07 to 0.36 s [15]. So the smallest observed gap clears its threshold by 0.01 s, exactly one hop [22], and the shortest tail clears its threshold by the same 0.01 s [23]. Those two constants are fitted to four failures of one model family, according to the dev.to write-up.
The false positive is the useful part of the story. A comma pause is correctly rendered script audio, and it satisfied both conditions with margin to spare [16]. GAP_MIN is a property of your probe script's punctuation, not of TTS artifacts [14][16]. The copy of the post I have cuts off as the author begins to state the discriminator he added, so I cannot tell you what replaced the bare gap rule.
Two arithmetic notes on the defect report itself. Body plus silence plus artifact comes to 1.52 s against a stated 1.61 s total, and 1.56 s against 1.65 s, leaving 0.09 s unaccounted for in both clips, which the post does not place [4][24].
The retention order in the transcripts runs against duration: the shorter artifact left a trace and the longer one, nearly twice its length, left none [7][25]. The stated reason is that short sounds which are not meaningful words may not appear in STT output at all [8]. Before the waveform work, the author read his own null result as evidence about the model, recording that STT scored 0/6 on extra sounds and concluding there were none [9].
For these constants to transfer to your pipeline, two things have to be true. Your probe text must contain no internal silence longer than 0.25 s [14], and your artifacts must sit above roughly -48 dBFS [19]. The first one you write yourself.
Ranked by verification strength, evidence, and original report placement.
On a later recheck from a different angle, 4 of the 12 voices still had defects that were invisible to STT-based inspection.
The author's TTS quality-control process was: have the model read probe sentences, transcribe with Whisper, compare against the script to check accuracy and trailing elongation, and analyse the waveform for utterance duration, sound pressure and F0.
The author created 12 voices and passed all of them through this QC: Whisper scored 4/4 accuracy, there was no trailing elongation, and sound pressure was within normal range, so a 100 percent pass rate was reported.
Reported measurements: one probe line totalled 1.61 s with a 0.88 s body, 0.48 s silence and a 0.16 s utterance; a second totalled 1.65 s with a 0.72 s body, 0.56 s silence and a 0.28 s utterance.
After the script finished there was a full 0.5-second silence followed by a 0.1 to 0.3 second utterance; the author states this is not trailing resonance but the model producing sounds that are not in the script.
Whisper barely caught the first artifact, appending a trailing vowel pair to the transcript, and completely dropped the second; the 0.28-second utterance does not appear in the transcription at all.
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · September 3, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
Whisper's exact-match gate selected the flattest take in an emotion-TTS corpus1 distinct publisher
build
A transcript is not a citation: Content Understanding's pitch to Foundry IQ users1 distinct publisher
build
Whisper's second segment turned a tail trimmer into a silence trimmer1 distinct publisher
build
A 0.85 speed request came back longer than the call that sent no parameter at all1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One engineer's numbers, published with the code
The strongest thing on offer is the segmenter itself: printed in full, inspectable line by line, and its two threshold arms convert cleanly to -24.4 dB relative and about -48 dBFS. Everything empirical is weaker, because no audio, corpus or per-voice table accompanies it - the 1.61 s and 1.65 s clips, the -13.3 to -18.8 dB spread and the detection counts are all self-reported and unreplayable. And the one figure a reader can check does not close: body plus silence plus trailing sound falls 0.09 s short of the stated total in both clips.
Twelve voices, 72 clips, one pipeline
The whole footprint is one engineer's rescan of his own voices - 72 probe clips, 29 hits before the comma fix and 16 after. That is a real measurement rather than a proposal, which is why this is not simply unknown, but no other team, product or pipeline is reported to use the technique, and there is no repository, package or downstream user named.
A modest write-up with one immodest edge
This is a retraction, not a launch, and the author volunteers the embarrassing parts: the 100 percent report was wrong, and his first detector run would have declared all twelve voices broken over a comma. What tilts slightly overstated is generality. The constants are presented as sound - 0.25 s 'is sufficient', 0.06 s 'avoids catching fade-out tails' - while each clears the smallest case it has ever seen by a single 10 ms hop, and the corpus-contamination cause is stated as settled fact on no shown evidence.
Reputation running the wrong way
Whatever pull exists is the ordinary one of a developer blog cross-posted for readers - the piece points back to the author's own Japanese site. Against that, the story only exists because he had to unfile a 100 percent pass rate under his own name, and there is no model, service or vendor whose fortunes the conclusions could help. Self-inflicted correction is a poor vehicle for promotion.
Checkable logic, uncheckable audio
We can be fairly sure about the reasoning: STT genuinely will not surface a 0.28 s non-word, the dual threshold argument holds, and the comma false positive is self-evident once the block boundaries are shown. We cannot be sure about the measurements, since one author, one outlet and no released clips leave the numbers untestable and the arithmetic already slips by 0.09 s. Confidence lands mid-range because the method survives scrutiny while the data cannot be examined.