From: John Rigg <aldev@sound-man.co.uk>
To: Peter Dolding <oiaohm@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa-lib has anyone looked at taking it cross platform?
Date: Sat, 26 Jul 2008 22:24:00 +0100 [thread overview]
Message-ID: <20080726212400.GA2415@localhost> (raw)
In-Reply-To: <e7d8f83e0807260548j4892fb2cga6149a6d3c8e4f13@mail.gmail.com>
On Sat, Jul 26, 2008 at 10:48:14PM +1000, Peter Dolding wrote:
> Note its imposable to get nested sound server to work perfectly. But
> its more than possible to get a single sound server to do all the jobs
> of all the other sound servers so giving perfect API coverage.
Where does JACK fit into this? It's aimed at a completely different
set of users from the other sound servers for Linux.
The requirements for pro audio, eg. music recording, sound for film
etc. are totally different from those of the average desktop user.
A single sound server that tries to do everything for everybody
sounds to me like a potential nightmare of conflicting requirements.
John
next prev parent reply other threads:[~2008-07-26 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1217066401.19372.alsa-devel@alsa-project.org>
2008-07-26 12:48 ` Alsa-devel Digest, Vol 17, Issue 128 Peter Dolding
2008-07-26 21:24 ` John Rigg [this message]
2008-07-27 3:18 ` alsa-lib has anyone looked at taking it cross platform? Peter Dolding
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=20080726212400.GA2415@localhost \
--to=aldev@sound-man.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=oiaohm@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 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.