Ming-3.0-tts vs Qwen-Audio-3.0-TTS: Open Weights Against a Voice You Meter by the Character

Ming-3.0-tts and Qwen-Audio-3.0-TTS are the two most credible Chinese text-to-speech systems released in 2026, and they disagree about almost everything except the quality of their output. Ming-3.0-tts is Ant Group's MIT-licensed open-weight model, published by the inclusionAI team on 20 October 2026 as part of the Ming-3.0 speech family. Qwen-Audio-3.0-TTS is Alibaba's closed, API-only speech synthesizer, announced at WAIC on 20 July 2026 in Plus and Flash tiers with no weights published at all. One you download and run; the other you rent by the character. That difference is the comparison, and the quality gap is smaller than the business-model gap.

There is also a wrinkle that most comparisons of these two models miss, and it changes the recommendation: Qwen-Audio-3.0-TTS is no longer the Qwen speech model you would actually buy. Alibaba replaced it with Qwen-Audio-3.1-TTS on 23 September 2026 and cut synthesis prices by roughly 70% the day before. So this page compares the model named in the title against Ming-3.0-tts, because that is what people are searching for, and then tells you what the newer Qwen changes about the answer.

The model in the title is already superseded

Qwen-Audio-3.0-TTS launched at WAIC with a genuine claim: first place on Artificial Analysis's Provider Voice Arena, ahead of Gemini 3.1 Flash TTS and a long list of commercial systems. It shipped in two tiers — Plus for quality, Flash for real-time interaction with roughly 300 ms first-packet latency — at list prices around $27.60 and $15 per million characters respectively.

Nine weeks later, Qwen-Audio-3.1-TTS arrived at the Apsara Conference. The changes that matter for this comparison:

• Price — synthesis down about 70%, real-time down about 85%, effective 22 September 2026 for the Beijing and Singapore regions. That puts 3.1 TTS Flash at roughly ¥1.5 per million input tokens and ¥12 per million output tokens, and puts the Plus-equivalent near $8 per million characters on the old unit.

• Control — free-form natural-language instructions for emotion, pace and style replace 3.0's 86 inline delivery tags. That is a usability change, not a quality change, and it is the one most likely to affect whether you can ship.

• Cloning — cross-language timbre transfer across Mandarin, Cantonese, English and Japanese, plus direct handling of noisy or reverberant reference audio.

• Verification — no independent arena score at the time of writing. The quality claims for 3.1 are vendor claims.

So the fair framing is not "Ming versus Qwen" but "Ming versus Qwen's current generation, whose price is now roughly a third of what 3.0 charged." Ming's cost advantage narrows accordingly. The architecture difference does not.

Two different products, not two versions of one

• Delivery model — Ming-3.0-tts is MIT-licensed weights on Hugging Face and ModelScope, with inference code in a separate GitHub repository. Qwen-Audio-3.0-TTS publishes no weights; it is served through Alibaba Cloud Model Studio.

• Size — Ming's default checkpoint is 0.5B parameters, dense, on a Qwen2.5-0.5B backbone, about 2.96 GB. Its sibling Ming-3.0-tts-tiny is a 7.9B-total, 1.3B-active MoE on Ant's Ling V3 backbone. Qwen does not disclose parameter counts for either tier.

• Output quality ceiling — Ming tops out at 44.1 kHz. Qwen-Audio-3.0-TTS moved to 48 kHz, and supports one-pass synthesis of up to three minutes.

• Language coverage — Ming covers Chinese, English, German, Spanish, French, Korean and Japanese, plus Sichuanese and Cantonese. Qwen covers 16 languages and 20 Chinese dialect regions, having added Arabic, Vietnamese, Malay and Filipino with 3.0.

• Voices — Ming ships 100-plus Chinese voices and five English ones. Qwen's catalogue is a hosted selection you do not manage.

• Control surface — Ming offers voice design from a text description, a "director mode" for free-form delivery instructions, 14 inline paralinguistic tags, and explicit emotion, speed, pitch and volume controls. Qwen 3.0 offered free-style director prompts plus fine-grained tags; 3.1 replaced the tags with instructions.

The pattern in that list is consistent: Ming gives you more control over a narrower language set, and Qwen gives you broader coverage with less visibility into what is underneath.

Quality: what the arena says, and what it does not

Both models have independent measurements, which is rare enough to be worth using carefully. The trap is comparing across different boards.

On the Provider Voice Arena — models speaking in their own stock voices, which is the like-for-like comparison — Qwen-Audio-3.0-TTS-Plus scored 1,238 Elo in August 2026 and 1,259 by September, ranked second. Ming-3.0-tts scored 1,188 Elo, third among open-weight models and around 18th overall. On that board, Qwen is ahead by roughly 50 to 70 Elo, which is a real but not enormous gap — about the difference between two adjacent tiers of commercial voice.

Ming has two results Qwen cannot match on the same board. It tied for first overall on Pronunciation Robustness at 93.2%, and it ranks first among open-weight models on the Controlled Voice Arena at 1,069 Elo, a board built from eight cloned voices across US and UK accents. Qwen does not appear on the controlled-voice board, because there is no local checkpoint to run that test against.

Read together, those numbers say something specific. Ming is at its best when it is reproducing a voice you give it, and at its weakest when it is drawing from its own small English catalogue. Qwen is strong on its own voices and claims state-of-the-art speaker similarity across all 16 languages — a vendor claim, not an independent one. If your workload is "clone our founder and read the newsletter," Ming's strongest board is the one that matters. If it is "give us 40 voices in 12 languages," Qwen's coverage is the deciding fact.

One vendor-reported number deserves flagging because it is unusual and practical: Qwen-Audio-3.0-TTS throughput was reported at about 16 characters per second, against roughly 120 for Sonic 3.5 and 30 for Simba 3.2. That is slow. It is the reason the Flash tier exists, and it is the kind of limitation a quality leaderboard will never show you. Ming's 0.5B checkpoint has no comparable public throughput figure, which is its own gap.

Cost, in the unit each one charges in

The two models do not share a unit, so the comparison has to be converted before it means anything. At roughly 14 characters per second of speech, a million characters is about 19 to 20 hours of audio.

• Qwen-Audio-3.0-TTS-Plus — $27.60 per million characters, or roughly $1.40 per audio-hour at list price.

• Qwen-Audio-3.0-TTS-Flash — around $15 per million characters, or roughly $0.76 per audio-hour.

• Qwen-Audio-3.1-TTS — after the September cut, roughly a third of 3.0's price, so somewhere near $0.40 to $0.45 per audio-hour for equivalent synthesis.

• Ming-3.0-tts — no per-character price. MIT weights, and a GPU bill instead. A rented H800 at around $2 per GPU-hour, running a 0.5B model well above real time, produces several audio-hours per wall-clock hour; batched, the effective rate falls below what any of the metered prices above can reach at sustained volume.

The crossover is the whole argument. For a few hours of audio a month, self-hosting is a bad deal: the GPU is idle 99% of the time, the dependency stack is a day of work, and the metered API costs less than the electricity. For a few hundred hours a month, the metered API is the expensive option by a wide margin, and the gap widens with every additional hour because the marginal cost of the next generation is nearly zero. Where exactly your crossover sits depends on GPU pricing and utilization, but it is measured in hundreds of hours per month, not thousands.

There is a second cost that does not appear on either price list: the cost of the model changing under you. Qwen-Audio-3.0-TTS was the best speech model Alibaba sold for about nine weeks. Anyone who built a product on its 86-tag control grammar spent September rewriting prompts for natural-language instructions. Ming's MIT weights cannot be deprecated, only improved by you.

Control, cloning and the deployment reality

Ming's voice design is the feature Qwen does not have an equivalent for. You describe a speaker in text — age, timbre, pace, accent — and the model synthesizes a voice to match, without a reference clip. For prototyping a character or a brand voice before you have a recording, that is a genuinely different workflow from picking from a catalogue.

Qwen's counterweight is robustness. Its 3.1 release specifically handles noisy and reverberant reference audio, which is the failure mode that kills cloning in real deployments: someone records a sample on a laptop in a conference room and the clone sounds like a different person. Ming's model card is candid that speaker similarity trails content accuracy, with French the clearest multilingual gap.

Deployment is where the two diverge most sharply in effort.

• Ming — clone the GitHub repository, install CUDA 12.4 and PyTorch, optionally build flash-attn, install pynini for text normalization, and run infer.py or the ming_tts.MingTTS Python API. Hugging Face hosts checkpoints only and says so in a callout. The tiny model needs its own environment. There is no hosted inference provider on Hugging Face at the time of writing.

• Qwen — an API key and a regional endpoint. No infrastructure, no dependency stack, no GPU capacity planning. You also get no ability to pin a version, inspect the model, or run offline.

For a team with an existing GPU footprint and a compliance reason to keep audio in-house, Ming is the obvious choice and the effort is a rounding error. For a team without either, Qwen is cheaper this quarter and more expensive at scale, and the lock-in is real.

Where a router fits

Neither model is on OrcaRouter. We do not host Ming-3.0-tts and we do not resell Qwen-Audio-3.0-TTS, and a comparison page is the wrong place to pretend otherwise. What sits on our side of the pipeline is everything around the voice: the language model that drafts and rewrites the script, plus hosted speech models such as Gemini 3.1 Flash TTS Preview and GPT-4o mini TTS for the cases where self-hosting Ming is the wrong trade.

That matters most for the decision this page is actually about. A voice pipeline is not one model; it is a script generator, a normalizer, a synthesizer and a fallback. Putting the text half behind one API key — 200-plus models, 0% markup on provider list price, automatic failover when a provider degrades — means the only part you are committing to is the voice model itself. If you self-host Ming and it turns out to be weaker on your English brand names than the arena suggested, swapping the voice layer is a change of one component, not a re-platforming. If you build on Qwen's hosted API, the routing layer is what keeps the rest of the pipeline alive when the endpoint is slow or rate-limited, and the pass-through pricing means Alibaba's next price cut reaches you the day it lands rather than at a reseller's convenience.

Which one to pick

• Choose Ming-3.0-tts if you have GPUs, need a cloned or designed voice rather than a catalogue, want MIT terms that survive legal review, and can accept research-grade tooling and a thin English voice set. It is the only option here that you can own outright.

• Choose Qwen-Audio-3.0-TTS only if you are pinned to it for a specific reason — an existing Alibaba Cloud contract, a workflow built on its 86-tag grammar. Otherwise you are choosing a superseded model at a superseded price.

• Choose Qwen-Audio-3.1-TTS if you want a managed, broad-coverage voice API and the September price cut changes your economics. Accept that it is unverified on independent leaderboards and that its instruction-based control is a new grammar you will be learning.

The quality gap between the two families is narrow enough that it should not decide the question. On the one board where both compete directly, Qwen leads by roughly 50 to 70 Elo. On the boards that measure cloning, Ming is at the top and Qwen is absent. What actually separates them is whether the voice is a service you rent or an artifact you own — and after Alibaba replaced its own flagship in nine weeks, that distinction looks less like ideology and more like procurement risk.