Skip to main content
Qwen3-TTS features Dual-Track hybrid streaming generation architecture, enabling streaming and non-streaming generation from a single model. Achieve end-to-end synthesis latency as low as 97ms for real-time interactive applications.

Overview

Streaming generation allows you to:
  • Start receiving audio immediately after input
  • Achieve 97ms first-packet latency
  • Support real-time conversational AI applications
  • Process long-form content efficiently
  • Maintain high audio quality during streaming
All Qwen3-TTS models support streaming generation out of the box. No special configuration required.

Streaming Support by Model

How Streaming Works

Qwen3-TTS uses a Dual-Track hybrid architecture that:
  1. Processes text incrementally - Generates audio codes as text is processed
  2. Outputs first audio packet immediately - Can output after a single character input
  3. Maintains consistency - Same model handles both streaming and non-streaming
  4. Optimizes latency - Avoids information bottlenecks of traditional LM+DiT schemes

Enabling Streaming Mode

Set non_streaming_mode=False to enable streaming behavior:
Currently, non_streaming_mode=False simulates streaming behavior but processes the complete text input. True character-by-character streaming input will be supported in a future update.

Streaming with Different Models

CustomVoice Streaming

VoiceDesign Streaming

Base Model Streaming

Real-Time Application Examples

Interactive Voice Assistant

Live Commentary System

Phone System IVR

Performance Optimization

Model Selection

Choose the right model for your latency requirements:

Hardware Acceleration

Generation Parameters

Latency Benchmarks

First Packet Latency

Benchmarks measured on NVIDIA A100 GPU with FlashAttention-2 enabled.

DashScope API Streaming

For production deployments, use the DashScope API with native streaming support:
See the DashScope API for complete DashScope documentation.

Comparison: Streaming vs Non-Streaming

Limitations and Considerations

The current implementation simulates streaming by processing complete text input with optimized latency. True character-by-character streaming input will be available in future updates.
For remote deployments, network latency will be added to the 97ms model latency. Use edge deployment for minimum latency.
Streaming mode is optimized for single requests. For batch processing, use non_streaming_mode=True.

Next Steps