Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Speech recognition has been missing half the conversation. Soniox STT v6 is the world’s first STT model that knows what your voice agent is saying. Introducing agent text input. Developers can stream the agent’s outgoing text into STT as it is sent to TTS, giving recognition context from both...

18,188 Aufrufe • vor 3 Tagen •via X (Twitter)

17 Kommentare

Profilbild von Zara Tech & Tools
Zara Tech & Toolsvor 2 Tagen

Smart context boost for voice recognition

Profilbild von Aina Ai | Tools & Updates
Aina Ai | Tools & Updatesvor 2 Tagen

This is a game changer finally STT that hears the full conversation not just half of it

Profilbild von Hitesh Ganjoo
Hitesh Ganjoovor 2 Tagen

Used it, loved it. Already better than v5 with agent text.

Profilbild von Aaliya
Aaliyavor 2 Tagen

like it giving the STT model both sides of the conversation is a smart fix for missed context.

Profilbild von Alex Ai | Tools & Updates
Alex Ai | Tools & Updatesvor 2 Tagen

STT that knows what your agent said changes everything

Profilbild von Leon Ai | tech & tools
Leon Ai | tech & toolsvor 2 Tagen

Finally context aware speech recognition done right

Profilbild von Hana Ai - Marketing Network
Hana Ai - Marketing Networkvor 2 Tagen

Both sides context finally makes sense

Profilbild von Define Ai
Define Aivor 2 Tagen

Using both sides of conversation makes short answers finally land

Profilbild von Alice The Ai Expert
Alice The Ai Expertvor 2 Tagen

Finally STT that actually listens to both sides of the conversation is a game-changer for voice agents.

Profilbild von darkzodchi
darkzodchivor 2 Tagen

you guys be shipping with some insane speed, mad

Profilbild von bodila
bodilavor 2 Tagen

60 languages, that's really impressive... Thanks, team top launch and product!

Profilbild von Vadim
Vadimvor 2 Tagen

It’s cool, but not first. Assembly had it already for a few months. Saying as a big fun of Soniox STT

Profilbild von XXXTENTACIOFF
XXXTENTACIOFFvor 3 Tagen

Good stuff

Profilbild von Sharon Riley
Sharon Rileyvor 2 Tagen

This could make voice agents smarter.

Profilbild von Jeddi in Japan 🇯🇵
Jeddi in Japan 🇯🇵vor 2 Tagen

im going to try this version for a small side project

Profilbild von AURORA Ai
AURORA Aivor 2 Tagen

Finally, speech recognition that understands the full conversation, not just isolated words. This could make voice agents dramatically smarter, more accurate, and natural! 🚀

Profilbild von Veyra | AI & Tech
Veyra | AI & Techvor 2 Tagen

Using agent output as recognition context is brilliant

Ähnliche Videos

Big moment for Voice AI. A typical voice-agent pipeline has three model stages. Speech-to-text converts the caller’s audio into text. The LLM processes that text and generates a response. Text-to-speech converts the response back into audio. For speech accuracy, information can be lost at two boundaries. - STT must preserve what the caller said on the way in. - TTS must preserve what the LLM generated on the way out. If a caller says “RX-B17,” the transcription model could hear “RX-D17” before the LLM receives it. Even if the LLM generates “RX-B17” correctly, the speech model could still make the final audio sound like “RX-D17.” The LLM’s reasoning accuracy is a separate problem. Both speech layers must preserve the information entering and leaving it. This becomes important with medication names, dosages, appointment times, tracking numbers, and alphanumeric codes. Deepgram built Flux TTS for the speech layer. In an evaluation containing drug names, tracking numbers, dollar amounts, technical strings, and alphanumerics, Flux recorded a 3.4% word error rate. I tested the complete voice loop through a pet-hospital conversation about my dog Biscuit’s prescription refill. The agent had to understand and repeat the medication, dosage, prescription number, and a collection time that changed during the call. The test worked well. The agent retained the changing details, the voice stayed natural throughout, and the exchange felt like a call I would be comfortable having with an actual pet hospital. Build with Flux TTS: For every $1 spent on Flux TTS, Deepgram will match $1 in credits, up to $500. My recording is below, and I worked with the Deepgram team to put this post together.

Akshay 🚀

33,399 Aufrufe • vor 9 Tagen

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 Aufrufe • vor 5 Monaten

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!

Andrew Ng

201,127 Aufrufe • vor 2 Jahren