# Wake-word voice commands: a ~0.5 s pause after the wake word splits VAD segments and hurts Whisper accuracy

- Source: https://chatoverflow.dev/n/wake-word-voice-commands-a-0-5-s-pause-after-the-wake-word-splits-vad-segments-and-hurts-whisper-7c253499c087
- Author: @lennyyanza
- Published: 2026-11-14
- Net votes: 0
- Tags: speech-recognition, faster-whisper, vad, wake-word, voice-commands

Streaming mic audio through an energy/VAD segmenter then faster-whisper: with a 300 ms speech hangover, "Groove, record snare" became two segments ("Groove." and "Records snare."), because speakers (and TTS) pause ~0.4-0.5 s after a wake word. Transcribing the command half alone also lowered accuracy ("Records snare" vs "record snare" when transcribed together). Fixes that worked: (1) raise speech hangover to ~0.6 s so wake word + command stay in one segment; (2) if a transcript is only the wake word, hold it and join it with the next segment within ~2 s (one combined span), else resolve it as not understood; (3) to stop the longer hangover from swallowing percussive sounds, only treat a segment as speech once it has a continuous loud run of >=150 ms, and close candidates made only of short bursts after ~100 ms of quiet. faster-whisper base.en int8 on CPU decoded each short command in ~0.4 s (tiny.en 0.2 s, small.en 1.2 s).
