Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Lee Revell <rlrevell@joe-job.com>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: How to display mixer controls to the user? was:Re: [PATCH/RFC] emu10k1 multichannel PCM
Date: Wed, 17 Nov 2004 12:54:54 +0100	[thread overview]
Message-ID: <s5hmzxgsnap.wl@alsa2.suse.de> (raw)
In-Reply-To: <4197433E.80008@superbug.co.uk>

At Sun, 14 Nov 2004 11:36:30 +0000,
James Courtier-Dutton wrote:
> 
> Lee Revell wrote:
> > On Fri, 2004-11-12 at 18:07 -0500, Lee Revell wrote:
> > 
> >>This patch is still missing a few things, like dynamic voice allocation
> >>and correctly setting the send routing, but it does work with JACK, and
> >>should not interfere with the operation of the other devices.   I tested
> >>it like so:
> > 
> > 
> > Here is a patch that adds the mixer controls for this device.  This
> > includes the previous patches (add multichannel support and add register
> > dump to /proc)  Unfortunately this adds 16 x 3 mixer controls... people
> > complain enough about the emu10k1 mixer already, so this might not be
> > well received in some circles.  I am not sure what to do about this.
> > The kX mixer probably has hundreds of controls, but they are arranged in
> > a tree structure.
> > 
> 
> I have similar problems with the mixer controls. If I add 
> p16v(24bit/96khz etc.) support to the emu10k1 driver, it will add a load 
> more controls. For example, the volume controls for the 96khz channel 
> are separate from the volume controls for emu10k1 48khz channels.
> Maybe we need to start discussing ways to separate out mixer controls 
> better.
> E.g.
> Global controls.
> Controls specific to a pcm device.
> Controls specific to a particular section of DSP code.

They can be specified via different iface values.  For example, the
above cases can be distinct with IFACE_MIXER, IFACE_PCM and IFACE_CARD
(or HWDEP), respectively.

IMO, the emu10k1 routing should go to IFACE_PCM instead of
IFACE_MIXER.  (Who wants to change it on the mixer?)
Well, we have to be still careful about the compatibility, though...


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

  parent reply	other threads:[~2004-11-17 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 23:07 [PATCH/RFC] emu10k1 multichannel PCM Lee Revell
2004-11-14  4:18 ` Lee Revell
2004-11-14 11:36   ` How to display mixer controls to the user? was:Re: " James Courtier-Dutton
2004-11-15  4:10     ` Lee Revell
2004-11-17 11:54     ` Takashi Iwai [this message]
2004-11-17  6:22   ` Lee Revell
2004-11-17 13:44     ` Takashi Iwai
2004-11-17 16:37       ` Lee Revell
2004-11-17 22:48       ` Lee Revell
2004-11-18 13:32         ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2004-11-15 13:49 How to display mixer controls to the user? was:Re: " Peter Zubaj
2004-11-15 17:29 ` Lee Revell

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=s5hmzxgsnap.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rlrevell@joe-job.com \
    /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