public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Gene Heskett <gene.heskett@verizon.net>,
	linux-kernel@vger.kernel.org, Andrew Benton <b3nt@ukonline.co.uk>,
	Takashi Iwai <tiwai@suse.de>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA problems with 2.6.18-rc3
Date: Wed, 09 Aug 2006 18:11:37 -0400	[thread overview]
Message-ID: <1155161498.26338.216.camel@mindpipe> (raw)
In-Reply-To: <200608092307.27615.s0348365@sms.ed.ac.uk>

On Wed, 2006-08-09 at 23:07 +0100, Alistair John Strachan wrote:
> > It's impossible to predict the effect of some mixer controls across
> the
> > wide range of hardware that ALSA supports.  What makes sound work on
> one
> > machine is likely to break it on another.
> 
> However, ALSA _has_ defaults for these controls, which I believe are 
> usually "off" or "zero". All I'm suggesting is that these defaults are
> plainly suboptimal for emu10k1, and probably other cards to which this
> statement simply does not apply. Shipping defaults is one thing, but
> shipping useless defaults is quite another. We have policy all over
> the kernel for providing "sane defaults" e.g. filesystem mount
> options. 

I think muted is a sane default - the only sane default.  Otherwise you
could damage speakers or hearing.  Also many devices will be noisier if
unused inputs are enabled.  Is it really that hard for users to unmute
the mixer or for distros to create their own config?

Also, analog output on my emu10k1 works perfectly with "External
Amplifier" disabled.

Lee


  reply	other threads:[~2006-08-09 22:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 20:28 ALSA problems with 2.6.18-rc3 Andrew Benton
2006-08-08 21:50 ` Lee Revell
2006-08-09 16:30   ` Andrew Benton
2006-08-09 16:35     ` Lee Revell
2006-08-09 16:51       ` [Alsa-devel] " Liam Girdwood
2006-08-09 18:17       ` Gene Heskett
2006-08-09 20:41         ` Lee Revell
2006-08-09 20:51           ` Gene Heskett
2006-08-09 20:57             ` Lee Revell
2006-08-09 21:22               ` Alistair John Strachan
2006-08-09 21:34                 ` Lee Revell
2006-08-09 22:07                   ` Alistair John Strachan
2006-08-09 22:11                     ` Lee Revell [this message]
2006-08-09 22:28                       ` Alistair John Strachan
2006-08-09 22:49                         ` Lee Revell
2006-08-10  8:47                         ` Takashi Iwai
2006-08-10  1:47               ` Gene Heskett
2006-08-10 13:13       ` [Alsa-devel] " Takashi Iwai
2006-08-09 10:58 ` Takashi Iwai

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=1155161498.26338.216.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=b3nt@ukonline.co.uk \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=tiwai@suse.de \
    /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