25783 – madplay-0.15.0b is buggy/does not work with alsa

Bug 25783 - madplay-0.15.0b is buggy/does not work with alsa

Summary: madplay-0.15.0b is buggy/does not work with alsa

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Gentoo Sound Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-08-02 14:26 UTC by Eric Brown
Modified:	2003-08-18 04:02 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Eric Brown 2003-08-02 14:26:13 UTC

under portage there is: 
media-libs/libmad 0.15.0b (OK)
media-sound/mad
media-sound/madplay

mad = madplay i think.. but i've found that the latest build is broken. 
mad-0.14.2b-r2 works fine though.  the media-sound/madplay tree only has the
latest, and should not be used (i think).

to get madplay working (with alsa, as the latest one works if you have USE="-alsa"):
emerge libmad (0.15.0b)
emerge madplay (0.15.0b)  (can possibly be removed from these steps)
emerge /usr/portage/media-sound/mad/mad-0.14.2b-r2.ebuild 

tada.

Reproducible: Always
Steps to Reproduce:
1.USE="alsa" emerge mad
2.madplay *.mp3 (doesn't work at all, can't even pause)
3.

Actual Results:  
madplay wouldn't function, however if you use -o wave:- | aplay it would work..
something wierd is broken in the latest madplay build.  Also, if built with
USE="-alsa" it seemed to work fine.

use the older version anyway!

Expected Results:  
it should have played some sound :)

Portage 2.0.48-r7 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.20-gentoo-r5 i686 AMD Athlon(tm) Processor
GENTOO_MIRRORS="http://adelie.polymtl.ca/"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb
/opt/tomcat/conf /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 3dnow avi crypt encode foomaticdb jpeg libg++ mad mikmod mmx mpeg
ncurses nls pdflib quicktime spell truetype xml2 xv zlib gdbm berkdb slang
readline tetex svga java X sdl gpm tcpd pam libwww ssl perl python imlib
oggvorbis qt motif cdr aalib cjk -doc opengl -oss alsa gtk2 -gtk png gif tiff
-esd -kde -gnome mysql odbc -cups -arts tcltk flash -xmms -apm"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon -O3 -pipe"
CXXFLAGS="-march=athlon -O3 -pipe"
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox"

Comment 1 Eric Brown 2003-08-02 14:27:58 UTC

right.. latest version sucks.

Comment 2 Nick Hadaway 2003-08-16 03:13:39 UTC

hrm... i concur... madplay doesn't appear to work with alsa correctly.  Lucky for us there are about a million other choices for playing mp3s other than madplay.

Comment 3 Nick Hadaway 2003-08-18 04:02:40 UTC

I have tested this on a second system and madplay does not work properly still.  I get a note about a CRC error with the mp3s I play... if i do madplay -i file.mp3 to ignore the crc errors... madplay plays no sound out, have to ^C to stop it.

mpg123, xmms, and mpg321 all have no problems with the same file...

I have added madplay-0.15.0b-r1 to portage which removes the alsa code.  /etc/modules.d/alsa has oss-compatibility turned on by default so this should be fine for all users.

please test and let me know if you find any further problems.  I don't think 0.15.0b is that buggy. :)  The alsa feature is new as of 0.15.x series so it's most likely a work in progress.