From: Per Wigren <wigren@home.se>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] alsa support removed from current KDE
Date: Mon, 17 Jun 2002 21:20:27 +0200 [thread overview]
Message-ID: <200206172120.27295.wigren@home.se> (raw)
In-Reply-To: <200206170111.47964.verwilst@gentoo.org>
Maybe because ALSA has a superior API, support for more soundcards, uses less
resources, is going to be the default soundsystem in Linux 2.6?
ALSA itself is not buggy, it's some of the apps' ALSA-"support" that is
buggy...
Try to access the emu10k1 sequencer with the standard OSS-modules..
Total kernel freeze! :P At least with the lowlatency and preemptive patches
installed.. (I haven't tested without them)
// Wigren
Monday 17 June 2002 01.11 skrev Bart Verwilst:
> On Monday 17 June 2002 01:00, John A. Ouzts wrote:
> || I believe there will be some pent up demand for a HOWTO on getting sound
> || to work using KDE 3.0.1. and alsa 0.9, when a fix comes and alsa support
> || goes back into KDE. I suspect virtually all KDE users will be in need of
> || specific instructions for getting sound back.
>
> For getting sound back??
> I never used alsa in my life, and still i've always enjoyed sound on my KDE
> systems, without any hassle whatsoever... I can't understand why anybody
> would want to use something as (apparently) bugridden and hard to setup as
> alsa, when he can just compile his sounddrivers in the kernel, and let arts
> do all the work...
>
> just my 2 cents
next prev parent reply other threads:[~2002-06-17 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 23:00 [gentoo-dev] alsa support removed from current KDE John A. Ouzts
2002-06-16 23:11 ` Bart Verwilst
2002-06-17 19:20 ` Per Wigren [this message]
2002-06-20 23:26 ` Gioele Barabucci
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=200206172120.27295.wigren@home.se \
--to=wigren@home.se \
--cc=gentoo-dev@gentoo.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