Volume control (when a Playback stream stops, eg app notification), add a delay so user can change volume

In the ‘System’ / ‘Sound Settings’ window (or the ‘Audio Volume’ notification pop-up, which shows each application’s playback stream volume (currently “playing audio streams”), when an application which uses sound only for notifications and does not seem to honour the ‘Notification Sounds’ ‘Playback Stream’ volume setting, it is very difficult to adjust the volume for such an application.

This is due to the application appearing only when there is playback. After playback is finished the application is quickly removed from the ‘Playback Streams’ list, therefore making volume adjustment of said application “very challenging”.

Adding a simple optional delay to the removal of applications in the ‘Playback Streams’ list will allow users to control the volume for such applications.

I propose adding in the ‘Configure Volume Controls’ windows, to add a tick-box object and an input control object like the ‘Volume Control step’ control next to it that has the value for the Playback Streams Application List delay feature. The input box should accepts values in seconds from 1 to 59 seconds.

If the feature is enabled (ticked tick-box), whatever value in the input box determines the delay before the removal of the application that has finished playback from the "Playback Streams’ list.

Thus allowing them to individually customize the playback volume of each application that uses notifications and isn’t lighting fast to get to the Volume ‘Playback Streams’ list and adjust the volume of said application.

For the Dev who gets this implemented, I will send a donation in USDT on the TON or BEP20 chain as a sign of appreciation and in supporting development of KDE Plasma.

1 Like

Very nice idea, but needs to have a toggle so it can be toggled on and off.

Correct, that is what the tickbox would do.
I should have drawn in a tickbox and the input box next to it.

1 Like

This is all just a front-end to pipewire and wireplumber. You’d need to actually change pipewire so that the stream was held open and filled with zeros (silence), so that it existed, to have a volume, which you could set.

It’s plasible but pretty messy, that you could have plasma write directly to the wireplumber state file, thus setting the volume for next time.

Of course, all of this assumes a default wireplumber configuration where the volumes are restored from the state file. That’s not mandatory behaviour, there are good reasons to disable it, and then this problem still exists.

You might like to have a read of this thread: Issues with Notification Volumes - #11 by pallaswept

This is confusing for everyone (including me) it seems. That slider only sets the notification sounds which are emitted by this application. So, it’s for the sounds that can be triggered when you move that volume slider. Only that. It’s not actually for all notifications.

After reading your post sounds like this could be done on the distro level, a bit much for Plasma on it’s own.

Do you have any suggestions where I can post the request for wider ‘distribution’ related to I guess the deb package stream?