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: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/5] emu10k1 SB Live: Master volume and front channels via fxbus 8,9
Date: Wed, 23 Feb 2005 11:22:40 +0100	[thread overview]
Message-ID: <s5hwtszshhr.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0502230956490.1748@pnote.perex-int.cz>

At Wed, 23 Feb 2005 10:00:49 +0100 (CET),
Jaroslav wrote:
> 
> On Wed, 23 Feb 2005, Mikael Magnusson wrote:
> 
> > > Sorry, but I don't understand very well why we need to have "PCM mix" FX
> > > buses. We can do this "down-mix" in the DSP code, but it's better to do it
> > > in application. My original DSP code for emu10k1 have only front, rear,
> > > center+lfe FX buses (6). I must miss something important here.
> > > 
> > 
> > I don't understand what you mean with "PCM mix". Are you thinking of the 
> > default output which are up-mixed to 5.1? The patch doesn't down-mix 5.1 
> > to front or something like that. It adds two fx inputs that are routed 
> > to front only and not up-mixed to 5.1. This is how the Audigy driver 
> > works. It also can make the configuration file a little cleaner, since 
> > it doesn't have to mute the up-mixed outputs.
> 
> I see now. My behaviour was to "duplicate" front to surround with "Wave 
> Surround" controls and you propose to have FX buses which will route 
> signal to both front & rear and separate FX buses to route signal to 
> front only.
> 
> I don't see the real benefit. Both cases are correct and the alsa-lib
> configuration won't be much different. Anyway, if you feel that it's
> better, then go ahead...

IIRC, the problem was stated in the case that both front and
multi-channel streams are output at the same time.

I think this patch is fine (although not tested yet).  At least, it
will decrease the difference between Live and Audigy.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-23 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 19:44 [PATCH 1/5] emu10k1 SB Live: Master volume and front channels via fxbus 8,9 Mikael Magnusson
2005-02-22  8:31 ` Jaroslav Kysela
2005-02-22 10:19   ` Mikael Magnusson
2005-02-22 10:19     ` Jaroslav Kysela
2005-02-22 11:38       ` Mikael Magnusson
2005-02-22 12:01         ` Jaroslav Kysela
2005-02-22 22:04   ` Lee Revell
2005-02-23  8:22     ` Jaroslav Kysela
2005-02-23  8:57       ` Mikael Magnusson
2005-02-23  9:00         ` Jaroslav Kysela
2005-02-23 10:22           ` Takashi Iwai [this message]
2005-02-25 16:59             ` 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=s5hwtszshhr.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --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