Loading video...

Video Failed to Load

Go Home

NVIDIA released a fast speaker-labeling model today: Nemotron 3 Diarization. Like all of the Nemotron family from @NVIDIA_AI, this is an open weights model, so you can grab the weights from Hugging Face and use the model in the cloud or on your local device. Nemotron 3 Diarization is...

12,729 views • 1 month ago •via X (Twitter)

13 Comments

kwindla's profile picture
kwindla1 month ago

NVIDIA Nemotron 3 Diarization model card and weights: Jon's demo code: Models used in the demo: - NVIDIA Nemotron 3 Diarization - NVIDIA Nemotron 3.5 ASR - Pipecat Smart Turn - Pipecat PhoneLLM - Typesafe Jev - NVIDIA Magpie TTS

kwindla's profile picture
kwindla1 month ago

The NVIDIA launch post here on X, with links to model benchmarks:

Miguel Twahirwa's profile picture
Miguel Twahirwa1 month ago

@nvidia_ai @huggingface very cool!

Justin.md's profile picture
Justin.md1 month ago

@nvidia_ai @huggingface Already working on getting this in my app for audio recordings 🔥

Matthew Anorkplim Loh's profile picture
Matthew Anorkplim Loh1 month ago

@nvidia_ai @huggingface This is fantastic. Very fantastic

k0n00's profile picture
k0n001 month ago

@nvidia_ai @huggingface On phone interviews diarization never paid rent. Our false barge-ins came from a TV in the room, not a second speaker on the line.

kwindla's profile picture
kwindla1 month ago

Agreed. Phone use cases don't need diarization. A good primary speaker isolation model (a noise reduction model that removes all background noise including background speech) is a better fit. Diarization is important for use cases where you need the agent to "hear" multiple speakers, and you need the agent to know/track the different speaker identities.

GD's profile picture
GD1 month ago

@k0nOO @nvidia_ai @huggingface Are there some good noise reduction model out there which we can integrate in pipecat pipeline. Are there some code examples for that ?

kwindla's profile picture
kwindla1 month ago

@k0nOO @nvidia_ai @huggingface We usually recommend @krispHQ. It’s a commercial model so it isn’t free. But it’s available through Pipecat Cloud with 10,000 free minutes per month.

Git_Shark's profile picture
Git_Shark1 month ago

@nvidia_ai @huggingface this is something really awesome! looking for this for long

bendoesmath's profile picture
bendoesmath1 month ago

@nvidia_ai @huggingface Getting every word right and assigning the promise to the wrong person is how a meeting bot invents volunteers.

Lukas Mosser's profile picture
Lukas Mosser1 month ago

@nvidia_ai @huggingface Is give this to @GMHikaru and then no more mouse slips only “takes takes takes”

Nora Vale's profile picture
Nora Vale1 month ago

@nvidia_ai @huggingface Pairing it with whatever transcriber you already run is the practical move. Jev only stepping in to confirm the noisy bit is a sane split.

Related Videos

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

335,479 views • 2 months ago