All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: James Courtier-Dutton <James@superbug.demon.co.uk>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Problem with multiopen on SB Audigy 2
Date: Wed, 08 Oct 2003 17:00:46 +0200	[thread overview]
Message-ID: <s5h7k3fai5d.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0310081643030.1357@pnote.perex-int.cz>

At Wed, 8 Oct 2003 16:44:02 +0200 (CEST),
Jaroslav wrote:
> 
> On Wed, 8 Oct 2003, Takashi Iwai wrote:
> 
> > > I'm still not sure, if we should handle these things in the driver.
> > > Hardware is not designed in this way and we should describe hardware
> > > in the driver as most accurate as we can.
> >
> > IMO, the master volume is a feature we mostly need.
> > in the case of emu10k1, it's much easier to implement this on the
> > driver (as a digital attenuator) rather than implementing it outside
> > the kernel space (except for the lack of GPR space).
> 
> Ok, but add more channels to "Master" so we have still a chance to control
> values independently.

now i'm thinking of a hierarchy like

	master (mono?)
	
	front(l/r)  rear(l/r) center/lfe ...
	
	outputs...

the advantage is that you can adjust all volumes with a single
control.  adjusting the level for each channel is done by the volumes
below it.  there is still a problem that the sensitivity is different
between front and surround volumes (the former is ac97 and the latter
is the digital attenuation).  perhaps it's solved when we introduce dB
hints.

or, yes, instead of the top master, we merge all the lower layers as
the master volume (either multi-channels or "master front", "master
rear", etc.)

perhaps we should create some templates of basic mixer designs suited
to different hardware implementations.  the confusion we're facing now
seems to come from the different implementation even though the same
control name is used.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  reply	other threads:[~2003-10-08 15:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 17:00 Problem with multiopen on SB Audigy 2 James Courtier-Dutton
2003-10-07 17:08 ` Takashi Iwai
2003-10-07 22:16   ` James Courtier-Dutton
2003-10-08 11:08     ` Jaroslav Kysela
2003-10-08 13:42       ` Takashi Iwai
2003-10-08 13:49         ` Jaroslav Kysela
2003-10-08 14:05           ` Takashi Iwai
2003-10-08 14:24             ` Jaroslav Kysela
2003-10-08 14:39               ` Takashi Iwai
2003-10-08 14:44                 ` Jaroslav Kysela
2003-10-08 15:00                   ` Takashi Iwai [this message]
2003-10-08 15:44                     ` Jaroslav Kysela
2003-10-08 15:58                       ` Takashi Iwai
2003-10-08 16:27                         ` Jaroslav Kysela
2003-10-09  1:14                           ` James Courtier-Dutton
2003-10-09 13:13                             ` Jaroslav Kysela
2003-10-08 22:36           ` Problem with multiopen on SB Audigy 2 / Mixer setting James Courtier-Dutton
2003-10-07 18:02 ` Problem with multiopen on SB Audigy 2 Jaroslav Kysela
  -- strict thread matches above, loose matches on Subject: below --
2003-10-09  6:52 p z oooo
2003-10-09 13:26 ` 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=s5h7k3fai5d.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    /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.