SUMMARY Changing PipeWire node channel volumes on the CLI doesn't update the volume widget. If we run pw-cli e 119 Props we can see that moving the slider changes the channelVolumes property, but not vice versa. STEPS TO REPRODUCE 1. Play some audio in the background 2. Find the ID of the PipeWire node playing said audio with pw-cli list-objects Node 3. Run pw-cli s <node_id> Props '{ mute: false, channelVolumes: [ 1.0, 1.0 ] }' , substituting node_id with your node ID OBSERVED RESULT Open the audio widget and notice how the audio slider for the application hasn't moved even though volume levels have changed EXPECTED RESULT The audio slider(s) should have moved to represent the new values. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 19.4 GiB of RAM Graphics Processor: AMD Radeon RX 6600 ADDITIONAL NOTES I tried wrapping the commands in a code block, but couldn't figure out the text formatting. If someone could point me to how to format the text, I'd be more than happy to do so.
I cannot reproduce this behavior with latest master and libpipewire 1.2.7, libwireplumber 0.5.5. Can you check if the volume is updated on another audio controller like pavucontrol?
(In reply to Ismael Asensio from comment #1) > I cannot reproduce this behavior with latest master and libpipewire 1.2.7, > libwireplumber 0.5.5. > > Can you check if the volume is updated on another audio controller like > pavucontrol? I checked and the issue persists. Playback levels do change, but no changes on the widget. I will try to attach a screenshot. wireplumber: 0.5.8 libpipewire 1.4.2
Created attachment 181249 [details] Screenshot showing the discrepency between pavucontrol and the volume widget
Oops, seems like I misunderstood. Pavucontrol does show changes made with pw-cli, but the changes in pavucontrol don't cascade to the audio widget. Sorry for the spam, couldn't figure out how to edit a previous comment.
(In reply to Otto from comment #4) > Oops, seems like I misunderstood. Pavucontrol does show changes made with > pw-cli, but the changes in pavucontrol don't cascade to the audio widget. Thanks! This was helpful. I wanted to rule out an issue with pipewire not notifying the change in their pipewire-pulse interface, but this seems not to be the case, as pavucontrol do show the changes > Sorry for the spam, couldn't figure out how to edit a previous comment. Don't worry. Unfortunately current bugzilla interface doesn't allow to edit comments