Voice: local Whisper model missing from container, Kokoro TTS setup needed #11

Open
opened 2026-04-28 12:19:55 +00:00 by mik-tf · 0 comments
Owner

Problem

  1. Local Whisper STT: HERO_VOICE_STT_LOCAL=true is set in hero_voice.toml but the model file /data/models/whisper/ggml-tiny.en.bin does not exist in the container. Transcription falls back to Groq cloud.

  2. Kokoro TTS: hero_agent tries Kokoro (local) first for TTS, but the Kokoro service is not deployed/configured.

What works now

  • Groq Whisper cloud STT (via API key) — works as fallback
  • Groq Orpheus TTS — works as fallback
  • Voice transcription endpoint responds correctly

What's needed

  1. Add Whisper model download to the build pipeline (or entrypoint)
  2. Configure and deploy Kokoro TTS service
  3. Ensure provider selection in the voice UI works (whisper_local vs groq_whisper)
  4. Test both local and cloud paths

Priority

P3 — cloud fallbacks work. Local models are for privacy/latency.

Signed-off-by: mik-tf


Originally filed as home#114 on 2026-04-12 by mik-tf — moved to hero_demo as part of consolidating issue tracking.

## Problem 1. **Local Whisper STT**: `HERO_VOICE_STT_LOCAL=true` is set in hero_voice.toml but the model file `/data/models/whisper/ggml-tiny.en.bin` does not exist in the container. Transcription falls back to Groq cloud. 2. **Kokoro TTS**: hero_agent tries Kokoro (local) first for TTS, but the Kokoro service is not deployed/configured. ## What works now - Groq Whisper cloud STT (via API key) — works as fallback - Groq Orpheus TTS — works as fallback - Voice transcription endpoint responds correctly ## What's needed 1. Add Whisper model download to the build pipeline (or entrypoint) 2. Configure and deploy Kokoro TTS service 3. Ensure provider selection in the voice UI works (whisper_local vs groq_whisper) 4. Test both local and cloud paths ## Priority P3 — cloud fallbacks work. Local models are for privacy/latency. Signed-off-by: mik-tf --- *Originally filed as [home#114](https://forge.ourworld.tf/lhumina_code/home/issues/114) on 2026-04-12 by mik-tf — moved to hero_demo as part of consolidating issue tracking.*
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_demo#11
No description provided.