From: Jaroslav Kysela <perex@suse.cz>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: ALSA vs. OSS
Date: Mon, 19 Jan 2004 20:42:55 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0401192036070.3707@pnote.perex-int.cz> (raw)
In-Reply-To: <1074532714.16759.4.camel@midux>
On Mon, 19 Jan 2004, Markus Hästbacka wrote:
> Hello list,
> I wonder what's the difference with ALSA and OSS. I have tried both,
> someone may say that ALSA is much better than OSS, but with my
> experience with ALSA I wouldn't say that, I would probably say it should
> be removed from the kernel totally.
It seems that you don't understand our goals. Please, look to our web
pages - http://www.alsa-project.org. If you use audio devices only for
consumer use, you probably don't notice anything special.
> So, what are the reasons for ALSA to become "default" in 2.6?
> I know it gives somekind of nice features, but ALSA didn't let me to
> open two sound sources (like XMMS and Quake3) at the same time, so I
> guess it is not really done yet, or is it?
We don't do this in kernel. We implemented the direct stream mixing in our
library (userspace). If your applications already uses ALSA APIs or if you
redirect the OSS ioctls to ALSA library (our aoss library), you can enjoy
multiple sounds.
Of course, using hardware which can do the hardware mixing is still
better. It's the same difference like between sw 3D rendering and hw 3D
rendering.
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
next prev parent reply other threads:[~2004-01-19 19:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 17:18 Markus Hästbacka
2004-01-19 17:48 ` Steve Youngs
2004-01-19 18:21 ` Travis Morgan
2004-01-20 8:58 ` Gábor Lénárt
2004-01-20 9:46 ` Heinz Ulrich Stille
2004-01-20 13:18 ` Mark Borgerding
2004-01-20 14:03 ` Markus Hästbacka
2004-01-20 14:07 ` Takashi Iwai
2004-01-20 14:17 ` Markus Hästbacka
2004-01-20 14:28 ` Takashi Iwai
2004-01-20 14:37 ` Markus Hästbacka
2004-01-20 14:41 ` Takashi Iwai
2004-02-25 22:21 ` Markus Hästbacka
[not found] ` <20040120170658.GB23351@widomaker.com>
2004-01-20 17:35 ` Takashi Iwai
2004-01-20 14:08 ` Heinz Ulrich Stille
2004-01-20 15:13 ` Alistair John Strachan
2004-01-20 15:19 ` Jaroslav Kysela
2004-01-22 23:53 ` Zephaniah E. Hull
2004-01-23 8:31 ` Jaroslav Kysela
2004-01-20 19:00 ` Eric Sandall
2004-01-21 11:03 ` Dale Weber
2004-01-21 18:06 ` Mike Fedyk
2004-01-24 8:21 ` Travis Morgan
2004-01-20 19:24 ` Brian McGroarty
2004-01-20 19:46 ` Måns Rullgård
2004-01-19 18:08 ` Raphaël RIGO
2004-01-19 19:42 ` Jaroslav Kysela [this message]
2004-01-20 14:24 ` Olaf Dabrunz
2004-01-20 14:44 ` Thomas Dodd
[not found] ` <Pine.LNX.4.58.0401201524230.2010@pnote.perex-int.cz>
2004-01-20 14:48 ` Olaf Dabrunz
2004-01-20 15:06 ` Takashi Iwai
[not found] <20040119174543.59620.qmail@web40610.mail.yahoo.com>
2004-01-19 18:06 ` Markus Hästbacka
2004-01-21 2:40 Jonathan Boler
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=Pine.LNX.4.58.0401192036070.3707@pnote.perex-int.cz \
--to=perex@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.org \
/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
all inboxes | Powered by JetHome®