From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Dan Tihelka <dtihelka@kky.zcu.cz>, alsa-devel@lists.sourceforge.net
Subject: Re: Build-in mixer
Date: Wed, 08 Oct 2003 14:04:50 +0200 [thread overview]
Message-ID: <s5hsmm49bq5.wl@alsa2.suse.de> (raw)
In-Reply-To: <200310081124.h98BOGqq018813@oud>
At Wed, 08 Oct 2003 07:24:16 -0400,
Paul Davis wrote:
>
> >I don't know, if the term "mixer" is used correctly, because i am not
> >expert on it. I have in mind to use ALSA by more than one programs at
> >the same time (simultaneously), and ALSA itself should mix these audio
> >streams to one and play it via soundcard.
>
> just so you know, although this functionality is certain desired by
> many, its not the way that some users want things to work. as a
> result, ALSA makes this possible, but it doesn't do it by default. Put
> another way, it provides a mechanism to do this, but doesn't enforce
> it as a policy.
>
> >I tried dmix plug-in together with aplay -Dplug:dmix simultaneously from
> > two consoles and it works sufficiently (well, "underun!!! (at least
> >...ms long)" message was there but i don't know, if is is serious bug or
> >not). I thing that it should work transparently without special swithes
> >or settings separately for each application or its instance, but i don't
> >know if it is possible or not.
>
> the dmix plugin is indeed the way to do this. what you need to do (or
> perhaps ALSA needs to by default) is to set up your ~/.asoundrc so
> that the default device is a dmix configuration.
>
> all ALSA applications should accept options from the user specifying
> which PCM (or MIDI or ...) device they should open, and they fall back
> to "default" if none is specified. consequently, with this
> configuration setup, you'd get what you are hoping for, but other
> people could still use "hw:1" or specific named devices when they
> don't want dmix to get in the way (e.g. professional audio users).
>
> unfortunately, i don't know how to write an ~/.asoundrc file that
> would do that :( somebody will, though.
it's becoming an FAQ... :)
pcm.!default {
type plug
slave.pcm "dmix"
}
the point is '!' prefix, which means overriding the existing
definition.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-10-08 12:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 8:24 Build-in mixer Dan Tihelka
2003-10-08 11:24 ` Paul Davis
2003-10-08 12:04 ` Takashi Iwai [this message]
2003-10-10 8:41 ` Dan Tihelka
2003-10-11 15:33 ` Daniel Tihelka
2003-10-12 16:44 ` Frank Barknecht
2003-10-14 7:39 ` Dan Tihelka
2003-10-14 11:34 ` Paul Davis
2003-10-15 9:15 ` Dan Tihelka
2003-10-15 11:24 ` Paul Davis
2003-10-15 12:10 ` Dan Tihelka
2003-10-15 12:40 ` Paul Davis
2003-10-15 14:19 ` Takashi Iwai
2003-10-15 14:53 ` Paul Davis
2003-10-15 15:01 ` Takashi Iwai
2003-10-15 15:31 ` Takashi Iwai
2003-10-17 7:41 ` Jaroslav Kysela
2003-10-17 11:13 ` Takashi Iwai
2003-10-17 7:31 ` Jaroslav Kysela
2003-10-17 7:28 ` Jaroslav Kysela
2003-10-13 12:13 ` Clemens Ladisch
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=s5hsmm49bq5.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dtihelka@kky.zcu.cz \
--cc=paul@linuxaudiosystems.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