April 22, 2026•1 min read•from Machine Learning

I can't believe text normalization is so underdiscussed in streaming text-to-speech [D]

Our take

Text normalization in streaming text-to-speech (TTS) is surprisingly underdiscussed, yet it plays a crucial role in the effectiveness of these models. While users often seek natural-sounding voices and high-quality output, many TTS systems stumble over basic elements like dates, URLs, and promo codes. I recently found a benchmark comparing commercial real-time streaming TTS models based on their handling of these challenges. This analysis, which evaluates over 1,000 sentences across 31 categories, highlights the industry’s pressing need for robust solutions.

Kinda suprises me how little discussion there is around about mistakes in streaming TTS models

People look for natural readers, high voice quality, expressive speech. And most models don't look dumb here and fail. They fail when you give them basic stuff like price, dates, URLs, promo codes, phone numbers.

So I was looking for some info and found a benchmark that compares commercial real time streaming TTS models in terms of how they pronounce dates, URLs, acronyms, etc. They are checking 1000+ sentences in 31 categories then use Gemini to see how results came out. https://async-vocie-ai-text-to-speech-normalization-benchmark.static.hf.space/index.html . Looks valid to me.

Obviously this is a vendor benchmark so I am not taking it for granted but the focus feels on point.

This has been one of the biggest challenges for us in the production.I am curious how you guys deal with it in practice.

submitted by /u/lilitbroyan
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article →

I built a real-time pipeline that reads game subtitles and converts them into dynamic voice acting (OCR → TTS → RVC) [P]I've been experimenting with real-time pipelines that combine OCR + TTS + voice conversion, and I ended up building a desktop app that can "voice" game subtitles dynamically. The idea is simple: - Capture subtitles from screen (OCR) - Convert them into speech (TTS) - Transform the voice per character (RVC) But the hard parts were: - Avoiding repeated subtitle spam (similarity filtering) - Keeping latency low (~0.3s) - Handling multiple characters with different voice models without reloading - Running everything in a smooth pipeline (no audio gaps) One thing that helped a lot was using a two-stage pipeline: While one sentence is playing, the next one is already processed in the background. I also experimented with: - Emotion-based voice changes - Real-time translation (EN → TR) - Audio ducking (lowering game sound during speech) I'm curious: How would you approach reducing latency further in a multi-model setup like this? Or is there a better alternative to RVC for real-time character voice conversion? Happy to share more technical details if anyone is interested. submitted by /u/fqtih0 [link] [comments]

I can't believe text normalization is so underdiscussed in streaming text-to-speech [D]

Related Articles