2008/4/10, Mark Knecht <markknecht@gmail.com>:
>
> On Thu, Apr 10, 2008 at 12:33 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> > "Mark Knecht" <markknecht@gmail.com> posted
> >  5bdc1c8b0804101043pdfacaeep2d6793d11ceac10@mail.gmail.com, excerpted
> >  below, on  Thu, 10 Apr 2008 10:43:10 -0700:
> >
> >
> >  > I cannot even remember anymore how many times these setting have
> fooled
> >  > me. I use a lot of audio apps and they have a tendency to leave some
> of
> >  > these settings in somewhat unknown states so starting here generally
> >  > works for me.
> >
> >  Same here.  No one's an idiot for missing some of those obscure
> function
> >  settings with even more obscure names, once in awhile.  It happens,
> which
> >  is exactly why I suggested covering the simple basics like that first.
> >
>
>
> I don't know if others have the same problem I do but every time I
> look at alsamixer I don't have a clue whether something is muted or
> not. I generally have to hit 'm' a few times to refresh my memory of
> which way it is set.
>
> Something about the visual design of that app doesn't automatically
> trigger for me.


to me alsamixer is quite a bore. i prefer to use alsa only to configure the
modules to load and the starting volumes. after that i use kde mixer to
adjust them. i think it's better, clearer and simpler. also i only have
front, sw-synth and cd out as mixers, since the other are useless and making
them visible might provoke problems like your.


-- 
dott. ing. beso