From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: sudden sound loss
Date: Fri, 11 Apr 2008 10:14:47 +0200 [thread overview]
Message-ID: <d257c3560804110114uf816b41oaebdf65cb5f5867a@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0804101245t45d95992kd1397694c99e6d8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2207 bytes --]
next prev parent reply other threads:[~2008-04-11 8:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 11:43 [gentoo-amd64] sudden sound loss Mark Haney
2008-04-10 12:16 ` Raffaele BELARDI
2008-04-10 12:22 ` Mark Haney
2008-04-10 13:44 ` Raffaele BELARDI
2008-04-10 15:52 ` Chris Brennan
2008-04-10 12:45 ` Beso
2008-04-10 14:13 ` [gentoo-amd64] " Duncan
2008-04-10 14:30 ` Mark Knecht
2008-04-10 15:02 ` Duncan
2008-04-10 16:49 ` Mark Haney
2008-04-10 17:10 ` Mark Knecht
2008-04-10 17:20 ` Mark Haney
2008-04-10 17:43 ` Mark Knecht
2008-04-10 19:33 ` Duncan
2008-04-10 19:45 ` Mark Knecht
2008-04-11 8:14 ` Beso [this message]
2008-04-12 2:29 ` Duncan
2008-04-11 11:16 ` Mark Haney
2008-04-11 11:33 ` Raffaele BELARDI
2008-04-11 13:24 ` Mark Knecht
2008-04-11 14:33 ` Raffaele BELARDI
2008-04-11 15:32 ` Mark Knecht
2008-04-12 16:32 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d257c3560804110114uf816b41oaebdf65cb5f5867a@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox