Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pulseaudio module only detects new default device after volume change #605

Closed
siwyd opened this issue Feb 26, 2020 · 3 comments · Fixed by #3464
Closed

pulseaudio module only detects new default device after volume change #605

siwyd opened this issue Feb 26, 2020 · 3 comments · Fixed by #3464
Labels
bug Something isn't working
Milestone

Comments

@siwyd
Copy link

siwyd commented Feb 26, 2020

I have a small script I use to quickly switch between output devices. Basically, it sets a new default device and moves all of the sink-inputs to the new sink. I've noticed that Waybar doesn't pick up the change of default device (reproducible when using Pulsemixer or something like that to pick a default device).

Waybar only seems to pick up on the new device when the volume is changed on it. So right now I have this hacky workaround in my script to have Waybar pick up the change:

ponymix increase 1
ponymix decrease 1

Would it be possible to have the module pick up the change in device without any volume changes?

@Alexays Alexays added the bug Something isn't working label Apr 5, 2020
@Alexays Alexays added this to the 1.0.0 milestone Apr 5, 2020
@mssdvd
Copy link

mssdvd commented Apr 6, 2020

i3blocks-contrib's module volume-pulseaudio has cool features like changing the default output and muting the volume.

@nolanl
Copy link

nolanl commented Aug 17, 2023

I have this problem as well, using pipewire's pulse compability. waybar 0.9.17 from Debian 12. Even changing the volume didn't fix it for me, I had to restart waybar for it to detect the change in output.

@xlucn
Copy link

xlucn commented Sep 23, 2024

Having this as well. Really hope this could be worked on.

What I observe:

  • Sometimes the pulseaudio module can't pick up the change of current device (usually when I connect/disconnect a bluetooth earphone) at all.
  • The volume change by scrolling on the module actually changes the device that the module shows at the time, not the actually used one.
  • Wireplumber module detects the change successfully.
  • Switch default devices back-and-forth in pavucontrol, and the module probably will detect it after that. Any reason device connection does not trigger the module to update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants