π§ Troubleshooting¶
Golden Rule
For any problem, the first step is always to check system logs.
bash
# View logs in real-time
tail -f ~/.local/state/v2m/v2m.log
π Audio and Recording¶
No sound / Empty transcription¶
- Symptom: Recording starts and stops, but no text is generated.
- Diagnosis: Run the audio diagnostic script:
- Solutions:
- Audio Driver: Voice2Machine uses
SoundDevice. Make sure your system (PulseAudio/PipeWire) has an active default microphone. - Permissions: On Linux, your user must belong to the
audiogroup (sudo usermod -aG audio $USER).
Cut-off or incomplete phrases¶
- Cause: The silence detector (VAD) is too aggressive.
- Solution:
Adjust settings in
config.tomlor via the GUI: - Reduce the
threshold(e.g., from0.35to0.30). - Increase
min_silence_duration_ms(e.g., to800ms).
π’ Performance and GPU¶
Slow transcription (> 2 seconds)¶
- Probable Cause: Whisper is running on CPU instead of GPU.
- Verification:
- Solution:
- Install updated NVIDIA drivers (CUDA 12 compatible).
- Verify
config.tomlhasdevice = "cuda". - If you don't have a dedicated GPU, switch model to
distil-medium.enorbase.
Error CUDA out of memory¶
- Cause: Your GPU doesn't have enough VRAM for the selected model.
- Solution:
- Change
compute_typetoint8_float16(reduces VRAM usage by half). - Use a lighter model (
distil-large-v3consumes less than originallarge-v3).
π Connectivity and Daemon¶
"Connection refused" in GUI or Scripts¶
- Cause: The backend process (Python) isn't running or the server crashed.
- Solution:
- Verify status:
- If not running, start manually to see startup errors:
- If it says "Address already in use", kill the existing process:
Keyboard shortcuts don't respond¶
- Cause: Permission issue or incorrect path in window manager configuration.
- Solution:
- Run the script manually in terminal:
scripts/v2m-toggle.sh. - If it works, the error is in your shortcut configuration (e.g., relative path
~/instead of/home/...). - If it doesn't work, verify permissions:
chmod +x scripts/*.sh.
π§ AI Errors (LLM)¶
Error 401/403 with Gemini¶
- Cause: Invalid or expired API Key.
- Solution: Regenerate your key at Google AI Studio and update the
.envfile orGEMINI_API_KEYenvironment variable.
"Connection refused" with Ollama¶
- Cause: The Ollama server isn't running.
- Solution: Run
ollama servein another terminal.