EBOX × EAR CLOUD EAR CLOUD
Home / Core Technologies / Full-Duplex Voice

Full-Duplex: like a phone call, not a walkie-talkie

Traditional voice terminals are half-duplex — you cannot cut in while the device speaks. EBOX achieves true interruptible full duplex with three layers: cut in anytime during playback and the device goes quiet within 100ms to listen.

SoulX-DuplugAEC 40dB≤100ms barge-in
Live conversation · full-duplex demo SoulX-Duplug
Listening · barge in anytime ···
HALF vs FULL DUPLEX

From walkie-talkie to phone call

Same voice interaction — the whole experience gap lives in one question: can you cut in?

Old way

Traditional: half-duplex (walkie-talkie)

Hold to talk → wait for it to finish → then speak. Want to correct? Let it read the whole list. Especially painful in a noisy plant.

EBOX way

EBOX: full duplex (conversation)

Cut in, interrupt, correct — anytime. The device hears itself and hears you; the rhythm feels like talking to a colleague.

THREE LAYERS

Three layers behind true full duplex

First the device "hears itself", then "hears you", and the scheduler decides who speaks first.

VAD

Voice activity detection · VADNet

Neural VAD distinguishes speech / pause / noise in 75dB plant noise, sensing who speaks at millisecond level — the first reaction to an interruption comes from the edge, not the cloud.

Millisecond local response · network-free

AEC

Acoustic echo cancellation · industrial

Dual-filter AEC (linear + non-linear) cancels the device's own playback echo with 40dB suppression — the device "knows what it is saying" and never mistakes its own voice for a command.

Espressif 2026 new-gen full-duplex AEC

Duplug

Full-duplex turn scheduling · SoulX-Duplug

A 160ms acoustic window continuously judges dialogue state (listening / speaking / pausing / idle), with turn decisions in ~250ms — telling "still thinking" from "finished", at human pace.

Open-sourced by Soul AI × Shanghai Jiao Tong University × Northwestern Polytechnical University · Apache-2.0

BARGE-IN TIMELINE

How one interruption happens

Device is reading the answerthe worker cuts in
≤100ms mutestops instantly, never talks over
Listens againhears the full sentence, understands intent
Re-answers in secondsthe new answer picks up seamlessly
Interrupting, talking over, correcting — all happen naturally. This is a conversation, not push-to-talk.
160 ms
full-duplex turn window
~250 ms
turn decision time
≤100 ms
interrupt mute response
75 dB
still hears you in plant noise
Next:Hardware-Software Integration

Want to feel what "barge-in anytime" is like?

A 5-minute live demo beats ten pages of specs.