All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: alsa-devel@lists.sourceforge.net
Subject: Mixer control elements.
Date: Fri, 11 Oct 2002 12:45:11 +1000	[thread overview]
Message-ID: <3DA63B37.5020109@superbug.demon.co.uk> (raw)

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.

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.

Cheers
James





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2002-10-11  2:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11  2:45 James Courtier-Dutton [this message]
2002-10-11 10:14 ` Mixer control elements Takashi Iwai

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=3DA63B37.5020109@superbug.demon.co.uk \
    --to=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.