run optional command after switching audio sink/source - #917
Open
romanstingler wants to merge 1 commit into
Open
run optional command after switching audio sink/source#917romanstingler wants to merge 1 commit into
romanstingler wants to merge 1 commit into
Conversation
romanstingler
force-pushed
the
feat/audio-post-switch-cmd
branch
from
August 21, 2026 17:26
e54df92 to
fa9fed5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #892
Allows an optional command to run automatically after switching the audio output or input device in the settings panel. Useful for working around PipeWire/WirePlumber routing issues (e.g. RAOP/HomePod sinks) that require restarting the audio service on switch.
audio_sink_post_switch_cmdandaudio_source_post_switch_cmdtoSettingsModuleConfig/AudioSettingsConfig.pending_*flag when ashell issues a default sink/source switch, then run the command once theServerInfoevent confirms the default actually changed. Re-selecting the current default is treated as a no-op and does not trigger the command.bash -c) viacrate::utils::launcher::execute_command.full_config.md,settings.md).Example config