From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Marc Titinger <titinger@digigram.com>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: dmix plugin
Date: Thu, 13 Feb 2003 10:51:20 +0100 [thread overview]
Message-ID: <s5h65romrtz.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0302122015190.30420-100000@pnote.perex-int.cz>
At Wed, 12 Feb 2003 20:21:31 +0100 (CET),
Jaroslav wrote:
>
> On Wed, 12 Feb 2003, Marc Titinger wrote:
>
> > This looks Great !
> >
> > I haven't yet experimented a lot with .asoundrc files, so please excuse
> > me if the following questions are irrelevant or OTO, but:
> >
> > I was wondering if one could define a plug pcm, that offers two stereo
> > pairs routed with policy "average" to a single-stereo "hw" slave.
> >
> > My understanding is that until this dmix pcm, there was no "official"
> > means supported by alsalib to achieve software mix of streams comming
> > from differents apps.
>
> Yes, that's true.
well, route (or plug) has the capability for software mix (in a
certain meaning), but not for separate pcm streams. you can downmix
the multi-channels in a stream via route plugin if the channels is
given.
but it's defenitely different from what dmix plugin does, and perhaps
it's different from what Marc wants, too...
> > Could I have one app open the first pair of my hypothetic plug pcm, and
> > another app open the second pair ? I guess this would be managed like a
> > concurrent access to a pcm, and block or fail the second open() call.
> >
> > Would'nt it be nice to create a dmix pcm "behind" a such plug pcm, to
> > provide mix in a transparent way ?
>
> Some cards with multiple open hardware acceleration doesn't need this
> default. Also, the dmix plugin has some limited things so I don't prefer
> to select it as default.
agreed here, although i feel it's also nice to set it as default for a
consumer card which has no hardware mix function.
please note that you can re-define the default in asoundrc.
if you want to set up dmix as the system default, you can define it in
/etc/asound.conf, too.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-02-13 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 18:04 dmix plugin Marc Titinger
2003-02-12 19:21 ` Jaroslav Kysela
2003-02-13 9:51 ` Takashi Iwai [this message]
2003-02-13 16:30 ` Jaroslav Kysela
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 10:04 Jaroslaw Sobierski
2003-02-13 10:28 Marc Titinger
[not found] <20030212125323.C75F059D34D@kerberos.suse.cz>
2003-02-12 13:32 ` Jaroslav Kysela
2003-02-12 9:45 Jaroslav Kysela
2003-02-12 12:18 ` Takashi Iwai
2003-02-12 13:55 ` Jaroslav Kysela
2003-02-12 12:57 ` Paul Davis
2003-02-13 13:10 ` Abramo Bagnara
2003-02-16 13:27 ` Jaroslav Kysela
2003-02-16 18:00 ` Abramo Bagnara
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=s5h65romrtz.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
--cc=titinger@digigram.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