Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pieter Palmers <pieter.palmers@student.kuleuven.ac.be>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: building a mixer
Date: Tue, 28 Jan 2003 10:22:14 +0100	[thread overview]
Message-ID: <s5hsmvdmxx5.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E35C4B3.5000004@student.kuleuven.ac.be>

At Tue, 28 Jan 2003 00:45:55 +0100,
Pieter Palmers wrote:
> 
> Hi all,
> 
> is it possible to support multiple mixers in one card?

no, on ALSA 0.9.0, there is only one control interface per card.

> I have the following situation:
> The card consists of a Maestro2E PCI controller with AC97 codec. On the 
> expansion port of the maestro is a SAM9707 device. I'd like separate 
> mixers for the AC97 and the SAM, because the control names can be very 
> confusing otherwise (i.e. Master volume of Codec does not change Master 
> volume of any SAM output).

it's possible to give the index value to the control element, so  that
the elements with the same name can coexist.

it's also possible to extend the existing API, of course, but i don't
think it's the best solution.
what we really need is a card-specific mixer application.  then you
can arrange the appearance more reasonably. 

i think either an external database giving the mixer topology or a
script-based mixer GUI which runs different scripts for each card will
be necessary.


Takashi


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

  reply	other threads:[~2003-01-28  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 23:45 building a mixer Pieter Palmers
2003-01-28  9:22 ` Takashi Iwai [this message]
2003-01-28 10:02 ` Uros Bizjak

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=s5hsmvdmxx5.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pieter.palmers@student.kuleuven.ac.be \
    /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