Good news!
MAD now supports the MPEG 2 extension to Lower Sampling Frequencies (24, 22.05, and 16 kHz.)
In addition, the Layer III performance has improved yet again due to a new optimization that avoids the IMDCT calculation when all the inputs would be zero.
I'd appreciate any testing anyone is able to do with respect to MPEG 2 LSF; I have several Layer III streams I could verify but I don't have any Layer I or II streams handy.
The release:
ftp://ftp.mars.org/pub/mpeg/
Cheers, -rob
MAD is now in Debian. libmad0-dev is the package name. I only packaged the actual decoder lib, not the id3 or the audio work.
How do you want to handle shared libs? I can give you the info for making them on linux, but I do not know about other unix systems, other than they are all different. The debian package only has the static lib that you now provide.
MAD is now in Debian. libmad0-dev is the package name. I only packaged the actual decoder lib, not the id3 or the audio work.
How do you want to handle shared libs? I can give you the info for making them on linux, but I do not know about other unix systems, other than they are all different. The debian package only has the static lib that you now provide.
Sean,
MAD is now in Debian. libmad0-dev is the package name. I only packaged the actual decoder lib, not the id3 or the audio work.
Thanks. :-)
How do you want to handle shared libs? I can give you the info for making them on linux, but I do not know about other unix systems, other than they are all different. The debian package only has the static lib that you now provide.
Is there a convention or common practice with respect to this for Debian in general? Or do most packages normally provide a way to create shared libs?
-rob
Is there a convention or common practice with respect to this for Debian in general? Or do most packages normally provide a way to create shared libs?
in general libfoo.tar.gz becomes libfoo<soname> and libfoo<soname>-dev. The shared library goes in the libfoo package along with any user docs; the headers and .a go in the -dev package, along with any programmer docs. Occasionally a -doc package will be made if the documentation is copious.
Most lib packages provide shared libraries, it is the preferred form of use.
-
Rob Leslie -
Sean 'Shaleh' Perry