From: Takashi Iwai <tiwai@suse.de>
To: David Lloyd <dmlloyd@tds.net>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
ALSA Mailing List <alsa-devel@lists.sourceforge.net>
Subject: Re: DMIX and capture stream
Date: Mon, 05 Jan 2004 17:42:07 +0100 [thread overview]
Message-ID: <s5hbrpi2vq8.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0401051020560.8705@tomservo.workpc.tds.net>
At Mon, 5 Jan 2004 10:29:01 -0600 (CST),
David Lloyd wrote:
>
> On Sun, 4 Jan 2004, Paul Davis wrote:
>
> > >I'm working on changing DMIX to allow clients to open the capture stream.
> >
> > i don't get it. dmix is for playback, not capture. what would be the
> > semantics of this?
>
> That is exactly the problem! DMIX is for playback. DSNOOP is for
> capture. Where is the module that is for both? Why, oh why, did they not
> simply make ONE MODULE in the first place??
patch welcome ;)
well, more practical answer is that capturing the playback would need
copy of the playback data to the capture buffer. meanwhile, the
implementation of dmix and dsnoop is basically only the multiplex
access of a single hardware buffer. it's not "copying" of data.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2004-01-05 16:42 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 20:29 DMIX and capture stream David Lloyd
2004-01-04 5:07 ` Paul Davis
2004-01-04 12:12 ` Joern Nettingsmeier
2004-01-04 13:52 ` Florian Schmidt
2004-01-05 0:02 ` David Lloyd
2004-01-05 0:15 ` Florian Schmidt
2004-01-05 6:00 ` Patrick Shirkey
2004-01-05 10:18 ` HDSP as normal user Patrick Shirkey
2004-01-05 14:02 ` Paul Davis
2004-01-05 14:22 ` Takashi Iwai
2004-01-05 14:48 ` Patrick Shirkey
2004-01-05 16:13 ` DMIX and capture stream David Lloyd
2004-01-05 16:21 ` Jaroslav Kysela
2004-01-05 16:29 ` David Lloyd
2004-01-05 16:28 ` Jaroslav Kysela
2004-01-05 16:43 ` Takashi Iwai
2004-01-05 17:27 ` David Lloyd
2004-01-05 17:28 ` Florian Schmidt
2004-01-05 16:42 ` Takashi Iwai [this message]
2004-01-05 17:20 ` David Lloyd
2004-01-05 17:41 ` Paul Davis
2004-01-05 17:45 ` David Lloyd
2004-01-05 18:59 ` Paul Davis
2004-01-05 18:12 ` Takashi Iwai
2004-01-06 17:05 ` David Lloyd
2004-01-06 21:38 ` Florian Schmidt
2004-01-07 11:01 ` Takashi Iwai
2004-01-07 12:05 ` Florian Schmidt
2004-01-07 13:06 ` Florian Schmidt
2004-01-07 13:49 ` Takashi Iwai
2004-01-07 12:45 ` Abramo Bagnara
2004-01-07 13:45 ` Takashi Iwai
2004-01-07 14:39 ` Abramo Bagnara
2004-01-07 15:02 ` Takashi Iwai
2004-01-07 15:15 ` Abramo Bagnara
2004-01-07 15:30 ` Takashi Iwai
2004-01-07 15:47 ` Abramo Bagnara
2004-01-07 16:12 ` Takashi Iwai
2004-01-07 16:58 ` Abramo Bagnara
2004-01-07 17:22 ` Takashi Iwai
2004-01-08 8:33 ` Jaroslav Kysela
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=s5hbrpi2vq8.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dmlloyd@tds.net \
--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 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.