ESpeak-ng: speech synthesizer with more than one hundred languages and accents

Original Article ↗ Hacker News Discussion ↗

Audio Quality, Tradeoffs, and Use Cases

  • Many commenters react to demos as “robotic” and reminiscent of decades‑old tech, especially compared to modern neural voices from big providers and browsers.
  • Others argue this is intentional: espeak‑ng prioritizes clarity, speed, small size, and responsiveness over naturalness, especially for screen reader usage.
  • There is disagreement over whether this is still the right tradeoff given modern CPU power and storage.

Classic Formant Synthesis vs Neural TTS

  • Espeak‑ng uses formant synthesis, an older technique modeling the vocal tract, vowels, and consonants with simple signals and rules.
  • Some see value and elegance in these classic, theory‑driven systems and worry that end‑to‑end neural models sacrifice understanding for brute‑force imitation.
  • Others propose hybrids: small neural models controlling a formant synth or other constrained vocoder to get high quality at very low bitrates and model sizes.

Accessibility Perspectives

  • Several blind users report using espeak‑ng (and similar synths) all day across devices, preferring it over “natural” voices.
  • Key benefits cited: extremely low latency, high intelligibility at very high words‑per‑minute, and strong predictability of pronunciation, which reduces cognitive load.
  • Another user with dyslexia and auditory processing issues finds classic TTS unusable and says neural TTS dramatically improved reading endurance and accuracy.
  • Overall theme: “quality” depends heavily on whether the goal is fast, reliable access vs. pleasant, humanlike narration.

Project State and Technical Debt

  • Espeak‑ng is described as critical for accessibility and a rich multilingual knowledge base, but with a difficult, aging C codebase.
  • Noted issues include a hand‑rolled XML/SSML parser interleaved with language logic, complex control flow, and multiple inconsistent phoneme APIs.
  • Suggested improvements: add tracing/logging, front it with a real XML parser, and gradually untangle or replace legacy parts, but developer time and funding are limited.
  • Some related projects (e.g., Piper) currently depend on espeak‑ng for phonemization but may move away due to licensing and maintenance concerns.

Language Coverage and Bugs

  • The project advertises support for 100+ languages, but specific bugs exist, e.g., Mandarin output reading tone numbers in English after characters.
  • Linked issue trackers indicate this behavior is known but not fully resolved; coverage vs. quality varies by language.