AI & ML
Toward accurate speaker inventories for online speaker diarization
arXiv eess.AS0 views
arXiv:2610.11278v1 Announce Type: new Abstract: An online speaker diarizer maintains a growing inventory of speakers, and applications read it directly: a live transcript enumerates them as they appear. Existing systems either fix the inventory's size in advance, so speakers beyond that size are merged, or grow it on distance alone, so noise and turn boundaries split speakers. Scored on speaker count over nine public datasets, both failures appear where DER reports neither: on VoxSRC-23 the fixed-capacity systems return 44-46% too few speakers and the unbounded tracker with the lowest DER 63% too many. We build on that embedding-based tracker and change only what triggers a registration. A candidate speaker pool keeps unregistered embeddings apart and registers a speaker only once one candidate has gathered enough mutually compatible embeddings; commit-gated label assignment holds an output while its candidate is undecided, so no speaker appears in the output before it is confirmed. Across the nine datasets the macro speaker-count error falls from 225% to 21% of the reference and macro DER from 17.59% to 15.95%, at a mean added latency of 0.109s over all outputs; on VoxSRC-23 the tracker obtains both the lowest DER and the most accurate speaker count of the systems compared.
Source:https://arxiv.org/abs/2610.11278PreviousUsing the enrollment gallery as evidence: affine-invariant score calibration for target speaker taggingNextMonaural Continuous-Radius Regional Speech Extraction with Cross-Radius Consistency Learning
Related posts
How I Diagnose a Slow, Loud, or Overheating PC: A Practical Checklist
0dev.to Beginners
You Did Great for Three Days. Then Life Happened. Here Is a Habit System That Survives That.
0dev.to Beginners
Building an Agent Evaluation CI/CD Pipeline: Architecture, Budgets, and Regression Gates
0dev.to Testing
Truncado silencioso: cuando un verificador de LLM da el mismo puntaje a una respuesta correcta y a una incorrecta
0dev.to Testing
Your CI is red because of code you didn't write
0dev.to OpenSource
Summer 2026 Internships: 8 New Openings This Week (Nov 2)
0dev.to Programming