From: Gregory Bonik <gregory@bonik.org>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Implementing full-duplex realtime sound processor
Date: Mon, 23 Aug 2010 23:14:43 +0200 [thread overview]
Message-ID: <1282598083.4691.26.camel@koffer> (raw)
In-Reply-To: <AANLkTimzWczB5XGN=16QaMDkd_mvW8bwK_14Bbpci+JL@mail.gmail.com>
On 23/08/2010 10:50 +0100, James Courtier-Dutton wrote:
> Why don't you want to use JACK. It is a perfect fit for what you are
> trying to do, and it solves a LOT of problems that you don't yet know
> you will run into.
Just because I don't want to force the users to use JACK, since it's not
so standard. I plan to add support for it later, but I want my program
still be usable without it. What are the problems you are talking about?
prev parent reply other threads:[~2010-08-23 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 16:40 Implementing full-duplex realtime sound processor Gregory Bonik
2010-08-23 9:50 ` James Courtier-Dutton
2010-08-23 21:14 ` Gregory Bonik [this message]
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=1282598083.4691.26.camel@koffer \
--to=gregory@bonik.org \
--cc=alsa-devel@alsa-project.org \
--cc=james.dutton@gmail.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;
as well as URLs for NNTP newsgroup(s).