Qwen3.8 LiveTranslate cuts lag and tracks speakers

Alibaba’s Qwen team has released Qwen3.8 LiveTranslate, a hosted model for simultaneous speech translation. The update reduces reported average lag, separates speakers in multi-party audio, preserves their voices in translated speech, and maintains terminology across long sessions. For conference, livestream, classroom, and meeting applications, those changes can replace several separately operated speech services with one WebSocket connection.

The half-second gain comes with speaker IDs

The previous Qwen3.5 release began with 18 input languages and 10 output languages before expanding to 60 input languages and 29 spoken-output languages. Qwen3.8 retains that expanded coverage and lowers length-adaptive average lagging, or LAAL, from 2.8 seconds to 2.3 seconds. LAAL estimates the delay between source speech and its corresponding translation.

Alibaba also reports gains in faithfulness, fluency, and concision. End-to-end application latency will exceed the 2.3-second LAAL measurement once capture, network transit, synthesis, buffering, and playback are included.

• Speaker-aware voice output. Real-time diarization assigns audio segments to individual speakers. Voice cloning then preserves each person’s vocal characteristics, allowing a translated panel to retain distinct voices. Earlier versions already cloned voices; Qwen3.8 focuses on maintaining the correct voice across multi-speaker turns.
• Synchronized bilingual text. The source transcript and translation appear together, supporting captions, monitoring interfaces, and localization workflows.
• Long-session terminology. Conversation history helps the model preserve names, product terms, and technical vocabulary instead of resolving them again for each sentence.

Meaning arrives before the sentence ends

A conventional simultaneous-translation stack chains streaming speech recognition, machine translation, and text-to-speech synthesis. Each boundary adds buffering, operational overhead, and another place for errors to propagate. Qwen’s Interleave architecture processes incoming media and generates translated text or speech within one model.

Semantic-unit prediction allows the model to emit coherent phrases before a complete sentence arrives, reducing delays caused by different word orders across languages. Dynamic sampling controls when output is generated as new context becomes available, while the mixture-of-experts design routes each token through a subset of the model’s parameters to limit computation.

Audio and video frames can enter the shared context, allowing lip movements, gestures, and on-screen text to inform translation. The same context carries speaker identity and prior terminology through a session. Alibaba reports that the real-time system retains more than 94% of its offline translation quality.

Results published with the earlier release placed the Flash line ahead of Gemini 2.5 Flash, GPT-4o Audio Preview, and Voxtral Small 24B on speech-translation accuracy, including tests involving business talks, casual conversation, technical material, echoes, and overlapping voices. Those evaluations predate Qwen3.8 and therefore do not measure its new diarization or latency changes.

One socket, five integration steps

The model runs through Alibaba Cloud Model Studio, branded internationally as QwenCloud. The following Python example opens the international DashScope WebSocket endpoint and prints server events; it does not configure a session or stream media.

import os
import websocket

api_key = os.environ["DASHSCOPE_API_KEY"]
url = (
    "wss://dashscope-intl.aliyuncs.com/api-ws/v1/"
    "realtime?model=qwen3.8-livetranslate-flash-realtime"
)

def on_open(ws):
    print("connected; configure the session before sending media")

def on_message(ws, message):
    print(message)

def on_close(ws, code, reason):
    print(f"closed: {code} {reason}")

client = websocket.WebSocketApp(
    url,
    header={"Authorization": f"Bearer {api_key}"},
    on_open=on_open,
    on_message=on_message,
    on_close=on_close,
)

client.run_forever()

1. Open the authenticated WebSocket connection from a trusted backend.
2. Send session settings for source language, target language, output modalities, and the required media format.
3. Stream ordered audio or video events in appropriately sized chunks.
4. Consume partial and final transcripts, translations, speaker identifiers, and generated audio.
5. Commit or close the stream according to the published event schema.

Production clients also need reconnection logic, event ordering, playback buffering, cancellation handling, and observability for model and network latency. Browser applications should proxy requests through a backend so the DashScope API key never reaches client-side code.

What a minute of audio costs

Billing is token-based. Audio consumes 12.5 tokens per second for both input and output, equivalent to 750 tokens per minute. Video frames are measured at 0.5 tokens per 28×28-pixel patch.

One minute of continuous audio input plus one minute of translated audio output costs about $0.0281 before text and video charges. At the same rates, an hour costs about $1.69. Actual bills depend on enabled modalities, session duration, and regional pricing.

The published defaults include a 53,000-token context window, 100,000 tokens per minute, and 10 requests per minute. Account and regional quotas should be checked before capacity planning, especially when many long-lived conference or classroom sessions start together.

Constraints that affect deployment

• No self-hosting. The model is API-only and closed-weight, tying deployment, availability, and pricing to Alibaba Cloud.
• Uneven language coverage. The model accepts 60 input languages but synthesizes speech in 29, so some translations can be displayed as text without spoken output.
• No tool or reasoning modes. Livetranslate does not expose the function-calling or thinking-mode features available in some other Qwen real-time models.
• Voice-data governance. Production reviews need to cover speaker consent, retention rules, access controls, and the region where voice data is processed.

Where the single endpoint fits

• International conferences with several panelists
• Livestreams that preserve the host’s voice in another language
• Remote classrooms with bilingual captions and audio
• Enterprise meetings containing dense product names and technical terms

Teams currently combining streaming speech recognition, a translation model, and text-to-speech can use Qwen3.8 LiveTranslate to reduce service orchestration and preserve speaker identity across the pipeline. That consolidation concentrates reliability, cost, privacy, and roadmap dependencies in Alibaba Cloud, making the service best suited to products that accept hosted inference and the available language matrix.