Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "D. Hugh Redelmeier" <hugh@mimosa.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: newbie problem with control settings
Date: Fri, 01 Apr 2005 11:55:01 +0200	[thread overview]
Message-ID: <s5hu0mqes96.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0503311400560.4699@redshift.mimosa.com>

At Thu, 31 Mar 2005 14:07:17 -0500 (EST),
D. Hugh Redelmeier wrote:
> 
> | From: Takashi Iwai <tiwai@suse.de>
> 
> | > >     Line-in jack is:
> | > > 
> | > >     [*] Line-in
> | > >     [ ] bass output
> | > >     [ ] rear Left and Right output
> | > 
> | > This sounds nice.  The (untested) patch below changes the handling of
> | > these controls as you proposed.
> | 
> | Can any one test the patch?
> 
> Thanks very much for this patch.  Unfortunately I am unable to test
> it.
> 
> I do have a question about the patch.  How is a mixer supposed to find
> out the names of the three possible values?  I see that there is a new
> control named "Mic-In Mode" but I don't see where the possible
> settings are described.

"Line-In Mode" and "Mic-In Mode" are enum controls.
You can find their items in their info callbacks.
The former has "Line-In", "Rear Output" and "Bass Output", while the
latter has "Mic-In" and "Center/LFE Output".


Takashi


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

  reply	other threads:[~2005-04-01  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23  7:04 newbie problem with control settings D. Hugh Redelmeier
2005-03-23 18:07 ` Takashi Iwai
2005-03-29 16:08   ` Takashi Iwai
2005-03-31 19:07     ` D. Hugh Redelmeier
2005-04-01  9:55       ` Takashi Iwai [this message]
2005-03-24 10:06 ` Clemens Ladisch
2005-03-24 15:27   ` Lee Revell

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=s5hu0mqes96.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hugh@mimosa.com \
    /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