Загрузка видео...

Не удалось загрузить видео

На главную

Voice agents still don’t understand who’s speaking to them. That’s a huge gap compared with humans, hidden by all the “phone-call” demos. But that changes today! NVIDIA is open-sourcing Nemotron 3 Diarization: a model that can reliably track speakers in live conversations, under a commercial-friendly license! In my tests,...

70,642 просмотров • 1 день назад •via X (Twitter)

Комментарии: 20

Фото профиля XYO
XYO1 день назад

This is an incredible development. That NVIDIA is sharing this technology makes it even better. We're headed toward the cool future, aren't we?

Фото профиля Andi Marafioti
Andi Marafioti1 день назад

Totally! Great future ahead

Фото профиля D_Gof
D_Gof1 день назад

Voice agents don't fail on the LLM half — they fail when they can't tell who said what. Diarization as open infra is the boring layer that makes multi-party agents usable.

Фото профиля Sujal
Sujal1 день назад

how does it hold up on cross talk, overlapping speakers is where one second chunks usually fall apart

Фото профиля Anmol
Anmol1 день назад

speaker drift is what actually breaks those demos in prod

Фото профиля Mena Botrous
Mena Botrous1 день назад

i like this for agents; transcripts need speaker labels when calls overlap.

Фото профиля Badanzer
Badanzer1 день назад

Running the open Nemotron diarization locally on a Spark is the part that matters. Open weights only help if inference stays next to the audio, not on someone else's API.

Фото профиля NarperX
NarperX1 день назад

We are already working on this in production at

Фото профиля Memento Mori
Memento Mori1 день назад

Layperson here: Why can Alexa differenciate betwen my wife, myself, and my kids? Even when there are other people in the house around the same age of the respective person. If the voice doesn't match anyone from our normal every day house hold... it doesn't respond to them directly but instead more generally.

Фото профиля Rugwed
Rugwed1 день назад

this is the missing piece for voice agents that actually work in a room. the phone-call demos hide the fact that most agents panic the second two people talk at once

Фото профиля Chen
Chen1 день назад

walk-mode agent should only call for a real yes/no decision

Фото профиля Arsh Sohal
Arsh Sohal1 день назад

This matters a lot on real phone calls, where a spouse or a colleague often picks up halfway through. Knowing the speaker changed lets the agent stop and re-check identity before it shares account details.

Фото профиля Jatin Garg
Jatin Garg1 день назад

speaker overlap is the hard part for live calls. does Nemotron 3 handle crosstalk reliably or does it still need clean turn-taking?

Фото профиля Mahesh | AI Architect × Systematic Trading
Mahesh | AI Architect × Systematic Trading1 день назад

Asking for the name is the smart bit. Diarization alone only gives you speaker 0 and speaker 1

Фото профиля Diego Carlino
Diego Carlino1 день назад

@huggingface damn i wish i had my reachy with me rn 😭 good stuff 🔥

Фото профиля Li Yibai
Li Yibai1 день назад

This is huge for voice agents in shared spaces.

Фото профиля مُحَمَّدٌ الشِّهَابِيُّ | Mohammed Al-Shihabi
مُحَمَّدٌ الشِّهَابِيُّ | Mohammed Al-Shihabi1 день назад

The bottleneck in voice agents isn't more parameters; it's acoustic telemetry latency. True diarization requires extracting raw communicative primitives at the edge, not routing conversational audio to cloud servers. Sovereignty starts with local acoustic logic. ♟️

Фото профиля matt
matt1 день назад

one-second chunks should make the live handoff a lot less janky

Фото профиля John Daniels
John Daniels1 день назад

Backup (no product): Phone demos hide speaker confusion hard. Feels like this closes a real gap vs humans.

Фото профиля Mo's fav goat
Mo's fav goat1 день назад

Voice AI tool to check out later

Похожие видео

Introducing PhoneLLM, an open model for voice agents. GPT 5.6 Terra performance on typical voice agent tasks at 1/3 the latency and 1/18 the cost. For voice agents, we need models that are both very low latency and very good at tool calling and instruction following. There's a trade-off here, and we often have to compromise on either latency or capability when building voice agents. With PhoneLLM (and the training and data stack that made this model possible) we're fixing this problem. For the last couple of years, most of the effort in frontier model development has gone towards leveraging test-time compute. Which is awesome! Models of all shapes and sizes are available that perform really, really well ... if you have "thinking" turned on for your model. But if you need your agent to respond at voice conversation speed, you can't use thinking models. PhoneLLM is a full-weights fine-tune of NVIDIA Nemotron Nano 30B. We trained on a wide range of real-world telephone and customer support use cases. The training focused on taking the excellent Nano 30B base capabilities and teaching the model to do typical voice agent tasks with thinking disabled. The results are really good: accurate tool calling and concise, on-topic responses in long conversations. And fast: TTFAT measured server-side is <100ms if you run PhoneLLM on a lightly loaded B200. :-) But seriously, when we characterize model latency, we do it with full, end-to-end, batched request simulations using real Pipecat voice agent pipelines. You can serve more than 80 concurrent agents on a single B200 with P95 end-to-end TTFAT <600ms. Including network overhead. That's an LLM cost-per-minute around $0.0025. (1/4 of a cent.) At a latency lower than any third-party API offers today. More details about this model, including weights on Hugging Face, how to spin it up with one click on Modal, and a starter project repo you can clone, are in the thread ...

kwindla

331,175 просмотров • 28 дней назад

Nvidia has just announced Alpamayo 2 Super, an open 34 billion parameter reasoning vision-language-action model designed to accelerate the development of autonomous vehicles. This new model combines the NVIDIA Cosmos 3 Super reasoning model with a 2 billion parameter diffusion-based action expert model, and is post trained with reinforcement learning. The model can return multiple outputs: future trajectory plans, reasoning traces, grounded answers to questions about the scenes, and auto label generation. The model weights are now available for anyone to download on Hugging Face, and the inference code has been posted to GitHub. Distilled models can be deployed commercially without any further permission from Nvidia, and model outputs carry no license conditions. Automakers can distill down a compact version of this model that can run on the Nvidia computer in the car. Major kudos to Nvidia and Jensen Huang for advancing the state of the industry by releasing this as an open model with permissive licensing. Jensen isn't just paying lip service to the idea of open models, Nvidia is actually contributing to the ecosystem — and it's great for their business, because it helps sell more Thor computers that go in the car. Anyone can go download the model and play with it. If you do, let me know what you think. Personally I think it's so cool that we have open weights models that are this advanced, for anyone to download.

Whole Mars Catalog

45,595 просмотров • 1 месяц назад

Cerebras inference is very fast. So fast that it changes how we think about configuring our LLMs for voice agent use cases. Kimi K2.6 is a 1T parameter reasoning model that Cerebras serves at 650 - 1,000 tokens per second (end-to-end throughput), with time to first token metrics as low as 150ms (latency). These numbers are two to three times faster than other similarly capable models. The biggest lever we get from this kind of speed is that we can use the model in reasoning mode, and still have excellent "time to first non-thinking token." This solves a big pain point we have in 2026 for voice agent use cases. Almost all recent innovation in post-training has focused on making models good at reasoning ("test time compute"). This is great, but it makes the user-facing model latency much, much slower. Which is a problem for conversational voice agents. We can run Kimi K2.6 with reasoning turned on, and get responses faster than other models produce with reasoning disabled. On my 30-turn voice agent benchmark, Kimi K2.6 with reasoning enabled ties GPT 5.1 and Haiku 4.5 with reasoning disabled, and is still about 200ms seconds faster! On my primary task agent benchmark, Kimi K2.6 is now the #2 model. It ranks just behind Gemini 3.5 Flash in "high" reasoning mode, and tied with GLM 5, Sonnet 4.6, and GPT 5.4 with reasoning set to "low." But Kimi K2.6 completes each turn in the agent loop in under 500ms. The other four models are all at least 3x slower. (Models only qualify for this benchmark if they can complete task turns at a P50 <4s.) A couple of other things that this speed buys us, for production voice agents: - Tool calls happen fast enough that we don't have to work around tool call latency in our pipeline design. - We can prompt the model to output structured data at the beginning of a response, followed by plain text for voice generation. This opens up possibilities like asking the model to do complex classification/generation tasks that influence the rest of the pipeline. For example, the model could create a detailed style prompt for a steerable TTS model, for each individual conversation turn. And, of course, you can use Kimi K2.6 with reasoning turned off. Cerebras calls this "instant" mode. Here's a video of a Cerebras Kimi K2.6 voice agent with voice-to-voice response time, measured at the client, under 500ms. This is the true response latency as perceived by the user, including all network and audio codec overhead, transcription and turn detection, Kimi K2.6 token generation, and voice generation. 500ms is, effectively, instant. So the Cerebras naming for this mode is a propos. :-)

kwindla

40,593 просмотров • 4 месяцев назад