Skip to content

Comments

feat(tts): switch default model from vctk_vits to vits (LJSpeech)#82

Open
dzianisv wants to merge 1 commit intomainfrom
feat/switch-default-tts-to-vits
Open

feat(tts): switch default model from vctk_vits to vits (LJSpeech)#82
dzianisv wants to merge 1 commit intomainfrom
feat/switch-default-tts-to-vits

Conversation

@dzianisv
Copy link
Owner

Summary

  • Switch default Coqui TTS model from vctk_vits (~9GB memory) to vits (LJSpeech, ~1-2GB)
  • Default voice changed from p339 to default (single speaker model)

Changes

  • shared/src/schemas/settings.ts: Default voice p339default
  • scripts/coqui-server.py: Default model → LJSpeech, reordered model list
  • backend/src/services/coqui.ts: Same default model change and reordering
  • frontend/src/components/settings/TTSSettings.tsx: Updated fallback model
  • README.md: Updated default model/voice references

Why

The vctk_vits model loads all 109 speaker embedding vectors into GPU memory (~9GB on MPS) even when only one speaker is used. The vits (LJSpeech) model uses ~1-2GB — a 7GB reduction with no quality loss for single-speaker use.

Switch default Coqui TTS model from vctk_vits (multi-speaker, 109
speakers, ~9GB memory) to vits (LJSpeech, single speaker, ~1-2GB).
The vctk model loaded all 109 speaker embeddings into GPU memory even
when only one speaker was used.

Changes:
- Default model: vctk_vits -> vits (LJSpeech)
- Default voice: p339 -> default (single speaker, no selection needed)
- Model lists: LJSpeech now listed first as recommended
- Documentation updated with memory usage notes
@github-actions
Copy link

⚙️ Settings E2E Test Recording

Screencast

Run #22028822222 | Commit 7ffb188

@github-actions
Copy link

🎥 Browser E2E Test Recording

Screencast

Run #22028822222 | Commit 7ffb188

@github-actions
Copy link

🔔 Push Browser E2E Test Recording

Screencast

Run #22028822222 | Commit 7ffb188

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant