From: "Sebastian H." <vand2@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Eliot Blennerhassett <eblennerhassett@audioscience.com>,
Eliot Blennerhassett <linux@audioscience.com>,
alsa-devel@alsa-project.org
Subject: Re: asihpi: Control naming
Date: Thu, 30 Sep 2010 23:28:46 +0200 [thread overview]
Message-ID: <4CA5010E.4050705@gmx.de> (raw)
In-Reply-To: <s5haamz9che.wl%tiwai@suse.de>
>>> "PCM 3 Capture Meter" is regarded as a playback control since it has
>>> an invalid (unknown) suffix. If it's "PCM 3 Meter Capture Volume",
>>
>> But it is not a volume, it is a level meter?!
>> We also have controls for tuners, microphones, equalizers, sampleclocks
>> etc. Surely these can't be all "Volume" or "Switch"
>> I'm not sure why the suffix has any bearing on the direction?
>
> Actually, this control is handled as a "neutral" control without
> the directional attribute. alsamixer or else may show it in the
> playback but also may show in capture, too.
>
This is interesting. In alsamixer-qt4 I've just stumbled over
enum elements for which both
snd_mixer_selem_is_enum_playback and
snd_mixer_selem_is_enum_capture
return 0/false (2.6.32 kernel emu10k1 chip).
May I drop the question in if this state can be considered valid
and besides *playback* and *capture* elements there's a third group of
*neutral* elements?
(On the other hand switches and volumes are always directed.)
Right now I handle it by dumping a warning message to stdout
and puting it into the playback direction element list.
Sebastian
next prev parent reply other threads:[~2010-09-30 21:26 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. [this message]
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=4CA5010E.4050705@gmx.de \
--to=vand2@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=eblennerhassett@audioscience.com \
--cc=linux@audioscience.com \
--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