
What happened
AWS detailed deploying Qwen3-TTS-12Hz-1.7B-Base from Alibaba Cloud's Qwen team via Amazon SageMaker JumpStart to a managed real-time endpoint. It clones a voice from a few seconds of reference audio, in 10 languages, with cross-lingual cloning.
Why it matters
Teams can now produce speech in a chosen speaker's voice, in any of 10 languages, from just a few seconds of reference audio — without retraining a model or collecting large training datasets.
What to watch
Whether deployments stay inside the roughly 24 GB GPU the walkthrough uses — the setup hinges on splitting GPU memory correctly between the talker and code2wav stages. Watch the KV cache token budget of 56,928 tokens for concurrency.
WHO IT HITSMedia teams, educators, and application developers who build personalized voice experiences or localize multilingual content can now run voice cloning on their own managed AWS endpoint. Contact-center and virtual-assistant builders may particularly benefit from a consistent brand voice, though the setup requires GPU memory configuration and routing knowledge.
Summaries like this, in your inbox every morning.
The Qwen3-TTS family, developed by the Qwen team at Alibaba Cloud, uses the Qwen3-TTS-Tokenizer-12Hz speech tokenizer and supports streaming generation for low-latency, interactive scenarios. The Base variant used here performs voice cloning from a few seconds of user audio and can also serve as a base for fine-tuning. It differs from the CustomVoice variant, which generates speech from a fixed set of predefined speakers rather than a user-supplied reference.
The deployment runs the model as two stages on the same GPU: a talker stage that generates speech tokens from text and reference voice, and a code2wav stage that renders them into a waveform. At container startup, each stage logs memory use to the endpoint's CloudWatch Logs log group. The talker model weights are 3.66 GiB and the code2wav model weights are 0.45 GiB, with most of the remaining memory becoming KV cache — the working memory that holds tokens for in-flight requests.
The key test for this deployment is whether teams can keep the two stages' combined GPU memory reservation within the 24 GB capacity while still handling enough concurrent requests. The article notes that one instance can accommodate multiple simultaneous requests because TTS requests are typically short, but for higher traffic, more instances or a larger GPU would be needed. The walkthrough shows how to manage that balance with configuration and monitoring, which is where the practical value of this news lies for teams building voice-enabled applications.
For example, today's edition would include:
AI-summarized, only the topics you pick: one digest a day via Email, LINE, or Slack.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
McDonald's unveiled "Archy," an English- and Spanish-speaking AI drive-thru system it says exceeds 90% accurac…

Sony and Universal Music Group filed yet another suit against Suno, saying its v6 model is trained on user out…

Google is testing "Call for Me," letting Gemini call businesses for US Pixel 11 owners with a paid Gemini subs…

Intrinsic, Google's AI robotics group, announced it is making parts of its platform open source

PrismML created a version of its tiny language models for smart glasses running on Qualcomm's Snapdragon chips

AWS released the WhisperX Deep Learning Container, a GPU-ready image bundling Whisper, wav2vec2 forced alignme…
