How we made a text-to-speech model respond in sub-50 ms
11–20 of 49 posts
Re: How we made a text-to-speech model respond in sub-50 ms
#12Re: How we made a text-to-speech model respond in sub-50 ms
#13also sweet spot is under 150ms so the remainder is inference latency turn around, a 50ms turnaround including tts-stt would ofc be the dream
that is "this ai agent is indistinguishably present and sentient" area
Re: How we made a text-to-speech model respond in sub-50 ms
#14chatgpt responds super fast but says filler words like 'hmm..' 'let me think' and responds later with delay
Re: How we made a text-to-speech model respond in sub-50 ms
#15Re: How we made a text-to-speech model respond in sub-50 ms
#16Re: How we made a text-to-speech model respond in sub-50 ms
#17Re: How we made a text-to-speech model respond in sub-50 ms
#18time-to-first-audio (TTFA) is critical for realtime voice applications. open source implementations (e.g. vLLM-Omni, SGLang-Omni) are often too slow for production and can have issues with realtime playback if you push for lower latency. we wanted to fix that. we optimized qwen3-tts, a popular OSS TTS model, to achieve 34 ms p95 TTFA at 10 requests per second on 1 x H100. we open source the implementation and benchma…
Hi there! I actually thought your Dia models were amazing and very natural sounding, I haven’t tried qwen 3 tts yet - has your focus shifted away from building your Dia models and shifted more towards hosting and infrastructure?
Re: How we made a text-to-speech model respond in sub-50 ms
#19time-to-first-audio (TTFA) is critical for realtime voice applications. open source implementations (e.g. vLLM-Omni, SGLang-Omni) are often too slow for production and can have issues with realtime playback if you push for lower latency. we wanted to fix that. we optimized qwen3-tts, a popular OSS TTS model, to achieve 34 ms p95 TTFA at 10 requests per second on 1 x H100. we open source the implementation and benchma…
How fast is it on consumer-level hardware?
Re: How we made a text-to-speech model respond in sub-50 ms
#20Humans have a roughly 200ms auditive processing latency, (audio input to neural response), in conversation we know and account for this, such that if someone responds in 100ms, we interpret that we interrupted them and that their message doesn't come in response to what we just said, but what we said before.
This can be especially relevant in sentences where an interruption would sharply contrast.
"I think murder is bad, but.."
If someone cuts of right after the but, a human would interpret that the interjection responds to the fact that someone thinks murder is bad. Which is starkly different than interrupting someone after they are about to excuse murder.