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
I have uninstalled PulseAudio and use plain ALSA. MATE Volume Control has started to behave differently: anything below 50% is inaudible, and all the action occurs between about 70 & 100.
In AlsaMixer the scale is perceived almost linear.
Screenshots show that changing the volume in MATE Volume Control also changes the volume in AlsaMixer. But, as said above, the scale of AlsaMixer is perceived almost linear so the scale in MATE Volume Control is perceived like logarithmic one.
The text was updated successfully, but these errors were encountered:
LavirtheWhiolet
changed the title
mate-volume-control controls volume non-linearly when ALSA is used
mate-volume-control controls volume non-linearly when ALSA backend is used
Oct 30, 2015
LavirtheWhiolet
changed the title
mate-volume-control controls volume non-linearly when ALSA backend is used
MATE Volume Control adjusts volume in highly non-linear way when ALSA backend is used
Oct 30, 2015
From the screenshot you are using the gst-mixer from MATE 1.8 which is unsupported software. The current mixer in MATE 1.10 and 1.12 should not exhibit this behaviour (if it does, please let us know), although it's currently lacking in support for secondary channels on ALSA (I hope we'll improve this soon). So in short, please use a more recent mixer.
I have uninstalled PulseAudio and use plain ALSA. MATE Volume Control has started to behave differently: anything below 50% is inaudible, and all the action occurs between about 70 & 100.
In AlsaMixer the scale is perceived almost linear.
Screenshots show that changing the volume in MATE Volume Control also changes the volume in AlsaMixer. But, as said above, the scale of AlsaMixer is perceived almost linear so the scale in MATE Volume Control is perceived like logarithmic one.
The text was updated successfully, but these errors were encountered: