Temporarily mute system playback during voice capture
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Shell
- Sterne
- 11.2k
- Forks
- 1.9k
- Ø Merge
- 14 Std. 16 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
Describe the feature or problem you'd like to solve
Temporarily mute system playback while voice capture is active. For example, I may be listening to Spotify when I press the keyboard shortcut to speak to Copilot. The speaker audio can interfere with microphone capture, so I would like playback muted immediately and restored when I finish talking.
Proposed solution
Add an option such as Mute system playback while listening. When voice capture begins, Copilot should save the current output device and mute state, then mute the active playback device. When capture ends or is cancelled, it should restore the saved state rather than simply toggling mute.
This would improve transcription quality and prevent background audio from being captured without requiring users to manually pause or mute other applications.
Example prompts or workflows
- While Spotify is playing, press the Copilot voice shortcut; playback is muted until voice capture ends.
- Cancel voice capture; playback immediately returns to its previous state.
- Start voice capture while the output is already muted; it remains muted afterward.
- Switch output devices, including a Bluetooth profile change, while capturing; Copilot safely restores the device state when capture ends.
Additional context
This appears feasible on all three desktop platforms without elevated privileges:
| Platform | Feasibility | Native mechanism |
|---|---|---|
| Windows | High | Core Audio IAudioEndpointVolume exposes GetMute/SetMute for the default render endpoint. |
| macOS | High | Core Audio exposes kAudioDevicePropertyMute, readable and writable through AudioObject property APIs on supported output devices. |
| Linux | Medium-high | PipeWire/WirePlumber supports muting the default sink (for example, wpctl set-mute @DEFAULT_AUDIO_SINK@); PulseAudio exposes pa_context_set_sink_mute_by_name. The implementation needs backend/runtime detection across distributions. |
Cross-platform implementation considerations:
- Snapshot the output device identity and prior mute state before changing it; do not implement this as a blind toggle.
- Restore state on every normal completion, cancellation, and error path. Because endpoint mute can survive a process crash, persist enough temporary state for best-effort recovery on the next launch.
- Handle default-device changes during capture, especially Bluetooth devices switching between high-quality playback and headset profiles when the microphone opens.
- Check whether the selected device actually exposes a writable mute control. If not, report that the option is unavailable rather than silently changing volume.
- Avoid overwriting a mute-state change the user makes manually while voice capture is active.
Muting all system playback would be simpler and more predictable than targeting individual applications such as Spotify. Per-application muting could be considered separately but varies more significantly by platform and audio backend.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Es werden keine Dateien, Tests oder Einstiegspunkte genannt. Beginne damit, die vorhandenen Pfade zum Starten, Abschließen, Abbrechen und zur Fehlerbehandlung der Sprachaufnahme zu finden, und ermittle anschließend die Audio-Integrationen der Plattform. Erledigt ist die Aufgabe, wenn eine optionale Stummschaltungsfunktion das Ausgabegerät und den Stummschaltungsstatus sichert, beides bei jedem Beendigungspfad sicher wiederherstellt und Änderungen des Geräts sowie nicht verfügbare Stummschaltungssteuerungen behandelt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- audio-video-rtc, desktop
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 30/100