XTTS is still being downloaded almost 5m times every month and 2.1m only on HF.
It is greater than many recent hyped models.
Hope people use it well for that to worth to my burnout that I’m still recovering from.
Coqui has been one of the most successful broke startups
Small CPU TTS bench updates
- Now with UTMOS
- PiVo-1.4M: 5 ms to first audio, 9x real time
- Inflect-Micro-v3: 11x real time, 0.8% WER
- Supertonic 3: UTMOS 4.47
Kokoro-82M missed real time.
erogol.com/small_tts_bench/
A 4-min explainer on "Weight-Space Programming":
• MIT's Sparks of WSP (GPT-6 Astra)
• @roicohen9: one paragraph in, a Qwen weight update out
• @HyunjongOk: sparse tables, ~1,800× fewer params
(Narrated by Phonon 31M )
1/ We still don’t have a simple picture of how even 2-layer MLPs learn features. In a new paper with @berkott3 and @learning_mech, we propose a simple, solvable model of shallow MLP training, and find that real MLPs roughly follow it. 🧵
⚠️ Numerical issues can go on silently for decades like in the softmax/CE! Similar issues are present in other widely-used divergences like the KL and JSD
I just posted this paper overviewing what they are and how to fix them:
📚 arxiv.org/abs/2611.18511
Hi all, I have a new result I'm excited to share. It turns out that *all existing implementations* of softmax and cross-entropy (that's JAX, PyTorch, textbooks, etc) have a subtle bug --- two bugs, actually. A simple rewrite fixes both, and eliminates "slingshots" when grokking:
🚀 Stop using Transformers for weight-space programming
If you are not training with gradients on a GPU, why default to a Transformer?
When an LLM writes network weights directly, letting it also design the architecture achieves:
📉 ~1,800× fewer parameters at matched accuracy on ARC (AI2 Reasoning Challenge), compared to the best Transformer the same LLM wrote.
⚡ Up to 17× faster GPU inference with a memory architecture built for these tables, compared to a Transformer of the same size.
🧵 Paper & code at the end 👇
Added tiny-voca to my small CPU TTS benchmark.
4.5M params, Apache-2.0. On 1 CPU thread:
- 117 ms to first audio
- 37x real time
- 3.3% WER
- 666 MB memory
2nd fastest of 13 models. Phonon 31M stays my pick for live voice.
Hear all: erogol.com/small_tts_bench/
Small CPU TTS Benchmark
12 tiny TTS models on 1 CPU thread, 60 audio samples.
My Pick -> Phonon 31M @GradiumAI. 82 ms to ttfa, 4x rtf, 1.6% WER, 363 MB, Apache-2.0.
Pocket TTS, same box: 286 ms, 1.2x, 1347 MB.
Let me know any models i missed
erogol.com/small_tts_bench/
Machine Learns - 81 🤖
• Weight-Space Programming: a closed LLM edits raw weights
• WaveGen: TTS with no codec or vocoder
• Decode Before You Hear
• Latent Sparse Attention
• Agentic Backdoors
• Mistral Large 4
• My small CPU TTS benchmark
erogol.substack.com/p/machin…
The Kimi K3.1 Pro is a beast!
It’s enough for 99.9% of AI work in a company and there’s no reason to pay premium for Claude or OAI.
I’ve tried to find any shortcomings but I can’t seem to find any.
Gemini iOS app is embarrassingly bad.
I tried to use it after a long time.
Got 3 connection errors after a long wait
Now I reached my limit and can’t ask anything