Alsa-Devel Archive on 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 16:39:22 +0200	[thread overview]
Message-ID: <s5h8ynvaj51.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0310081619270.1357@pnote.perex-int.cz>

At Wed, 8 Oct 2003 16:24:33 +0200 (CEST),
Jaroslav wrote:
> 
> On Wed, 8 Oct 2003, Takashi Iwai wrote:
> 
> > > but if DVD (or other 4+.0+ format) is used, then use channels
> > > independently. It appears that James is trying to do something
> > > non-standard (perhaps playing two DVDs simultaneously), so I am not sure,
> > > if we should have these things in our configurations.
> > >
> > > It's something like "auto" stuff, but I would like to avoid user
> > > confusion.
> >
> > hmm, now i see the problem.  i think disabling "wave surround, center,
> > lfe" doesn't belong to the rear or center/lfe pcm, but it's necessary
> > for front pcm.  or even better if we have FX bus bypassing these
> > duplications.
> 
> Yes, new FX bus will solve it, but on plain EMU10K1 chips, we're running
> out of GPRs.

grrr...

> > > Anyway, users are already confused with emu10k1+ mixers, so we have to do
> > > things more simple.
> >
> > yep, i'd like to see the new design of the routing/volume.
> >
> > at least, it'd be nice to have:
> >
> > - a new real "master" volume for all channels
> 
> 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).


Takashi


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

  reply	other threads:[~2003-10-08 14:39 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 [this message]
2003-10-08 14:44                 ` Jaroslav Kysela
2003-10-08 15:00                   ` Takashi Iwai
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=s5h8ynvaj51.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox