Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: asihpi: Control naming
Date: Thu, 30 Sep 2010 16:44:14 +1300	[thread overview]
Message-ID: <4CA4078E.6010601@audioscience.com> (raw)

Hi all,

I'm struggling with getting the correct names for controls, so that they
show up correctly in the Playback or Capture modes of alsamixer

E.g. "PCM 3 Capture Meter" appears in the playback controls?

How is capture vs playback display determined?
or to put it another way: What are the rules for creating control names.

Here is a reduced schematic of one of our cards (in reality more
channels e.g. 4 physical stereo ins and outs, 12 players, 8 recorders)
All players and inputs are mixed to outputs.
All inputs and players multiplexed to each capture.

How should all these controls be named?


                               (1)-[vol]--+
                               (2)-[vol]--+
[play0]--[vol]--[meter]--[mode]--,-[vol]--+----[vol]-[meter]--[level]--[lineout0]
                                 `-[vol]--|-.
                                          | |
                                 .-[vol]--' |
[play1]--[vol]--[meter]--[mode]--'-[vol]----+--[vol]-[meter]--[level]--[lineout1]
                               (1)-[vol]----+
                               (2)-[vol]----+

[linein0]-[level]-\                     \
                mux>-[meter]-(1)-,-------|\
[digitalin0]------/              |    mux >--[mode]--[meter]--[cap0]
                                 |    ,../
                                 |   |
                                  `--|--\
[linein1]-[level]-\                  |   >--[mode]--[meter]--[cap1]
                mux>-[meter]-(2)-----'--/
[digitalin1]------/

notes
[level] means calibrated reference level setting in dBu
[mode] stereo channel modifier
+ summing junction
--|-- wires cross, no join
(1) connect from input to matrix mix output

thanks and regards

-- 
Eliot Blennerhassett
AudioScience Inc.

             reply	other threads:[~2010-09-30  3:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30  3:44 Eliot Blennerhassett [this message]
2010-09-30  5:46 ` asihpi: Control naming 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
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=4CA4078E.6010601@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox