From: Jaroslav Kysela <perex@suse.cz>
To: Dave Andruczyk <djandruczyk@yahoo.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
ALSA user <alsa-user@alsa-project.org>
Subject: Re: asound.conf pcm.tee, anyone know how to use it
Date: Mon, 13 May 2002 09:57:06 +0200 (CEST) [thread overview]
Message-ID: <abnroh$o59$2@main.gmane.org> (raw)
In-Reply-To: <20020513004239.56478.qmail@web14108.mail.yahoo.com>
On Sun, 12 May 2002, Dave Andruczyk wrote:
> Please someone correct me if I am mistaken. Can the pcm.tee option in alsa.con
> (/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" ??
>
> My primary app (eXtace) needs this sort of functionality, The old ALSA 0.5.x
> called it loopback, can this do the same? Can anyone offer tips for someone
> who really doesn't understand the asound.conf syntax to possibly get it to
> work?
aplay -D tee:'plughw:0',a.raw ~/audio/audio_10.wav
All samples should go to 'a.raw' file, but as Paul mentioned, if you use a
pipe, the audio process can be blocked (possible underruns).
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
next prev parent reply other threads:[~2002-05-13 7:57 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 ` asound.conf pcm.tee, anyone know how to use it Paul Davis
2002-05-13 7:57 ` Jaroslav Kysela [this message]
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='abnroh$o59$2@main.gmane.org' \
--to=perex@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox