public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Adam Tlałka" <atlka@pg.gda.pl>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	perex@suse.cz, alan@lxorguk.ukuu.org.uk
Subject: Re: [Alsa-devel] OSS driver removal, 2nd round (v2)
Date: Tue, 11 Jul 2006 12:57:43 -0400	[thread overview]
Message-ID: <1152637064.21909.61.camel@mindpipe> (raw)
In-Reply-To: <200607111430.k6BEUUus006736@turing-police.cc.vt.edu>

On Tue, 2006-07-11 at 10:30 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 11 Jul 2006 08:15:28 +0200, Adam =?ISO-8859-2?B?VGxhs2th?= said:
> > Sorry to say but it is just not that way. Window manager is for managing windows
> > and it shouldn't depend on any audio system. It should use an external app using exec call
> > to play sounds (aplay, sox, wavplay etc.) configured by some config option.
> 
> So what you're saying is that something like 'esd' *is* needed.  (It's
> certainly silly to keep doing fork/exec for every little sound sample when
> you can just leave the app running and hand it requests...)

That approach also won't be reliable as it ignores the realtime
constraint that is inherent in audio playback.  It will probably work on
a fast/lightly loaded machine but will glitch out under load.

It's how GDM plays startup/shutdown sounds and it sucks - on shutdown
the sound is choppy.  You either need a dedicated daemon running
SCHED_FIFO or an RT thread for reliable audio playback.

Lee


  reply	other threads:[~2006-07-11 16:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 23:17 OSS driver removal, 2nd round (v2) Adrian Bunk
2006-07-07 23:50 ` Andi Kleen
2006-07-08  0:00   ` Adrian Bunk
2006-07-08  1:30   ` Jeff Garzik
2006-07-09 15:18   ` [Alsa-devel] " Lee Revell
2006-07-09 16:08     ` Olivier Galibert
2006-07-10 11:28     ` Adam Tlałka
2006-07-10 13:18       ` James Courtier-Dutton
2006-07-10 13:57       ` Adrian Bunk
2006-07-10 22:48       ` Lee Revell
2006-07-10 23:38         ` Adam Tlałka
2006-07-10 23:51           ` Cloning sound output [was Re: [Alsa-devel] OSS driver removal, 2nd round (v2)] J.A. Magallón
2006-07-10 23:51           ` [Alsa-devel] OSS driver removal, 2nd round (v2) Lee Revell
2006-07-10 23:59           ` Olivier Galibert
2006-07-11  0:39             ` Lee Revell
2006-07-11  6:59               ` Adam Tlałka
2006-07-11  7:02                 ` Andi Kleen
2006-07-11  7:58                 ` Jaroslav Kysela
2006-07-11  9:08                   ` Adam Tlałka
2006-07-11  9:52                     ` Jaroslav Kysela
2006-07-11 11:18                       ` Diego Calleja
2006-07-11 11:29                       ` Adam Tlałka
2006-07-11 10:28                     ` Adrian Bunk
2006-07-11  2:09           ` Valdis.Kletnieks
2006-07-11  6:15             ` Adam Tlałka
2006-07-11 14:30               ` Valdis.Kletnieks
2006-07-11 16:57                 ` Lee Revell [this message]
2006-07-11 22:31                   ` Adam Tlałka

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=1152637064.21909.61.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=atlka@pg.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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