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

Bug#748124: kmix: Volume in kmix not equal to alsamixer (logarithmic scale / "mapped volume" should be used)



Control: tag -1 + upstream
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=331582

¡Hola vitalif!

El 2014-05-14 a las 18:25 +0400, vitalif@yourcmc.ru escribió:
> Starting with 4.10, kmix has incorrect volume regulation for me. I.e. it
> adjusts the volume linearly, while the correct behaviour is to adjust it
> logarithmically (in dB...). So the volume scale is incorrect, very
> unintuitive and the volume level isn't equal to alsamixer's. I use plain
> ALSA.

Interesting, is there any reference about whether the alsa interface provides
a logarithmic or linear values?

Do you know if there is a special case for certain sound cards?

If alsamixer handles this correctly it may be that the alsamixer code is the
documentation.

> I DON'T use PulseAudio and DON'T want to use it, because PA is a
> totally useless Lennart creation, wrapper around ALSA.

Please avoid this kind of hate mail comments, you are only adding yourself and
your efforts in an auto ignore list.

> I personally solve this problem on my machines by by applying the patch
> (attached) which makes kmix use mapped volume. But I've already reported
> this bug to KDE bugtracker - https://bugs.kde.org/show_bug.cgi?id=331582 -
> and they say KMix never used the logarithmic / dB values! So this is
> probably not a kmix issue!

I've added the forward information so if the bug state change we get noticed
of the update.

> Both machines on which the bug does reproduce run Debian unstable i386, both
> aren't a fresh installation - I continuosly upgrade them since debian 4.0
> etch. So maybe the bug is somehow related to ALSA setup on Debian? If so,
> the single alsa-related upgrade on my machine was libasound2 1.0.27.2-1 ->
> 1.0.27.2-3, happened 2014-01-03... As I remember that was somewhere around
> when it broke the first time... And the previous update happened 2013-07-16,
> 1.0.27.1-2 -> 1.0.27.2-1, and everything was OK...

Are you able to revert the issue by installing libasound2 1.0.27.2-1 ?
If that's the case a bisect might be productive.

Happy hacking,
-- 
"pi seconds is a nanocentury" -- Tom Duff
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: Digital signature


Reply to: