Bug 6775 - mpg123 with esd makes an mp3 sound scratchy
mpg123 with esd makes an mp3 sound scratchy
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: esound (Show other bugs)
6.1
All Linux
low Severity low
: ---
: ---
Assigned To: Michael Fulbright
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-06 07:16 EST by egalanos.
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-12-03 14:39:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description egalanos. 1999-11-06 07:16:08 EST
A very high priority bug :)

mpg123r as shipped with RH6.1 makes one particular mp3 I
have sound scratchy. What should have been an sinusoidal
base sound turns into a static scratch sound. I downloaded
mpg123r and compiled it. It does not show this problem when
compiled as normal (ie using /dev/dsp directly). When
compiled against esd (after patch to audio_esd.c to make it
compile ie esdserver -> NULL), it then makes the mp3 sound
bad. mp3 is a standard 44kHz MPEG1 layer 3, 128kbps joint
stereo file.
Comment 1 Bill Nottingham 1999-11-22 11:33:59 EST
Can you post a sample mp3 that shows this?
Comment 2 egalanos. 1999-11-22 19:41:59 EST
Sample at

ftp://ftp.cse.unsw.edu.au/pub/users/egalanos/test.mp3
Comment 3 Mario Lorenz 1999-11-23 15:03:59 EST
This .mp3 is not 44khz, its 48khz. Which kinda explains whats happening. ESD's
mixing routines dont handle anything != 44khz very well. This could be
considered an esd bug/unimplemented feature. Either esd needs to be fixed or
replaced by something else (alsa should become usable soon, and even then, nas
was the older standard for doing network audio / mixing)
Comment 4 Michael Fulbright 1999-12-03 14:39:59 EST
There are community efforts to replace esd in progress, but this is not
something we can fix in the short term.

Note You need to log in before you can comment on or make changes to this bug.