Public Access
fix: unify pyannote validation toggle
PR and Push Build/Test / build-and-test (push) Successful in 12m8s
PR and Push Build/Test / build-and-test (push) Successful in 12m8s
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
## Why
|
||||
|
||||
Speaker identity matching currently exposes two independent pyannote validation switches. Enabling the outer validation switch while disabling the nested diarization switch silently rejects every otherwise usable speaker sample, so the default configuration can prevent all automatic identity matches.
|
||||
|
||||
## What Changes
|
||||
|
||||
- Make `SpeakerIdentification:PyannoteValidation:Enabled` the only switch controlling secondary pyannote validation.
|
||||
- Remove the nested `SpeakerIdentification:PyannoteValidation:Diarization:Enabled` configuration setting.
|
||||
- Ensure enabling validation also enables its pyannote runtime and startup warm-up, while disabling validation preserves primary Azure identity matching without invoking pyannote.
|
||||
- Add regression coverage and configuration documentation for both toggle states.
|
||||
|
||||
## Capabilities
|
||||
|
||||
### New Capabilities
|
||||
|
||||
None.
|
||||
|
||||
### Modified Capabilities
|
||||
|
||||
- `meeting-transcription`: Clarify that secondary pyannote validation has one authoritative enable setting and cannot be partially enabled.
|
||||
|
||||
## Impact
|
||||
|
||||
- Speaker identification options and pyannote runtime invocation.
|
||||
- Pyannote startup warm-up selection.
|
||||
- Checked-in application configuration and configuration reference.
|
||||
- Speaker validation and warm-up behavior tests.
|
||||
Reference in New Issue
Block a user