From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Mixer control elements.
Date: Fri, 11 Oct 2002 12:14:10 +0200 [thread overview]
Message-ID: <s5hofa1cmfh.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DA63B37.5020109@superbug.demon.co.uk>
At Fri, 11 Oct 2002 12:45:11 +1000,
James Courtier-Dutton wrote:
>
> Hello
> I was wondering how easy it would be to add a classification to each
> control element. (switches, volume, capture on/off etc.)
> The classification would be as follows: -
> 1) Used during capture. I.E. Switches and volume controls for anything
> one can record.
> 2) Used during playback. I.E. Switches and volume controls for anything
> one can play.
> 3) General control. I.E. Hardware config. E.g. The SB Live
> Digital/Analogue switch for Digital SPDIF out/Analogue Center and LFE
> audio out.
i think the easiest way is to check the control name whether it
contains "Playback" or "Capture" substring.
> Then have alsamixer be able to filter the display using these 3 categories.
> User presses a key, and alsamixer displays only the controls used to
> effect sound playback.
> User presses another key, and alsamixer displays only the controls used
> to effect sound recording.
> User presses another key, and alsamixer displays only the controls used
> to do other stuff.
>
> This sort of functionallity could help users understand what each
> control does better.
> In my view the SB Live has so many controls, it is very difficult to
> sort out which ones to use.
>
> Currently, alsamixer seems to link playback and record volumes, that
> should be separate.
agreed. we need a better grouping method, anyhow.
i believe that the mixer is one of the biggest TODOs in ALSA.
since the mixer topology is really dependent upon the card, it's not
easy for a mixer application to build up the proper look and feel only
from the control API.
for example, "send volume" or "routing" of emu10k1 should not appear
on the normal mixer.
my idea is to provide an external database for each card, so that the
mixer app parses it for its GUI. perhaps a script language is
suitable for such a purpose.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2002-10-11 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 2:45 Mixer control elements James Courtier-Dutton
2002-10-11 10:14 ` Takashi Iwai [this message]
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=s5hofa1cmfh.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.