All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: New mixer api.
Date: Mon, 23 Jun 2003 16:36:22 +0100	[thread overview]
Message-ID: <3EF71E76.5070708@superbug.demon.co.uk> (raw)

Hi,

If a user has a 5.1 sound card, but only has 2 speakers connected, it 
would be nice if the user could tell alsa this fact.
Then the amount of sliders in the mixer could be reduced, and also, an 
application could detect what the user has set up.
It would be nice for the user to only have to tell one application(maybe 
the mixer app) that they only have 2 speakers connected to a 5.1 sound 
card, and then all other applications run by the user would 
automatically pick up that information.
It seems to me, that the best place to store this infomation is in alsa 
somewhere.
It would also be nicer to have a better description language for the 
mixer elements, so that a single GUI mixer, could draw a diagram of how 
each mixer element effects which other ones. This idea could probably be 
expanded for some sound cards, whereby the mixer GUI could be used to 
let the user design their own mixer setup. E.g. The SB Live could be 
programmed for all sorts of different mixing setups.
So, as a suggestion, each mixer element should have extra meta info like 
this: -
Entry: 1
Type: output
Description: Front Speakers.

Entry: 2
Type: Mixer
Description: Volume
Range: 1-100
Channels: Left and Right
Input comes from (3)
Output goes to (1).

Entry: 3
Type: input
Description: PCM stream from computer.

One could have multiple "Input comes from" and "output goes to" for each 
mixer element.

With this sort of information, a GUI could draw a nice diagram of the mixer.



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

             reply	other threads:[~2003-06-23 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 15:36 James Courtier-Dutton [this message]
2003-06-23 16:11 ` New mixer api Mark Knecht
2003-06-24  9:50 ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2003-11-08 23:20 James Courtier-Dutton
2003-11-09  8:00 ` Jaroslav Kysela

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=3EF71E76.5070708@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@alsa-project.org \
    /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.