Closed Feanor1397 closed 2 years ago
Can attest. This weird behavior started about a week ago or so. I was meddling with internet radios so I thought that was the cause...
[2022-02-03T22:59:43+0200] [ALPM] upgraded pipewire (1:0.3.44-1 -> 1:0.3.45-1)
[2022-02-03T22:59:43+0200] [ALPM] upgraded pipewire-pulse (1:0.3.44-1 -> 1:0.3.45-1)
Did some digging and it seems that the pipewire update (on arch repos at least) matches with the date when these errors started occurring. Since MPD wasn't updated during this time I think this is a bug or very retarded feature from pipewire to reset application volume.
A relevant discussion about this can be found on pipewire's issues page. The basic gist is that volume is restored by a session manager, which is by default pipewire-media-session. However, it seems to be broken currently so you can either:
wireplumber
sudo pacman -U /var/cache/pacman/pkg/pipewire-pulse-1\:0.3.43-5-x86_64.pkg.tar.zst
sudo pacman -U /var/cache/pacman/pkg/pipewire-1\:0.3.43-1-x86_64.pkg.tar.zst
This issue should be closed because it is not related to MPD.
Yeah, just looked in .config/pipewire/media-session.d/restore-session
There was line "restore.stream.Output/Audio.application.name:mpv": { "volume": 1.000000, "mute": false, "volumes": [ 1.000000, 1.000000 ], "channels": [ "FL", "FR" ], "target-node": "alsa_output.pci-0000_09_00.6.analog-stereo" },
Deleted it, now everything works fine.
Bug report
Describe the bug
When output set to hardware mixer, volume are reset to 100% after disabling and enabling output. Some times this happens even between songs. It worked fine for years with this config (except used pulse output) and this strange behavior started for no reasons. Nothing was updated, no configs was changed. Now it's 100% reproducible for me. Tried changing output from pulse to native pipewire - same bug.
System - Archlinux Sound server - Pipewire 0.3.45
Expected Behavior
Volume set to level it was before disabling
Actual Behavior
Volume always set to 100%
Config
Version
Log