Parley

Posted on Oct 26 Originally published at parleyvoice.com

How Real-Time Simultaneous Interpretation Works: Pipeline vs End-to-End Speech Models

#translation #meetings #speech #ai

Short answer: “Realtime voice translation” usually means one of two architectures. A three-stage pipeline turns speech into text (ASR), translates the text (MT), then speaks the result (TTS). An end-to-end / speech-to-speech (S2S) system maps speech toward speech more directly, with less (or no) intermediate text you can inspect. Latency, fidelity, language coverage, voice cloning, and cost all follow from that choice — not from marketing labels.

I built Parley Voice (China: parleyvoice.cn) because I sit in international meetings, my spoken English is weak, and I wanted two-way spoken translation through Zoom, Google Meet and similar apps without asking the other side to install anything. Disclosure: I make Parley. This piece is the architecture trade-off I wish someone had written before I started shipping.

What “three-stage” means (ASR → MT → TTS)

Cascaded systems do three jobs in sequence:

ASR — turn source audio into text.
MT — translate that text into the target language.
TTS — synthesize speech from the translated text (system voice or cloning).

Buffers and phrase-boundary logic sit between stages. That is why cascades often feel like sitting next to a human interpreter: they wait a beat for context, then emit a chunk.

Strengths: inspectable intermediate text (captions, logs, SRT); independent knobs for ASR / MT / TTS; familiar failure modes (“the transcript misheard the name”).

Costs: stacked delay; error compounding (ASR miss → wrong MT → confident TTS); prosody loss unless cloning or style transfer is added.

What “end-to-end / S2S” means

End-to-end (often marketed as speech-to-speech or S2S) tries to go from source audio toward target audio with fewer hand-offs. Designs vary: a single model emitting translated speech or speech tokens; a shared latent space; or hybrids that peek at text internally without exposing a clean ASR→MT→TTS product surface.

For buyers, the practical definition is: you hear translated speech, and you may or may not get a reliable intermediate transcript as a first-class feature.

Strengths: fewer hand-offs can reduce stacked error and, in some demos, feel more continuous; prosody may transfer better when speech is modeled jointly.

Costs: harder to debug without a stable text stage; language matrices are often narrower than cascaded ASR/MT catalogs; caption quality is not guaranteed; you may lose independent cost/control over each stage.

Neither architecture is “more simultaneous.” Simultaneous means overlapping in time with the speaker — not zero delay. Both buffer audio for context.

Latency, fidelity, languages, voice, and cost

Latency

Published figures are easy to misuse. On Parley’s live site (as of 2026-10-22), Qwen officially reports LAAL of about 2.3 s, and Doubao reports speech output latency of about 2.53 s. The site is explicit: these are different metrics — not a direct speed comparison or a guarantee of in-app latency. Actual delay depends on the model, network, and audio devices. Provider demos are not Parley app recordings.

Ask vendors: is the number model-only or full path (capture → cloud → playback)? Does silence while connected count toward billing? Did you measure on your network before an important call?

Fidelity

Cascades fail when ASR mishears; E2E fails when the joint model drifts. Mitigation is the same: pause on numbers and names, confirm commitments, keep captions as a second channel when available. For legal, safety, or contractual content, use a qualified human interpreter when the risk requires it.

Language coverage

Input recognition and spoken output are not the same list. On Parley’s live languages (China) page:

Model	Input	Spoken output
Qwen (multilingual)	60 languages	29 languages (Cantonese is input-only)
Doubao	Chinese ↔ English	Chinese ↔ English

OpenAI and Gemini adapters are marked coming soon on the live site — not available in the app’s provider selector today.

Cascaded stacks often win breadth by composing ASR/MT catalogs. E2E stacks often win continuity on fewer pairs. Check spoken targets, not “supports 100 languages” headlines.

Voice cloning

Voice answers “what should the translation sound like?” — not which architecture is used. On Parley’s managed service, Qwen and Doubao currently support live voice cloning at the displayed session rate: no advance sample or enrollment (per live FAQ / homepage). You can also pick a built-in voice. Likeness is not a guarantee of translation accuracy. Deeper note: Meeting translation in your own voice (China).

Cost knobs

As of the live pricing page (China): managed Qwen $0.070 / minute, managed Doubao $0.148 / minute, no recurring Parley subscription for managed meeting use, billed by the millisecond once the connection is ready (silence included; stop the session to stop billing). Two directions share one session charge. A 60-minute Qwen session at list rates is $4.200; Doubao is $8.880. Temporary Preview offers can change what you pay for credit — check the live page. The homepage still states a $1 first top-up is enough to try.

When each fits meetings vs venues

This is different from choosing meeting voice vs captions vs venue mode (Live voice, captions and venue interpretation (China)). Here the question is pipeline style inside the speech path.

Online meetings (two-way): you need speak + listen, turn-taking, and often captions for verification. A cascade that exposes bilingual text is usually easier day to day. An E2E model can feel smoother in demos only if captions, language pairs, and virtual-mic routing still work with your meeting app.

Venue / one-speaker events: continuity and clear output routing matter more than back-and-forth repair. Either architecture can work; physical audio (feedback into the source mic, language bleed) often dominates. Architecture alone will not fix a bad PA layout.

Buyer checklist: (1) spoken output languages you need, (2) captions you can re-check, (3) what is billed and whether silence counts, (4) whether the other side must install anything, (5) a real both-directions test before the important call.

Where Parley sits today

Parley is a Windows and Mac desktop app for live meeting translation (China): your mic → cloud translation → virtual microphone into Zoom / Meet / similar; meeting audio → translation → your headphones; bilingual captions in the app; caption history local with SRT export. Only you install it. Managed models shipping now are Qwen and Doubao, with live voice cloning included at the session rate. Gemini and OpenAI are listed as coming soon — not shipped.

I will not invent a roadmap about whether our cloud providers are “pure cascade” or “pure S2S” under the hood. Users feel the product surface — delay, captions, language matrix, voice, and price — more than the research label. We expose managed models with clear per-minute rates, bilingual captions, and honest caveats about network and devices. Delay is often on the order of a couple of seconds in practice (like sitting next to a human interpreter); we do not promise a fixed app SLA.

Try a short session

Download Parley for Windows (x64 / ARM64) or Mac (Apple Silicon / Intel).
Check both audio directions with the meeting app you actually use.
Top up — the live homepage still says a $1 first top-up is enough to try — and run a few minutes at pricing (China) rates for Qwen or Doubao.
Stop the session on breaks; connected silence is billed.

Questions: support@awiki.ai.

Disclosure: I am Gaowei Chang, founder of Parley Voice (parleyvoice.com · parleyvoice.cn). I built the product described here. This is not an independent review. Features and prices reflect the public site; confirm /pricing and /languages before you buy.

Learn about ParleyVoice: Overseas parleyvoice.com · China parleyvoice.cn

Canonical / original:

Also ZH:

Official posts (both domains):