| Summary: | Maximum volume increase (boost volume) per app not available from plasmoid anymore | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma-pa | Reporter: | Marcelo Bossoni <mmbossoni> |
| Component: | applet | Assignee: | David Rosca <nowrep> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | nate, plasma-bugs-null, shtetldik |
| Priority: | NOR | ||
| Version First Reported In: | 5.19.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Firefox still at 100% even if increase maximum volume is checked | ||
|
Description
Marcelo Bossoni
2020-06-11 00:20:43 UTC
The functionality is now visible in the main view itself, via the checkbox on the bottom of the plasmoid. :) Although it works for main volume, it doesn't apply per application. (Application tab of the volume plasmoid) Created attachment 129233 [details]
Firefox still at 100% even if increase maximum volume is checked
The "raise maximum volume" setting is now systemwide, not per-device or per-app. So Firefox's effective maximum volume is likewise raised when you check the checkbox. (In reply to Nate Graham from comment #4) > The "raise maximum volume" setting is now systemwide, not per-device or > per-app. So Firefox's effective maximum volume is likewise raised when you > check the checkbox. I can raise maximum volume per application for example using pavucontrol-qt. It's also doable in System Settings > Audio > Playback Streams. So why can't it be conveinetly done from the Audio Volume plasmoid anymore? Right now to raise it for individual application requires opening pavucontrol-qt or doing these multiple steps: click on audio volume icon > click on sandwich menu icon (More actions) > Configure audio devices > Playback Streams. It should be simpler by checking Raise Maximum volume checkbox in the Applications tab there and increasing the volume above 100% right there. So I'd say it's a regression and would be good to reopen this. Should I open a separate bug about it? I think this one is good already to indicate the problem. |