The 4.5M Voice Model That Never Heard a Human Speak
i keep coming back to one line in the model card. "No recording of a real speaker is involved." Both voices in tiny-voca were generated by another model. Qwen3-TTS made the audio, and this thing learned from that audio.
i keep coming back to one line in the model card. "No recording of a real speaker is involved."
Both voices in tiny-voca were generated by another model. Qwen3-TTS made the audio, and this thing learned from that audio. So before it said a single word, it had only ever heard a machine.
That is a strange way to build a voice.
Muhammed Nazeem published tiny-voca on November 14. It has 4.5 million parameters. The file is 18 MB. It runs about 70 times faster than real time on four CPU threads, and it runs in a browser tab.
The whole project cost $9.56 in GPU time. That covers the dataset, the failed attempts, and the final training run.
i have spent more than that on lunch and regretted it.
The reaction was quick. 468 GitHub stars in a day. 94 likes on Hugging Face. A 32-comment thread on r/LocalLLaMA where nobody is arguing about voice quality. They are arguing about how something this small exists at all.
What 4.5M parameters buys
Here is the whole model, split up:
| Piece | Parameters |
|---|---|
| Text encoder | 1,588,864 |
| Frame transformer B | 1,985,984 |
| Frame transformer A | 795,971 |
| Duration predictor | 123,906 |
| Waveform head | 25,862 |
| Embeddings | 16,704 |
The waveform head is the interesting row. 25,862 parameters. Most TTS systems spend millions on a neural vocoder to turn math into sound. tiny-voca uses a source-filter synth instead.
A pulse train at the predicted pitch, plus a noise signal, each shaped by a filter the network predicts once per frame. That is it. Classic speech synthesis wiring, attached to a small transformer.
It should sound terrible. It mostly doesn't.
It learned from a model, not a person
i used to think "trained from scratch" meant "trained on the internet." Not here. The dataset is 16,018 clips and 17.6 hours, and every second came out of Qwen3-TTS.
The pipeline is short:
- Write a description of a voice, let Qwen3-TTS design it.
- Generate all the audio with Qwen3-TTS 1.7B.
- Phonemize the same text with dizione.
- Force-align the audio with wav2vec2 to get phoneme lengths.
- Train tiny-voca on the pairs.
Step 4 is the only place a real recording enters the picture, and even then it is just a labeler. No human voice lives in the weights.
The training data is synthetic, so the model cannot be more natural than the model that generated it.
Nazeem wrote that in the limitations himself. A Redditor named Waarheid heard it right away. He said you can hear the Qwen3-TTS in it, sounding like English anime dubs.
That is a real ceiling. But it is also why the bill was $9.56 and not $90,000.
Seven and a half hours on one rented RTX 4090. i keep failing to make that feel normal.
The boring part is the best part
The most praised piece of this project is not the model. It is the phonemizer.
dizione is 5.4 MB of NumPy and data files. A 125,000-word dictionary, rules for numbers and dates and money, context checks for words like "read" and "live," and a small model for anything unknown. It handles about 4,400 sentences a second.
One Reddit comment nailed why this matters:
It specifies RTX "forty ninety" and "four thousand and ninety" correctly based on context.
That is the thing everyone skips. Turning text into sound is easy. Turning text into the right sound is a dictionary problem, not a neural network problem.
python -m dizione --words "Dr. Patel paid $12.99 on 3/14."
Try that sentence in your own TTS wrapper and see what comes out.
Where it falls apart
A user called PrestigiousBag2994 did exactly what Nazeem asked and stress-tested the demo. The list is brutal and specific:
- "Emmaleigh" drops the last syllable
- "Hermione" gets an extra syllable in the middle
- "She's a well-read girl" uses the wrong "read"
- European number formatting fails
- Coeliac, celiac, scabies, and lyssavirus all break
Nazeem did not get defensive. "Names and medical words are the weak spot, they are mostly not in the dictionary so the model has to guess."
The same text is always read the same way. No prosody sampling, no variation, no streaming. And the audio peaks above 1.0 in roughly one sentence out of twenty, so you have to scale it before saving.
The word error rates look great until you read the fine print. 0.6% on validation and 0.9% on test, but those sets are 8 clips each. No formal listening test has been run.
But none of that stopped 468 people from starring the repo in a day.
One commenter did find something it gets right. "It pronounces WWE correctly. Unlike a certain infamous video." Two decades of speech research and the test we all actually run is a console name.
Who should actually use this
Here is the part i find genuinely useful.
If you are building an agent that needs a voice, you have two options today. Call an API and pay per character, or ship a 200 MB model that wants a GPU. tiny-voca is a third path. 21 MB of ONNX, no network call, no GPU.
Think about what that gets you:
- a reading assistant that works on a plane
- an accessibility feature with zero backend cost
- a voice for a toy or a kiosk with no cloud bill
- anything running on a Raspberry Pi
The privacy angle is the real one. The demo page runs the model locally, and nothing you type leaves the device. For plenty of products that is not a nice-to-have. It is the only version of the feature that ships at all.
i have a soft spot for the "$9.56, less than a pizza" line in that README.
Partly because it is honest about scale. Nobody is pretending a weekend project competes with a funded lab. It just costs what it costs, and here is the receipt.
And partly because the tools i use every day came from exactly this shape of project. One person, a donation link, no roadmap. ffmpeg. sqlite. Half the terminal utilities i have installed and forgotten the names of.
The pattern is always the same. Somebody gets annoyed enough at one specific problem to solve it badly, then keeps going until it is good.
When not to use it
Most people do not need this.
If you are producing an audiobook, a podcast, or a narration track, tiny-voca is the wrong tool. Two voices, slightly synthetic, no emotion control, no cloning. Pay ElevenLabs or OpenAI and get something a listener will not flinch at.
Also, the benchmarks are eight clips. Anyone quoting "0.0% word error rate" as a result is overselling a sanity check, and the author says so in the model card.
And the phonemizer is English only. The "just train it for Arabic" advice in that thread is doing a lot of hand-waving. You need a whole new front end before the model is even relevant.
Someone in the comments mentioned an 8M Turkish model called Antalia. It needed 1,500 hours of audio and still sounded bad on a small corpus. This is not a solved problem.
i would not put this in anything handling medical instructions or money. Not yet.
What is left
What i keep thinking about is the 18 hours of training audio. A person recorded nothing. One model designed two voices from text prompts. Another spoke 16,000 sentences. A third learned to imitate that imitation.
And the result is 18 MB that runs on a phone.
At some point a decent synthetic voice costs less than the electricity to run it. i do not know what happens after that. i do want to hear what it sounds like when someone trains one of these on a language that never had a TTS model at all.
Somebody in that thread already asked about Arabic. i hope they actually do it.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.