Loading video...
Video Failed to Load
If you're looking for a weekend project, how about training your own text-to-speech model from scratch on your own GPU, and then running it on any device's CPU? We just open-sourced the entire Pocket TTS training stack: data pipeline, recipes, and evals. It learns pretty damn fast: ~15k steps:... show more
106,234 views • 1 month ago •via X (Twitter)
34 Comments

Thanks for releasing the training code it matches what i was doing. only issue was mine kept blabbering and eos token prediction had issues

PocketTTS --- the fastest model in the audio.cpp Arena!

Love Pocket, but can you train the English model to say "live" with a hard "i" when appropriate? In my experience, it incorrectly says it with a soft 'i' 90% of the time.
Anyone interested in doing Slovenian?

would really love to see audio tags on a kyutai model one day!

Vous êtes des crack 🫡

crazy release! thank you

Training TTS on one GPU and running it on CPU is a killer open stack.

you guys are cracked-- keep it up!

Wow. Under $200 to train a useful TTS model from scratch is way more accessible than I expected. How much clean speech data do you need before it starts sounding natural in a new language, not just reading it correctly?

i like the open approach here. training recipes plus cpu inference makes this a practical tts project.

does the 50k step number hold for a language with way less data? romanian is my usual wall

You made my day 😁

Running inference on any device's CPU is the part I care about, that's the difference between a demo and something you'd actually ship inside a product.

love it!!!

That's cool 🔥

thats what i was waiting for so long

Amazing, thanks 🔥🙌

There goes my $300

exciting, thanks!

Thank you You made my day

So are you saying any language TTS can be built with this stack? Isn’t the tokenizer dependent on language?

The step-count breakdown is the useful part: WER under 1% at ~50k but not sounding synthetic until ~200k means intelligibility and prosody are separate curves, and WER alone says you're done long before you are.

thank you 🙏🏼

Finally the wait is over!

cpu latency is mostly memory bound, so model size decides whether this ships

@kyutai_labs I am not very tech savy and I am trying to learn python but it will be quite sometime before I can do these things is there any way for you guys to release a version or some way where we can train our own voice in the browser like via browser inference

thanks for this 🤑

< $200 for a full TTS train is the part I keep thinking about. that's the 200k-step run on rented H100s?

Amazing 🤩 thanks thanks thanks!

Open-sourcing recipes and evals turns TTS from an API dependency into a reproducible lab experiment. The next frontier is voice quality, latency, and footprint together; WER under 1% is one axis when an agent must speak on CPU in real time.

Hi guys, I decided to train this model on my MacBook, and the README invited a bug‑fix PR because it wasn't supported out of the box, so I opened one after making it possible to train on my MacBook, but the maintainer closed it, saying that was an oversight since they can't support platforms they have no hardware to test. I hold no grudge; his comment ended warmly, and I just want to share it here in case anyone wants to use it to train on a Mac as well.

i might try!

under $200 for a full run is way lower than i would have guessed
