[iPAQ] madplay/mpg123

Nico
        I did a quick modification of madplay to format its output a la
mpg123 if it has been started up with a name of mpg123 (i.e. link mpg123 to
madplay), otherwise it just outputs things in madplay format. This way
gqmpeg (and any other GUI front end for mpg123 for that matter) can now use
madplay. These initial changes only output what madplay already output,
just in a different format. I did not try to have madplay generate new
output to match everything mpg123 outputs (Copyright yes/no, original
yes/no, CRC, etc), these less crucial fields are statically output for now.
gqmpeg now plays and displays mp3s properly on the iPAQ, but is using
madplay to INSTANTLY startup the songs, with MUCH better sound quality.
        I have put a tarball of madplay up at
ftp://handhelds.org/pub/apps/sound/, with madplay.c and a README.mpg123
being the only files that have changed, check it out and let me know what
you think.

Thanks

Tom

-----Original Message-----
From: Nicolas Pitre [mailto:nico@cam.org]
Sent: Monday, September 25, 2000 10:13 AM
To: Lawler, Tom
Cc: ipaq list; Robert Leslie
Subject: RE: [iPAQ] underwater audio

On Mon, 25 Sep 2000, Lawler, Tom wrote:

> Nicolas
> One reason mpg123 is popular is there are a number of GUI front-ends
> for it. I got your version of splay compiled and running on the iPAQ, but
> the only GUI front-end I have found for it is QT based, which, among other
> issues QT has, is HUGE. Is there a GUI front-end to madplay?

Not at the moment. However, I mentionned to Rob Leslie the idea of having
a mpg123 compatibility mode to madplay, sort of a madplay frontend that
implement mpg123's command line interface or whatever required by any GUI
on top of it. It shouldn't be too hard given the good separation provided
by madplay's decoding library. I'm just not in a position to commit time
into such development at the moment.

However, if there is any volunteer to do so, please identify yourself!

Nicolas
Received on Thu Oct 5 14:55:33 2000