[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#613806: ITP: mplayer2 -- next generation movie player for Unix-like systems



Peter Samuelson <peter <at> p12n.org> writes:
> > >   Description     : next generation movie player for Unix-like systems
> > > 
> > >    MPlayer plays most MPEG, VOB, AVI, Ogg/OGM, VIVO, ASF/WMA/WMV,
> > >    QT/MOV/MP4, FLI, RM, NuppelVideo, yuv4mpeg, FILM, RoQ, PVA files,
> > >    supported by many native, XAnim, RealPlayer, and Win32 DLL codecs. It
> > >    can also play VideoCD, SVCD, DVD, 3ivx, RealMedia, and DivX movies.
> > > 
> > >    Another big feature of MPlayer is the wide range of supported output
> > >    drivers. It works with X11, Xv, DGA, OpenGL, SVGAlib, fbdev, DirectFB,
> > 
> > > The text above is copied from the existing mplayer package. It is
> > 
> > The long description really needs a rewrite.
> 
> Maybe ... but mentioning all those file formats _is_ pretty useful for
> 'apt-cache search' purposes.  I know we're all supposed to use tags for
> such things now, but I find 'apt-cache search' a lot easier than
> figuring out what tag I should be looking for.

That file format list is missing at least one of the major container formats
(Matroska). Some of the listed ones are very obscure; I think mentioning ability
to play back various audio-specific formats (none of which are listed now) would
be at least as important. The rest of the description is worse. The following
codec section is meaningless and misleading (most codecs now come from
libavcodec; I think about nobody uses XAnim for example).

More than half the lines in the description are about video output drivers, and
mostly list completely obscure features that very few will care about. The
drivers you may reasonably want to use on Linux are VDPAU (missing from the
description), OpenGL and XVideo. Plain X11 can be a fallback if your system
doesn't support any proper video output method. The rest are mostly special
cases and/or obscure unmaintained crap which doesn't belong in the package
description.


Reply to: