What broke when I shipped a local Whisper dictation app to real Windows hardware

说明与用途

作者构建了 VoxScribe，本地 Whisper 语音识别应用。硬件和驱动问题导致录音无声或崩溃。解决方案：选择 WASAPI 设备、按设备原生采样率录音并后期 16 kHz 重新采样、改为按键录音、预缓存前 0.5 秒音频。应用现已在多种麦克风上稳定运行。

问题

Audio hardware and driver issues caused failures in a local Whisper dictation app on Windows.

结果

The app now reliably transcribes speech from various microphones on Windows, handling sample rate differences, Bluetooth latency, and voice activity detection issues.

工作流

• 1. Detect and select the WASAPI default input device instead of the generic default.
• 2. Record audio at the device’s native sample rate.
• 3. Resample recorded audio to 16 kHz using linear interpolation before feeding it to Whisper.
• 4. Replace automatic VAD with a hold‑to‑talk mechanism; keep VAD code for future use.
• 5. Optionally keep the mic stream open and buffer the last half‑second to avoid clipping the first word.

证据

The first was a Bluetooth headset that recorded near silence. On my machine the sounddevice library picked a default input device that landed on an MME driver, and for my headset that produced audio so quiet that Whisper transcribed almost nothing.

来源

The fix was to ask for the WASAPI default input device explicitly instead of trusting the generic default.

来源

The second was a crash when forcing 16 kHz. Whisper wants 16 kHz audio, so my first version opened the microphone at 16 kHz. That worked on my headset, then failed with an invalid sample rate error on a laptop's internal mic running at 48 kHz.

来源

The fix was to record at the device's own native rate and resample to 16 kHz in software afterward.

来源

I switched to hold-to-talk, so the user decides when speech starts and stops and there is nothing to guess.

来源

I added an opt-in mode that keeps the stream open and holds the last half second in a small in-memory buffer, so a recording starts with audio that is already there.

来源