From: "Nick French" <nick@greensignal.com>
To: Paul Davis <pbd@op.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Multiple PCM files
Date: Tue, 30 Jul 2002 14:58:59 +0100 [thread overview]
Message-ID: <104d01c237d1$412cc1e0$360110ac@dillon> (raw)
New to this sound thing most of the stuff we have done is graphical what is
the formula for mixing n streams is it as simple as (stream 1 / number
streams) + ( stream 2 / number of streams ) ..... + (stream n / number of
streams ). What about different sample rates, stereo and mono. Any sample
code around?
Cheers
Nick
----- Original Message -----
From: "Paul Davis" <pbd@op.net>
To: "Nick French" <nick@greensignal.com>
Cc: <alsa-devel@lists.sourceforge.net>
Sent: Tuesday, July 30, 2002 2:18 PM
Subject: Re: [Alsa-devel] Multiple PCM files
> >So does JACKs allow two separate applications to stream PCM audio at the
> >same time to the same device and if so will it then overlay them? If it
will
> >why would two threads each registering with JACKs not work.
>
> it might, but it would be very inefficient. every JACK connection
> requires a new thread in the client, and implies an IPC per client per
> process() callback cycle.
>
> the code to mix down your own threads' output buffers is a few
> lines. why bother with anything else?
>
> --p
>
-------------------------------------------------------
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 reply other threads:[~2002-07-30 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 13:58 Nick French [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 20:58 Multiple PCM files Philipp Vollmer
2002-07-31 20:20 ` 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='104d01c237d1$412cc1e0$360110ac@dillon' \
--to=nick@greensignal.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pbd@op.net \
/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