hotato
GitHub

VFA-2026-0003

The system fails to detect the caller's speech because voice-activity detection misjudges frame windowing and retained internal state, so the caller appears silent when they are talking.

open2 independent reportslast reported 2026-07-24seen on livekit

What this is

Filed as VAD endpoint misdetection, the name every report of this mode is collected under.

A failure mode is one named thing that goes wrong on a live call. This record carries every public report of it the atlas has found, in each reporter's own words, and a status that moves only when a re-check stores the artifact behind the move. Status open: reported and still open where it was reported.

Evidence

Every independent public report of this mode, newest first: who wrote it, where, when, what they said, and the link back to the post it came from.

  1. kyle_shechtmanon community.livekit.io2026-07-24livekit
    Summary I found that the bundled inference.VAD sometimes fails to detect a clearly audible caller utterance in a telephony recording. The audio was captured correctly, but LiveKit generated no VAD...

    https://community.livekit.io/t/bundled-inference-vad-false-negative-depends-on-32-ms-window-alignment-and-retained-state/1724

    first seen 2026-07-24 · fetched 2026-07-25T17:51:33Z · body sha256 0f2dd3dabf348cde

  2. sampdirectoron GitHub issues2026-03-11
    ❓ Questions and Help I am encountering consistent issues where Silero VAD fails to detect speech or exhibits significantly lower sensitivity when processing female voices compared to male voices,...

    https://github.com/snakers4/silero-vad/issues/765

    first seen 2026-03-11 · fetched 2026-07-25T17:51:05Z · body sha256 c2e3ce78528cdf45

Each quote is at most 30 words around the reported failure and links to the post it came from. If you wrote one of these and want it off this page, the removal path takes it down within 24 hours.

Hit this one yourself? Add your call to this entry: the stack, the versions, and what the caller heard. It lands as another independent report on this page, with your handle and a link back to what you wrote.

Report another occurrence

The form is a GitHub issue on the hotato repo. Prefer email? [email protected] reaches a person either way.

What is measurable

Evidence tier: Atlas record: every field on this page traces to a fetched public artifact.

What it establishes

  • Every report below links to the original post and names the handle that wrote it; the quote is at most 30 words around the reported failure.
  • The status changes only when a re-check stores the evidence link, the quote and the date behind the change.
  • Every timestamp comes from the fetched artifact it describes, recorded with the sha256 of the response body it was read from.

What your trace settles

  • Reproducing the mode on your own stack is the next step: the reports below carry the configuration each reporter was running.
bash
# the timing incidents in one recording, ranked
hotato autopsy ./call.wav

The tier above is what this record establishes on its own: linked sources, an artifact behind every status move, and timestamps that trace to a fetched response. To put a number on your own call, hotato autopsy reads a recording you already have and ranks the timing incidents in it. hotato is MIT and runs locally. getting started.

Status history

A daily re-check reads every source thread on this page. The status moves when that re-check stores the link, the quote and the date behind the move, so every state on this record is one you can open.

The record has carried one status since it opened: open, reported and still open where it was reported. A move lands here with the link, the quote and the date that show it.

Discussion

Reader discussion of this mode: what fixed it, what did not, and what the record here is missing. It is a conversation, not part of the evidence above. The reports on this page are attributed and linked to their sources, and a comment is a comment.

Open this discussion on GitHub

The record

Atlas id
VFA-2026-0003
Mode id
pat_2a36d2f9762944e3073b088b
Content digest
sha256:2a36d2f9762944e3073b088be25bc1c06ecfdf13375926bddb81b21f307a0ef1
First reported
2026-03-11
Last reported
2026-07-24
First seen by the atlas
2026-07-24T17:53:14.628Z
Last re-checked
2026-07-24T17:53:14.628Z
Reported on
livekit
Sources
GitHub issues, community.livekit.io
Scope
2 independent public reports across 2 sources. This entry states where the mode has been reported; where else it can occur is what the next report settles.

References

Every link this entry stands on: the post behind each report, and the artifact behind each status move.

  1. reporthttps://community.livekit.io/t/bundled-inference-vad-false-negative-depends-on-32-ms-window-alignment-and-retained-state/1724 · kyle_shechtman · community.livekit.io · 2026-07-24
  2. reporthttps://github.com/snakers4/silero-vad/issues/765 · sampdirector · GitHub issues · 2026-03-11

Machine surfaces

This entry, for an agent:feed.jsonfeed.atomfeed.schema.jsonatlas.llms.txt

Removal

If you wrote something quoted on this page and want it gone, one email does it. The removal path takes the quote, the handle and the link off this page, out of the feeds and out of the llms.txt within 24 hours, and tombstones the id so the entry cannot quietly return at a new address.