[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration

2023-05-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467123

--- Comment #17 from ak...@iname.com ---
Forgot to add that this is on Fedora 37, Plasma 5.27.4.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration

2023-05-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467123

ak...@iname.com changed:

   What|Removed |Added

 CC||ak...@iname.com

--- Comment #16 from ak...@iname.com ---
For me "raise maximum volume" keeps the max volume level at 100%, not 150% like
it used to.
I can still raise the volume with "pactl set-sink-volume @DEFAULT_SINK@ 150%"
but the level meter stays at 100%.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration

2023-04-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467123

--- Comment #15 from mrantonsae...@gmail.com ---
Created attachment 157882
  --> https://bugs.kde.org/attachment.cgi?id=157882=edit
when scrolling over plasma widget.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration

2023-04-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467123

--- Comment #14 from mrantonsae...@gmail.com ---
No, I think it does not matter,  but u just tried scrolling over it, and it
fixes the problem, everything shows like it should.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration

2023-04-05 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=467123

--- Comment #13 from Ismael Asensio  ---
I cannot fully reproduce, but found a small quirk that might or might not be
related.

Does this only happen with the volume buttons, or also if you change the volume
by scrolling over the plasma applet (mouse wheel-scrolling or touchpad
equivalent)?

Also, does it make a difference if you change the profile in the Audio settings
page (full dialog) vs changing it in the applet?

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration

2023-04-05 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=467123

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Target Milestone|1.0 |---
  Component|general |general
Summary|When Raise maximum sound is |When Raise maximum sound is
   |turned on, sound OSD only   |turned on, sound OSD can
   |shows 100% and shows wrong  |show wrong volume level
   |volume level|depending on the audio
   ||profile used and audio
   ||hardware configuration
 Resolution|WAITINGFORINFO  |---
Product|plasmashell |plasma-pa
 CC||isma...@gmail.com,
   ||m...@ratijas.tk,
   ||now...@gmail.com
 Status|NEEDSINFO   |CONFIRMED

--- Comment #12 from Nate Graham  ---
Got it. It does seem like the audio profile makes a difference.

When I have only one audio device (my laptop's internal audio card), both the
"Play HiFi quality Music" and "Pro Audio" profiles work properly. But when I
plug in a thunderbolt dock that includes a headphone jack, it shows up as a
second audio device, and while this second audio device is visible, switching
the laptop audio card to "Pro Audio" breaks it in the way you've described.

So this isn't exactly the same issue you're seeing, but it seems related, and
the audio profile is a relevant data point.

-- 
You are receiving this mail because:
You are watching all bug changes.