From: Paul Davis <pbd@op.net>
To: Dave Andruczyk <djandruczyk@yahoo.com>
Cc: alsa-devel@alsa-project.org, alsa-user@alsa-project.org
Subject: Re: asound.conf pcm.tee, anyone know how to use it
Date: Sun, 12 May 2002 22:33:04 -0400 [thread overview]
Message-ID: <200205130232.EAA31315@alsa.alsa-project.org> (raw)
In-Reply-To: Your message of "Sun, 12 May 2002 17:42:39 PDT." <20020513004239.56478.qmail@web14108.mail.yahoo.com>
>Please someone correct me if I am mistaken. Can the pcm.tee option in alsa.co
>n
>(/usr/share/alsa/alsa.conf) be setup so that the output of a program that uses
>alsa natively be monitored by connecting to this "tee" ??
well, the "tee" type allows redirection but its only sane to do it to
a file inode that allows (almost) endless non-blocking read/write. there are
almost no such devices in POSIX unless its a regular file. so you
can't really use it for loopback. its intended for instances where you
want the output to go to an audio interface *and* a file.
there is a way to do "loopback" in ALSA these days, but "tee" is not
it. someone will fill in the blanks (or better yet, write/complete a
HOWTO).
--p
<obJack>
of course, JACK can do loopback, multiplexing, app-2-app and many
other forms of data routing without any effort on the part of your
application ...
</obJack>
:)
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
next parent reply other threads:[~2002-05-13 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020513004239.56478.qmail@web14108.mail.yahoo.com>
2002-05-13 2:33 ` Paul Davis [this message]
2002-05-13 7:57 ` asound.conf pcm.tee, anyone know how to use it Jaroslav Kysela
2002-05-13 0:42 Dave Andruczyk
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=200205130232.EAA31315@alsa.alsa-project.org \
--to=pbd@op.net \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@alsa-project.org \
--cc=djandruczyk@yahoo.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.