public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Marcin Dalecki <martin@dalecki.de>
Cc: Takashi Iwai <tiwai@suse.de>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Mac mini sound woes
Date: Tue, 29 Mar 2005 23:14:37 -0500	[thread overview]
Message-ID: <1112156077.5598.10.camel@mindpipe> (raw)
In-Reply-To: <0683ecb1e5fb577a703689d1962ad113@dalecki.de>

On Wed, 2005-03-30 at 03:45 +0200, Marcin Dalecki wrote:
> > I think your misunderstanding is that you beliieve user-space can't do
> > RT.  It's wrong.  See JACK (jackit.sf.net), for example.
> 
> I know JACK in and out. It doesn't provide what you claim.
> 

This was just an example, to prove the point that user space can do RT
just fine.  JACK can do low latency sample accurate audio, and mixing
and volume control are fairly trivial compared to what some JACK clients
do.  If it works well enough for professional hard disk recording
systems, then it can certainly handle system sounds and playing movies
and MP3s.

And as a matter of fact you can implement all the audio needs of a
desktop system with JACK, this is what Linspire is doing for the next
release, even though it wasn't designed for this.  The system mixer is
just a JACK mixing client and each app opens ports for I/O, and only
JACK talks to the hardware (through ALSA).

The fact that OSX and Windows do this in the kernel is not a good
argument, those kernels are bloated.  Windows drivers also do things
like AC3 decoding in the kernel.  And the OSX kernel uses 16K stacks.

If audio does not work as well OOTB as on those other OSes, it's an
indication of their relative maturity vs JACK/ALSA, not an inherently
superior design.  Most audio people consider JACK + ALSA a better design
than anything in the proprietary world (CoreAudio, ASIO).

Lee




  parent reply	other threads:[~2005-03-30  4:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 23:42 Mac mini sound woes Benjamin Herrenschmidt
2005-03-28  1:42 ` Andrea Arcangeli
2005-03-28  2:34   ` Benjamin Herrenschmidt
2005-03-29  3:36 ` Lee Revell
2005-03-29  3:41   ` Benjamin Herrenschmidt
2005-03-29  7:47   ` Marcin Dalecki
2005-03-29  8:18     ` Benjamin Herrenschmidt
2005-03-29  9:22       ` Marcin Dalecki
2005-03-29 10:22         ` Takashi Iwai
2005-03-30  1:45           ` Marcin Dalecki
2005-03-30  2:08             ` Lee Revell
2005-03-30  4:14             ` Lee Revell [this message]
2005-03-30  5:15             ` Steven Rostedt
2005-03-29 22:13         ` Lee Revell
2005-03-29 23:25           ` Chris Friesen
2005-03-29 23:39             ` Benjamin Herrenschmidt
2005-03-30  1:48               ` Marcin Dalecki
2005-03-30  5:42                 ` Lee Revell
2005-03-30  1:45           ` Marcin Dalecki
2005-03-29 10:02   ` Takashi Iwai
2005-03-29 11:04     ` Benjamin Herrenschmidt
2005-03-29 12:12       ` Takashi Iwai
2005-03-29 19:05       ` Lee Revell
2005-03-29 19:31         ` Takashi Iwai
2005-03-29 20:11           ` Lee Revell
2005-03-29 22:03           ` Benjamin Herrenschmidt

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=1112156077.5598.10.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox