Comment by kzahiri

Comment by kzahiri

I built this expecting the opposite. A lot of voice AI is being pointed at elderly callers right now, and the assumed risk is that the model mishears them, so I went to measure how bad it is.

It isn't bad. On 2,760 Common Voice clips, with age brackets matched on accent, gender and speaker so age is the only thing varying, Whisper large-v3 gets 4.67% WER on speakers in their seventies against 6.53% for twenty-somethings. Substitutions, deletions and insertions all fall with age. Deletions in particular don't rise, which is what you'd see if quiet speech were being dropped.

Since Whisper's decoder is a language model and could plausibly be repairing older speakers' word choices rather than hearing them better, I re-ran the same clips through wav2vec2, which is pure CTC with no decoder and no LM: 10.30% for the sixties against 14.23% for the twenties. Larger effect, same direction. So it's acoustic, not a decoder artifact.

Where age does hurt is turn-taking. Voice agents end your turn after a fixed stretch of silence, typically 500-800ms. At 700ms, 8.0% of twenties utterances contain an internal pause long enough to be misread as end-of-turn, versus 19.7% for the sixties. Older speakers take about twice as many pauses inside a single utterance. WER is structurally blind to this: the words that arrive are transcribed correctly while the speaker gets cut off.

A maintainer corrected me on that and he was right. Mark Backman at Daily/Pipecat pointed out that production stacks don't endpoint on a bare VAD threshold anymore. Pipecat's default is smart-turn, a semantic model that listens to the waveform. So I measured smart-turn v3 on the same clips: the gap halves to +5.9pp and stops excluding zero. The fixed-threshold result describes a real and common configuration, not every configuration, and the README says so above the fold.

Things that mattered methodologically, mostly because they nearly produced wrong answers:

- One Common Voice contributor holds 9,792 clips in a single shard, and about seven people account for half the 60+ audio. Uncapped, a "bracket" is a description of one person. Capped at 25 clips each; all intervals bootstrap over speakers, not clips.

- The corpus's younger contributors skew non-native, so age and accent are entangled. Brackets are matched on the (accent, gender) pair. I also spent a while believing accent explained the whole result, based on a 40-clip pilot; at full sample it moves WER by at most 0.44pp. The wrong claim is corrected in the README rather than deleted.

- My first VAD was manufacturing the headline. A relative-energy threshold called breathy trailing-off speech "silence", and breathiness correlates with age, so the detector's error was correlated with the variable under study. WebRTC VAD disagreed on 36% of the eighties clips. Both are now recorded.

- fp16 on MPS is verified against fp32/CPU rather than assumed, because a quantised Whisper KV cache can take large-v3 from 1.91% WER to 100%.

There's a fourth result in there that's really about a different industry. Several startups now sell daily phone check-ins for older adults claiming to detect cognitive decline from "voice biomarkers". Validating that needs gated clinical corpora, but the within-speaker noise floor doesn't. Pause features vary about 99% within the same speaker, frequently within one sitting. Getting a 10% shift in total pause time above that noise takes roughly 19 days of daily calls per reading, so a "six-week trend" is two or three noisy measurements. Speech rate needs under one call. Pause metrics are the most-cited biomarker and the least usable for per-person drift.

Limits, stated because they're real: Common Voice's older speakers are volunteers who chose to record themselves, so this is healthy aging, not clinical. It's read speech, not conversation. And the disordered-speech follow-up is blocked on corpus licensing — TORGO and UASpeech need signed agreements and their HuggingFace mirrors look like unlicensed redistribution, so I didn't use them. The one openly-licensed option turned out to be fixed 3-second podcast excerpts where 74% start mid-speech, which makes the pause metric meaningless on it. That failure is written up in METHOD.md instead of being quietly dropped.

Everything runs locally, no API key, no spend.

Replies kzahiri · 2026-08-07
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.