From: Takashi Iwai <tiwai@suse.de>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: Christian Axelsson <smiler@lanil.mine.nu>,
Lukas Kolbe <lucky@knup.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1-mm2 music skips
Date: Mon, 21 Jul 2003 16:21:50 +0200 [thread overview]
Message-ID: <s5h65lwj6yp.wl@alsa2.suse.de> (raw)
In-Reply-To: <3F1B4027.2010301@wmich.edu>
At Sun, 20 Jul 2003 21:21:43 -0400,
Ed Sweetman wrote:
>
> Christian Axelsson wrote:
> > On Sun, 2003-07-20 at 22:34, Lukas Kolbe wrote:
> >
> > Please read the O*int threads.
> > It's probably Con's new scheduler that is causing these problems.
> > If you are using alsa, try the OSS emulation as it seems to help abit.
> >
>
> I've been using the 2.5 kernel for a long time now and the 2.4 kernel
> since it was just turned into 2.3. There have been these "problems"
> since 2.3, this is not something new caused by any new schedulers. The
> schedulers can cause problems, no doubt, but they also make userspace
> programming issues apparent. The fact that going to oss emu only proves
> that this is mostly a userspace problem. ALSA drivers have to be coded
> with much more attention to latency because it's very specific about
> being run on time. You can only send it a small amount of data every
> write you make to the soundcard.
well, just a small correction: it's ALSA output plugin of xmms, not
ALSA drivers. it uses the hardware buffer directly (or mmapped) while
xmms OSS output plugin has much larger internal buffers.
Takashi
prev parent reply other threads:[~2003-07-21 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 20:34 2.6.0-test1-mm2 music skips Lukas Kolbe
2003-07-20 21:12 ` Ed Sweetman
2003-07-20 21:56 ` Lukas Kolbe
2003-07-20 23:35 ` Antonio Vargas
2003-07-20 23:47 ` Christian Axelsson
2003-07-21 1:21 ` Ed Sweetman
2003-07-21 14:21 ` Takashi Iwai [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=s5h65lwj6yp.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lucky@knup.de \
--cc=smiler@lanil.mine.nu \
/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;
as well as URLs for NNTP newsgroup(s).