All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Rush <jeff@taupro.com>
To: alsa-devel@alsa-project.org
Subject: Call for Explanation of ALSA Config Behavior
Date: Sat, 05 May 2007 02:24:32 -0500	[thread overview]
Message-ID: <463C3130.1070105@taupro.com> (raw)

I'm trying to get ALSA to support all the little features of my laptop, which
is based on the Intel HDA chipset with the Realtek codec.  I'm also playing
with the softvol plug to add a volume controls over certain virtual devices.

A few questions I can't figure out:

1. Isn't it the standard convention that there be a control named "Master"
   that adjusts the overall volume of a device?  So why does the Intel HDA
   ALSA driver define one named "Headphone" that does the same thing instead
   of following that convention?  Is there some reason, or perhaps a
   difference in opinion within the ALSA community on the naming of controls?
   Shouldn't every ALSA driver define a "Master" control?

2. When I add a control using the softvol plugin, the mixer GUI shows it in
   both the playback and the capture set of controls.  Why and how can I
   tag a control to belong to only one set or the other?  Being a volume
   control it seems it should only be in the playback collection.

3. Once I add such a control, it -never- goes away.  What I mean is that if
   I rename it, or remove it, and restart ALSA or even restart the entire
   computer, the old name for the control always shows up in the mixer GUI.
   I've grepped *all* of /etc, looking in the /etc/asound.conf,
   /etc/asound.state and ~/.asoundrc files but the old name isn't anywhere
   --  where is it coming from?

Thanks very much for any help you can provide,  For years I've just tried to
"use" ALSA but now I'm trying to actually understand its subtle nuances.

-Jeff

             reply	other threads:[~2007-05-05  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05  7:24 Jeff Rush [this message]
2007-05-05  8:30 ` Call for Explanation of ALSA Config Behavior Ingo Müller

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=463C3130.1070105@taupro.com \
    --to=jeff@taupro.com \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.