Public Access
fix: recover from microphone disconnects
PR and Push Build/Test / build-and-test (push) Successful in 12m29s
PR and Push Build/Test / build-and-test (push) Successful in 12m29s
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
## Why
|
||||
|
||||
Unplugging the active microphone currently propagates a WASAPI capture error through the recording pipeline and terminates the active meeting recording. Recording must remain available through transient device changes so that already-captured meeting work and continued system audio are not lost.
|
||||
|
||||
## What Changes
|
||||
|
||||
- Recover microphone capture when the active Windows capture endpoint disappears or otherwise stops unexpectedly.
|
||||
- Re-resolve the effective microphone for each recovery attempt so an available configured, runtime-selected, default, or fallback endpoint can take over.
|
||||
- Keep the active recording and its independent system-audio capture alive while no microphone is temporarily available.
|
||||
- Log microphone recovery failures and successful capture restarts without terminating the meeting run.
|
||||
|
||||
## Capabilities
|
||||
|
||||
### New Capabilities
|
||||
|
||||
None.
|
||||
|
||||
### Modified Capabilities
|
||||
|
||||
- `meeting-recording`: Active recording becomes resilient to microphone endpoint disconnection and automatically resumes microphone capture from an available endpoint.
|
||||
|
||||
## Impact
|
||||
|
||||
- Affects the Windows microphone capture source and device-provider boundary.
|
||||
- Adds behavior tests around the public meeting audio-source contract.
|
||||
- Does not change recording endpoints, tray controls, system-loopback capture, or transcription-provider APIs.
|
||||
Reference in New Issue
Block a user