[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#824059: plasma-desktop: When used with pulseaudio, can make people deaf



¡Hola Salvo!

El 2016-05-17 a las 11:33 +0200, Salvo Tomaselli escribió:
The problem occurs on my work computer, so it is a bit difficult for me to debug the issue.

However, I attach the list of my installed packages.

I have done aptitude purge pulseaudio to prevent hear loss, but I could install it again and not wear the headphones to make some tests.

The notification was a popup from amarok, explaining that if I close the main window, it will still be running in the tray area.

I had done no configuration to notifications or audio. I had installed kde-full, and configured themes, keyboard and other programs.

I'm adding some extra information about the bug, using pulseaudio's configuration flat-volumes = no (in /etc/pulse/daemon.conf) works correctly, the master volume is used for new applications without a volume configuration, and the volumes set in the applications are relative to the master volume.

Using the default flat-volumes = yes, the volume is tweaked on each input source, that is, the sound card volume is set to the one in the master volume and then moved to the relative value corresponding to the applications volume, (in particular for amarok this is done for each reproduced file, which can be heard at the end of each file as a volume increase).

On the amarok side of things, amarok seems to be ignoring the external volume changes in his volume control widget, the widget sets the initial value of the input source volume, and overrides the master volume if the master volume is less than the one set in the widget.

But at the same time, changing the amarok volume in some other way (using plasma-pa, kmix, pavucontrol, etc) is frustrating.

This was tested using virt-manager and it's probably behaving worse than how real hardware behaves. In any case, it would be better if the pulseaudio's default changes to flat-volumes = no.

On the phonon side of things, using phonon 4.8.3, amarok manages to ignore most of the events that would produce a notification while it's reproducing something, as trying to close amarok from the tray icon. Using phonon 4.9.0 (currently in experimental) amarok reacts to most of the events, but still not to all of them.

When there are two sound sources pulseaudio tries to use the volume of the loudest sound to mix the other one in relation with their relative volume levels. What happens here seems to be somewhat different if you are using the newer phonon or the old one, it seems that the in the new one uses the volume of the last that the sound cards volumes is tweaked and left either as it was, or at the maximum or somewhere in the middle, this might be related with the tweaks that are being produced at the end of each amarok sound file and the fact the notifications are quite short.

Using the newer phonon this behaviour seems to be sane, as the sound source uses the last volume level used by default, so no tweaking is necessary.

I still need to test this issue without pulseaudio, but it seems to me that a good chunk of the problem is solved with the newer phonon.

Happy hacking,
--
"recursividad 95, 154, 156, 201, 224, 293"
-- El Lenguaje de Programacion C, pag. 293 (Kernighan & Ritchie)
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: Digital signature


Reply to: