The real-time audio engineering nobody talks about
Chintan Agrawal & Daniel Wirjo · AWS Solutions Architects
The difference between a voice agent that feels broken and one that feels natural comes down to how well it handles interrupts and turn-taking.
User: "I want to fly to—"
Agent keeps talking — ignores interruption for 1.8 s
User: "no wait, a HOTEL—" (ignored)
User: "I want to fly to—"
✖ STOP — interruption detected
User: "actually, a hotel in Sydney"
Agent: "Hotel in Sydney — got it!"
200 ms is the time from when the user stops speaking to when the agent starts responding. Below that, conversation feels natural. Above it, users pause, repeat themselves, or assume the call dropped. Chat agents get seconds — voice agents don't get a second chance.
Best measured human TTFA
Stivers et al., PNAS 2009 — 10 languages, 10K+ conversations
Best measured TTFA — cascaded pipeline
Qiu et al., Salesforce 2026
Speech-to-Text (STT), a Language Model (LLM), and Text-to-Speech (TTS) are all critical components of a voice agent. But VAD — voice activity detection — is an often-overlooked layer. It decides when the user has finished speaking. Get it wrong and everything downstream breaks.
Smart Turn Detection
Listens to VAD + audio features. Decides: respond or wait.
Interruption Handler
Propagates InterruptionFrame — flushes TTS + LLM buffers.
What is Pipecat?
Open-source framework for real-time voice agents — wires STT, LLM, TTS, and VAD into a frame-based pipeline with backpressure, interruption handling, and streaming built in.
The simplest component you fully own. This is where most production systems start.
Snappy. May cut off thinking.
Balanced. Most users happy.
Patient. Respects pauses.
Never interrupts. Dead-air risk.
Is the user done, or just thinking? 300 ms and 1200 ms silence look identical to raw VAD.
The decision depends on context — correction, affirmation, or ambient noise. Most agents don't distinguish.
Complete sentence. Incomplete thought. Thinking pause. Backchannel "yeah". VAD fires on all of them.
Smarter than raw VAD. State-of-the-art STT models are now starting to incorporate turn detection.
turn.start / turn.end eventsCartesiaTurnsSTTServiceendpointing parameter controls silence thresholdBoth are Level 2 — smarter than raw VAD, no local model required. Best for prototypes and latency-sensitive deployments where control is less critical.
Full control. Transparent. Tunable. Portable.
| System | Recall | Precision | Size | License | Status |
|---|---|---|---|---|---|
| Smart Turn v3.2 ✓ Open source | 58.9% | 68.4% | 8–32 MB | BSD-2 | pip install today |
| Helwani (Meta, 2026) | 87.7% | 57.2% | 1.14M params | No code released | Research only |
| Cartesia Ink-2 | — | — | API | Proprietary | Built into STT |
| Deepgram Flux | — | — | API | Proprietary | Built into STT |
| LiveKit Turn Detector | — | — | v1 / v1-mini | Proprietary | v1: cloud (LiveKit); v1-mini: local CPU |
Smart Turn: 12 ms inference, 200–400 ms effective detection. Runs only during silence. CPU (8 MB quantized) and GPU (32 MB unquantized) versions available.
pipecat-ai/smart-turn
Decision logic
STOP
Correction detected. Cut audio immediately.
FADE
Affirmation ("yeah"). Taper over 200 ms.
FINISH
Noise / backchannel. Complete current sentence.
Level 1
Silero VAD
Own your silence detection
Level 2
Built-in turn detection
Smarter, but vendor-managed
Level 3
Silero VAD + Smart Turn
Full control, fully portable
Total: ~1,100–1,300 ms (API-based) · ~500 ms achievable with co-located models
Source: voiceaiandvoiceagents.com — learn more about voice agent latency breakdown
TTFT alone isn't enough. Instruction following must not degrade across multiple turns — if it does, you'll need workarounds like context pruning or context trashing to keep the model on-task. The aiewf-eval benchmark tests 30-turn conversations specifically to surface this.
Source: aiewf-eval multi-turn benchmark (kwindla, 2026) — 30-turn conversations, 10 runs each. TTFT = time to first token. · wirjo.github.io/voice-ai-benchmarks · github.com/kwindla/aiewf-eval
Infrastructure is hard
Multiple components — WebRTC transport, VAD, STT, LLM, TTS — each with its own scaling, latency, and failure modes. Coordinating them in production is non-trivial.
Pipecat Cloud
Managed hosting for Pipecat pipelines. Handles scaling, session management, and WebRTC — so you focus on the agent logic, not the plumbing.
AWS Guidance
For enterprise deployments: secure, governed, within your AWS environment. Reference architecture covering VPC, IAM, Bedrock integration, and SageMaker bidirectional streaming.
Repositories
Demo & code
github.com/wirjo/
pipecat-turn-detection-demo
AWS Guidance
github.com/aws-solutions-library-samples/
sample-voice-agent
LLM Benchmarks
wirjo.github.io/voice-ai-benchmarks
Stack
Pipecat · pipecat.ai
Cartesia STT & TTS · cartesia.ai
Daily managed WebRTC · daily.co
Smart Turn · github.com/pipecat-ai/smart-turn
Silero VAD · github.com/snakers4/silero-vad
Speakers
Chintan Agrawal
Daniel Wirjo
Solution Architect
Amazon Web Services (AWS)

Open source voice agent framework by Daily. Thanks to the Pipecat community for building the tools that make this possible.