From: David Ford <david+powerix@blue-labs.org>
To: John M Flinchbaugh <glynis@butterfly.hjsoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0: alsa, esd, mpg123
Date: Tue, 30 Dec 2003 12:01:25 -0500 [thread overview]
Message-ID: <3FF1AF65.4010107@blue-labs.org> (raw)
In-Reply-To: <20031230155358.GB23963@butterfly.hjsoft.com>
Unless esd has ever gotten fixed, esd doesn't handle errors or write()
return values.
Some sound cards can't handle the flood of data and only accept so many
bytes at a time. Esd does a write of 4K, only 2387 bytes (this is an
example) are actually written. Esd doesn't pay attention to this and
starts writing with the next 4K chunk. This leads to the skips.
On slow machines or slow kernels you don't notice this (as much), on
faster stuff, it's very apparent.
For what it's worth, there is hardly any error checking at all in esd.
David
John M Flinchbaugh wrote:
>on my debian (unstable) laptop newly running 2.6.0, i've noticed
>an irritating tendency for music to not pause, but instead to
>try to go too fast, skipping small parts of the song (fractions
>of a second). this results in music with regular beats sounding
>erratic.
>
>i'm using gqmpeg -> mpg123-esd -> esd -> oss -> alsa (maestro3).
>
>switching esd to use -tcp instead of -unix seems to alleviate
>the trouble a bit. ogg123 playing through esd doesn't seem to
>do it as much either.
>
>has anyone else noted this problem and tuned it away? thanks.
>
>
prev parent reply other threads:[~2003-12-30 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 15:53 2.6.0: alsa, esd, mpg123 John M Flinchbaugh
2003-12-30 16:25 ` Jaroslav Kysela
2003-12-31 19:27 ` John M Flinchbaugh
2003-12-30 17:01 ` David Ford [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=3FF1AF65.4010107@blue-labs.org \
--to=david+powerix@blue-labs.org \
--cc=glynis@butterfly.hjsoft.com \
--cc=linux-kernel@vger.kernel.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