Speech-to-Text (STT) is technology that converts spoken audio into written text.
π― Why it matters: Live use cases like voice assistants, meeting tools, and live captions cannot wait for a recording to finish. They need text immediately.
Latency = the delay between when someone speaks and when the text appears.
| Latency Level | Experience |
|---|---|
| > 500ms | Noticeable lag, feels broken |
| 150β500ms | Acceptable but sluggish |
| < 150ms | Feels instant/natural |
Scribe v2 Realtime targets under 150ms latency, which is roughly the threshold of human perception for "real-time."
This is the most advanced concept in the article.
Normal latency: System waits for you to finish a word β then transcribes it
Negative latency: System predicts the next word and punctuation before you finish saying it
You say: "I'd like to schedule a meetβ"
System: Already predicting β "meeting"
π§ Think of it like autocomplete, but for live speech. The model uses context to anticipate what comes next, effectively getting "ahead" of the speaker.
VAD answers one question: "Is someone speaking right now, or is this silence/noise?"
Without VAD:
With VAD:
ποΈ VAD is especially critical in noisy environments like call centers or meetings.
Real-time audio streams can drop and reconnect (network issues, timeouts, etc.).
The problem without text conditioning:
Connection 1: "The meeting is scheduled forβ" [drops]
Connection 2: [restarts with no memory] β confused transcription
With text conditioning:
π Think of it like giving the model a "memory" of what was already said.
In real-time STT, transcripts go through two states:
| State | Meaning |
|---|---|
| Interim/Partial | Still being processed, may change |
| Final/Committed | Locked in, won't change |
Manual commit gives you (the developer) control over when a segment is finalized.
Use cases:
Traditional STT requires you to declare the language upfront.
Scribe v2 Realtime:
Speaker: "Hello, how are you? ... Bonjour, comment Γ§a va?"
System: English β βββββββββ French β (seamless switch)
π This is critical for multilingual environments like international support lines or global meetings. Supports 90 languages.
An AI Agent (like a voice assistant) needs to:
Scribe v2 Realtime is specifically optimized for this pipeline:
User speaks β [< 150ms] β Text β AI processes β Voice response
π€ Without fast, accurate STT, the entire agent feels slow and robotic β even if the AI reasoning and voice synthesis are fast.
Speed means nothing without accuracy. Key benchmarks:
π This is described as "human-level understanding" β meaning it performs comparably to a human transcriber under difficult conditions.
Audio Input
β
[VAD] β filters silence/noise
β
[Language Detection] β identifies language automatically
β
[Real-Time Transcription] β < 150ms latency
β
[Negative Latency] β predicts next words
β
[Text Conditioning] β maintains context if connection drops
β
[Manual Commit] β you control when transcript is finalized
β
Final Transcript β AI Agent / Captions / Meeting Tool
Each feature solves a specific real-world problem that makes live transcription difficult. Together, they enable natural, human-like real-time conversation with AI systems.