From: "Nick French" <nick@greensignal.com>
To: Philipp Vollmer <vollmer.philipp@t-online.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Multiple PCM files
Date: Wed, 31 Jul 2002 21:20:31 +0100 [thread overview]
Message-ID: <121a01c238cf$b88c66b0$360110ac@dillon> (raw)
In-Reply-To: 200207312258.48640.do1ypv@linux
Exactly. I would prefer the second as if I needed to add a third, 4th its
takes no effort and I don't reinvent the wheel as they say.
Does alsa support 2 or is this just JACK's.
The mathematics may be simple for 1 but why should it be done over and over
again. An API is meant to take away repetitive annoyances ;)
Cheers
Nick
----- Original Message -----
From: "Philipp Vollmer" <vollmer.philipp@t-online.de>
To: <nick@greensignal.com>
Cc: <alsa-devel@lists.sourceforge.net>
Sent: Wednesday, July 31, 2002 9:58 PM
Subject: Re: Multiple PCM files
Hello,
Maybe you're working at the same problem as me. At this
point of time.
There are two possibilities:
1. Open one device with one handler and mix the two files
with arimethic operations as they will be mixed by the sound
card although.
2. Open one devices but with two handlers in two threads
and write your pcm data to it.
regards
Philipp ( DO1YPV )
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
next prev parent reply other threads:[~2002-07-31 20:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 20:58 Multiple PCM files Philipp Vollmer
2002-07-31 20:20 ` Nick French [this message]
2002-07-31 22:18 ` Paul Davis
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 13:58 Nick French
2002-07-30 12:24 Nick French
2002-07-30 13:18 ` Paul Davis
2002-07-30 10:43 Nick French
2002-07-30 11:29 ` Paul Davis
2002-07-30 9:52 Nick French
2002-07-30 9:50 Nick French
2002-07-30 10:11 ` Paul Davis
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='121a01c238cf$b88c66b0$360110ac@dillon' \
--to=nick@greensignal.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=vollmer.philipp@t-online.de \
/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.