From: Nix <nix@esperi.org.uk>
To: ross@jose.lug.udel.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: software mixing in alsa
Date: Wed, 18 May 2005 14:50:24 +0100 [thread overview]
Message-ID: <87acms63tr.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20050518063014.GA7053@jose.lug.udel.edu> (ross@lug.udel.edu's message of "18 May 2005 07:32:44 +0100")
On 18 May 2005, ross@lug.udel.edu uttered the following:
> I use esd for all "consumer" level audio apps, and jackd for all
> professional audio apps. This is by far the simplest way to manage
> audio
In my experience, polypaudio replaces esd with something both simpler
and more powerful. (Oh, and without esd's *horrible* stutter,
interruption, mis-authentication, and code cleanliness problems.)
(For the professional stuff there is no replacement for JACK, I agree.)
--
`End users are just test loads for verifying that the system works, kind of
like resistors in an electrical circuit.' - Kaz Kylheku in c.o.l.d.s
next prev parent reply other threads:[~2005-05-18 14:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 9:56 software mixing in alsa Karel Kulhavy
2005-05-17 10:08 ` Jan Spitalnik
2005-05-17 14:13 ` Karel Kulhavy
2005-05-17 18:32 ` Lee Revell
2005-05-17 19:24 ` Karel Kulhavy
2005-05-17 19:32 ` Lee Revell
2005-05-17 20:27 ` Valdis.Kletnieks
2005-05-17 20:36 ` Lee Revell
2005-05-18 13:32 ` Karel Kulhavy
2005-05-18 13:53 ` Jaroslav Kysela
2005-05-18 17:47 ` Lee Revell
2005-05-18 6:30 ` ross
2005-05-18 8:42 ` Lee Revell
2005-05-18 13:21 ` Karel Kulhavy
2005-05-18 13:50 ` Nix [this message]
2005-05-18 13:48 ` Takashi Iwai
2005-05-18 14:38 ` Pierre Ossman
2005-05-18 18:25 ` Lee Revell
2005-05-19 15:10 ` Valdis.Kletnieks
2005-05-18 9:22 ` Pavel Machek
2005-05-17 19:28 ` Michal Schmidt
2005-05-17 21:04 ` Karel Kulhavy
2005-05-17 21:36 ` Lee Revell
2005-05-17 23:32 ` Lee Revell
2005-05-18 13:44 ` Takashi Iwai
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=87acms63tr.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ross@jose.lug.udel.edu \
/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.