All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Eliot Blennerhassett <linux@audioscience.com>,
	alsa-devel@alsa-project.org
Subject: Re: asihpi: Control naming
Date: Tue, 05 Oct 2010 18:10:27 +1300	[thread overview]
Message-ID: <4CAAB343.9040603@audioscience.com> (raw)
In-Reply-To: <s5haamz9che.wl%tiwai@suse.de>

On 01/10/10 09:56, Takashi Iwai wrote:

> So, you have matrix volumes.  We had discussions how to implement
> the matrix volumes, and there is actually an infrastructure to
> handle multi-dimension volume arrays.  But, no driver is using the
> feature, IIRC...


Further on the subject of playback vs capture vs other...
Of course we do have controls that are obviously "Playback" or "Capture",
however we also have controls that connect PCM out to PCM in i.e. both
Playback and Capture are involved,

"PCM0 to PCM1 Playback Capture Volume"  .. nooo!
"PCM0 to PCM1 Loop Volume"  ???

and others that connect linein to lineout ie. neither Capture or
Playback involved.

"LineIn2 to LineOut3 Volume"
maybe "LineIn2 to LineOut3 Loop Volume" ?

> 
>> Also, on the input multiplexer (route?), the options are
...
>> I.e. the names match, rather than using indices in one place, and
>> distinct names in another
> 
> One (known) remaining problem is the matching between an enum item
> string to a control (or mixer) with an index number.  

Exactly!

> For example,
> some HD-audio codecs have multiple mics, and a similar problem appears
> there.
> 
> 
> Takashi


-- 
Eliot Blennerhassett
AudioScience Inc.

  parent reply	other threads:[~2010-10-05  5:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30  3:44 asihpi: Control naming Eliot Blennerhassett
2010-09-30  5:46 ` Takashi Iwai
2010-09-30 20:23   ` Eliot Blennerhassett
2010-09-30 20:56     ` Takashi Iwai
2010-09-30 21:28       ` Sebastian H.
2010-10-01  7:05         ` Clemens Ladisch
2010-10-01 11:31           ` Sebastian H.
2010-10-01 12:45             ` Raymond Yau
2010-10-01 13:19             ` Clemens Ladisch
2010-10-01 20:06               ` Sebastian H.
2010-10-02  4:10                 ` Raymond Yau
2010-10-02 11:10                   ` Sebastian H.
2010-09-30 23:47       ` Mark Brown
2010-10-05  5:10       ` Eliot Blennerhassett [this message]
2010-10-05  7:07         ` Clemens Ladisch
2010-10-05  8:14           ` Eliot Blennerhassett
2010-10-05  8:15           ` Eliot Blennerhassett
2010-10-05  9:47             ` Clemens Ladisch
2010-10-05  9:53               ` Takashi Iwai
2010-10-06 22:55               ` asihpi: Control naming, Irritated Currant edition Eliot Blennerhassett
2010-09-30 20:56     ` asihpi: Control naming Takashi Iwai
2010-09-30  6:28 ` David Henningsson

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=4CAAB343.9040603@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    --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 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.