From: "Adam Tlałka" <atlka@pg.gda.pl>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Valdis.Kletnieks@vt.edu, 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: Wed, 12 Jul 2006 00:31:39 +0200 [thread overview]
Message-ID: <44B426CB.4010405@pg.gda.pl> (raw)
In-Reply-To: <1152637064.21909.61.camel@mindpipe>
Użytkownik Lee Revell napisał:
> 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.
Yes, that is true. It was just simple example how you can get simple
sound effects without many lines of code. In case of heavy load or too
many events in short period of time this method is not working correctly
but this is not the main functionality of a window manager program.
Anyway you can aggregate events if there are too many of them and play
only one sound or not play anything at all. For this kind of program
it is quite acceptable and not breaks main functionality.
> 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.
True - and that makes things more complicated. I don't know if it is
worth it just for bells and whistles. In other cases you do need to
program more sophisticated sound support and RT thread probably will be
your solution. Or some kind of sound server which holds your sound
samples so you can fire them at the proper time.
ALSA lib is a low level library. Sometimes we need more abstract
functions like load(s, "sound.wav) and then play(s) without bothering
about all these parameters settings. So maybe OpenAL is a some kind of a
solution but I don't know its current status.
Regards
--
Adam Tlałka mailto:atlka@pg.gda.pl ^v^ ^v^ ^v^
Computer Center, Gdańsk University of Technology, Poland
PGP public key: finger atlka@sunrise.pg.gda.pl
prev parent reply other threads:[~2006-07-11 22:32 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
2006-07-11 22:31 ` Adam Tlałka [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=44B426CB.4010405@pg.gda.pl \
--to=atlka@pg.gda.pl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.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