Back to News
Advertisement
ttoebee about 4 hours ago 10 commentsRead Article on narilabs.com
Hey HN, Toby from Nari Labs here.

We've been working on making OSS speech models super-fast. Last year, we built Dia, the first OSS text-to-speech model capable of doing natural dialogue. Since then, so many more great speech models have been released to the public.

But the market is still dominated by closed source models. We think that's an inference problem. Existing systems such as vLLM / SGLang are not well suited for multimodal inference. To prove this, we built an inference engine specialized for Qwen3-TTS and open-sourced it (https://github.com/nari-labs/nari-qwen3-tts). Running at sub-50 ms latency at 10 RPS, this showed open models can be run much faster and cheaper.

Since then, we've been working hard to bring cheap, fast, and high quality serving to all. And we've even beat closed models at their game!

Measured on the highly cited Coval (YC S24) voice AI benchmarks, our Qwen3-TTS endpoint not just is #2 in latency, but #1 in accuracy (WER) compared to 11Labs, Cartesia etc. while being the cheapest endpoint. Our Qwen3-ASR endpoint has the lowest latency and #2 accuracy, just 0.1% away from #1. It is the second cheapest model on the list.

It took a lot of clever inference engineering to make these models quick, perform well while keeping costs low. Interestingly, Alibaba's official endpoints seem to perform worse in terms of accuracy and latency compared to ours. But nonetheless, much love to the Qwen team for OSS-ing these amazing speech models.

We want to continue to push prices down to make speech technology a commodity - so that every app can have great TTS and STT without worrying about unit costs. We're also working on other parts of audio such as diarization - as well as video and world model inference. More to come!

Advertisement

⚑ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 238 words in the discussion.

Trending Topics

#tts#https#asr#gemma#cool#something#models#clip#model#inference

Discussion (10 Comments)Read Original on HackerNews

mowmiatlasβ€’about 2 hours ago
Cool, I’ve released something to the same beat of the dr this weekend as well

https://github.com/loudreader/loudkit

I think real time natural tts should be possible everywhere soon

iharnoorβ€’about 1 hour ago
By next month the competition for TTS will be even more!

Voice models are not winner take all market unlike LLM APIs

Coming here as Developer Relations at AssemblyAI

rahimnathwaniβ€’about 2 hours ago
For some reason it switched voices half way through a 33 second clip.

For OP the clip name is nari-nina-01a0a12f-980a-765e-8029-fa56bd23210d.wav

asaiacaiβ€’about 3 hours ago
This is really cool work! I'm curious like what do you see as the biggest lever for speeding up TTS models or from a technical perspective that this was a promising direction in the first place to push on. If I were to guess, some distillation but I'm certain there are probably TTS model aware architectural changes that just make inference wayyyy faster?
ipsum2β€’about 2 hours ago
If you're going to announce a TTS model, service, or whatever, you really need demos.
yoloakkiβ€’about 1 hour ago
You definitely need independent evals by Datapoint AI or someone who can verify your claims about TTS quality
DylanMerigaudβ€’about 1 hour ago
Rooting for you on this one.
meatmanekβ€’about 2 hours ago
> and Qwen3-ASR

Is the ASR inference engine open source as well?

nshmβ€’about 1 hour ago
Yes, and it is very good one. Leading position on private leaderboard on HF: https://huggingface.co/spaces/hf-audio/open_asr_leaderboard
verdvermβ€’26 minutes ago
They have a number of demos and examples in their HF space

https://huggingface.co/Qwen/spaces

I saw a local-ai demo (something + gemma), where the person used ASR to get text and gemma to clean it up (like turning "question mark" into a literal "?", bullet points another one). The presenter also showed a gemma only option, that did both in one go, but had a higher WER on average, and even though the formatting statements were handled without a multi-stage pipeline, they preferred the multi-stage overall