You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the volume slider is shown next to the standard system volume slider making it messy the settings messy and unclear. It would be way more clear which app the volume slider belongs to if it was integrated into the appropriate volume slider.
Current Implementation
Suggested Implementation
The text was updated successfully, but these errors were encountered:
I would have done it this way, but there is no way to associate these two everytime. The one on the buttom uses the MPRIS interface which applications fully or partially implement. For example Spotify implements volume control, loop, shuffle control and everything else and so it can be controlled through mpris alone, but playing youtube on firefox only implements play-pause next and previous actions. The one under the system volume slider uses Gvc and anything that plays sound, even the system sounds are going to show up there. The issue is that they don't necessarily have a common id or something which you can use to pair them, and even if there were, there would be still complications, for example having two videos playing in firefox will display two sliders for them but the mpris one would still only show one.
Make sense however there is still a way to make the slider look better and more neat. Currently, it the slider section looks cluttered and it would be nice if they were grouped together, for example an expandable section only for app volume. Or maybe add the app volumes into the main volume slider.
Thanks for your work it is much appreciated.
Currently, the volume slider is shown next to the standard system volume slider making it messy the settings messy and unclear. It would be way more clear which app the volume slider belongs to if it was integrated into the appropriate volume slider.
Current Implementation

Suggested Implementation

The text was updated successfully, but these errors were encountered: