Repository navigation
Allow setting the known speaker count - #1586
Conversation
|
Excellent feature, I see it to be very valuable. Ideally we would sort out your PR to the Great work! |
|
Thanks! I agree that depending on an upstream My plan is to keep the exact speaker-count option available for the current MSDD path for as long as Buzz still ships that backend. It is opt-in ( I have also separated the backend-independent part of the work into PR #1587: structured speaker metadata, an editable Speaker column with multi-row assignment, a colored and filterable Speakers view, and a colored DOCX export with optional timestamps. That workflow does not depend on MSDD; Sortformer or any future diarizer can populate the same speaker field and reuse the editor, view, and exports. |
|
Moved your change for speaker count to a patch file in Buzz repo, it will be easier to manage. If at some point upstream whisper_diarezation repo will merge it, we can drop our patch. Thanks again for the contribution! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1586 +/- ##
==========================================
- Coverage 83.49% 83.44% -0.06%
==========================================
Files 108 108
Lines 12096 12112 +16
==========================================
+ Hits 10100 10107 +7
- Misses 1996 2005 +9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
Motivation
Buzz can currently merge similar or quieter participants when automatically estimating the speaker count. This implements the known-speaker-count part proposed in discussion #1043 while keeping Auto as the backward-compatible default.
Dependency
This updates the
whisper_diarizationsubmodule to the implementation proposed in MahmoudAshraf97/whisper-diarization#379.Testing
uv run --no-sync pytest -q tests/widgets/speaker_count_test.py: 8 passed