[Cooker] [Bug 4344] [alsa-utils] alsamixer fails to unmute sound channels on LM9.2 beta1
http://qa.mandrakesoft.com/show_bug.cgi?id=4344 --- Additional Comments From [EMAIL PROTECTED] 2003-28-07 02:49 --- All of that is valid to at least some degree, but what it isn't is any kind of bug in Mandrake. Mandrake packages alsamixer; the ALSA team write it. Close this as invalid and file a bug there. :) -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I am using the ALSA driver "snd-via82xx" and have these rpms: libalsa-data-0.9.5-1mdk libalsa2-0.9.5-1mdk alsa-utils-0.9.5-1mdk At boot, the driver's channels are all mutes (at zero). Now, if alsamixer is used to unmute them (set non-zero values), it has no effect since no sound can be heard even if alsamixer shows 100 for PCM and Master. However, if some other mixer (such as aumix) is used to unmute the sound channels to any non-zero values, alsamixer starts working fine. In brief, alsamixer cannot increase the volume (Master and PCM channels) if it starts from zero. This is a serious problem since after booting the ALSA drivers are muted and therefore it is impossible to get sound using alsamixer.
[Cooker] [Bug 4344] [alsa-utils] alsamixer fails to unmute sound channels on LM9.2 beta1
http://qa.mandrakesoft.com/show_bug.cgi?id=4344 --- Additional Comments From [EMAIL PROTECTED] 2003-28-07 02:01 --- Thanks for the clarification. I confirmed that pressing "m" alternately mutes and unmutes the channel. Basically, the muting option is like a digital 1/0 value which is multiplied with the actual value of the channel. Obviously, anything multiplied with zero is zero. The problem lies elsewhere. Kmix has buttons for muting which are very visible and obvious. I have also seen cases where kmix automatically sets the value of a channel to zero if it is muted. Aumix also does the same. But alsamixer obviously does differently. Given different mixers (kmix, gmix, aumix, xmix, alsamixer) follow different protocols, its hard to know which is doing what. Now, whatever be the "correct" behavior, the problem with alsamixer is that it does not say anything about pressing "m" (even though it says to press "esc" to quit) after it is started in a terminal. This is a design flaw. Adding a few more help lines like: Press "m" to toggle muting for the current channel would avoid such trouble. Note that the terminal version of aumix does a much better job and lists a set of keys needed to perform the basic functions of a mixer. Running "man alsamixer" and learning from it should be a last resort, not the first necessity in the GUI desktop world. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I am using the ALSA driver "snd-via82xx" and have these rpms: libalsa-data-0.9.5-1mdk libalsa2-0.9.5-1mdk alsa-utils-0.9.5-1mdk At boot, the driver's channels are all mutes (at zero). Now, if alsamixer is used to unmute them (set non-zero values), it has no effect since no sound can be heard even if alsamixer shows 100 for PCM and Master. However, if some other mixer (such as aumix) is used to unmute the sound channels to any non-zero values, alsamixer starts working fine. In brief, alsamixer cannot increase the volume (Master and PCM channels) if it starts from zero. This is a serious problem since after booting the ALSA drivers are muted and therefore it is impossible to get sound using alsamixer.
[Cooker] [Bug 4344] [alsa-utils] alsamixer fails to unmute sound channels on LM9.2 beta1
http://qa.mandrakesoft.com/show_bug.cgi?id=4344 --- Additional Comments From [EMAIL PROTECTED] 2003-28-07 00:15 --- The description of this bug is misleading; the bug is invalid. The volume level is separate from the "muted" property; that is, a channel may have a non-zero volume yet still be muted. Being "muted" does not equal having the volume set to zero. Some mixers assume that if the volume is zero and the channel is muted and the user then raises the volume they would "of course" also wish the channel to be unmuted and thus unmute it, but this is not necessarily the only "correct" behaviour. alsamixer does not make this assumption, and so if the channel is both set to zero and muted you must raise the volume and also press "m" to unset the "muted" property before you hear sound. This is intended behaviour, not a bug. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I am using the ALSA driver "snd-via82xx" and have these rpms: libalsa-data-0.9.5-1mdk libalsa2-0.9.5-1mdk alsa-utils-0.9.5-1mdk At boot, the driver's channels are all mutes (at zero). Now, if alsamixer is used to unmute them (set non-zero values), it has no effect since no sound can be heard even if alsamixer shows 100 for PCM and Master. However, if some other mixer (such as aumix) is used to unmute the sound channels to any non-zero values, alsamixer starts working fine. In brief, alsamixer cannot increase the volume (Master and PCM channels) if it starts from zero. This is a serious problem since after booting the ALSA drivers are muted and therefore it is impossible to get sound using alsamixer.
