Slashdot Mirror


MPlayer 0.90 released; MPlayer Maintainer Leaves

Viqsi writes "459 days after the previous stable release, the MPlayer folks have finally released stable version 0.90. With this done, A'rpi (th head maintainer) is leaving the project, citing too-much-free-time-forever-lost issues, and the team is looking closely at revising the way the project is managed as a result. Here's hoping some improvements come out of this."

13 of 334 comments (clear)

  1. well by daserver · · Score: 4, Informative

    Well Arpi is still there on the mailinglist doing stuff, he's just not the maintainer any longer.

  2. Re:THANKS ARPI! by den_erpel · · Score: 4, Informative

    Next to this obvious cheering, it is a fact that mplayer is the most versatile player around that I can think of. I've seen lots of cases that mplayer is capable of player files with odd framerates (audio and video, mainly produced by a bad configured digital camera) while other (includeing M$ mplayer) players choked on it.

    Since the license change, I've seen that (that allowed binary packaging) it is gradualy pushing other players to the background, exaclty due to it's versatility (aviplayer, xine, vlc, ...)

    The documentation seems to be somewhat lacking and for some things I (still) use IMHO better tools:

    video recording: nvrec, AFAIK mplayer does not support V4L2
    encoding: transcode, mainly because transcode seems to have a much better doc and logical buildup of the options to transcode and large modularity (for filters). I use mencoder sometimes when transcode has problems with particular file (or used to)

    One thing which no player seems to pull of correctly, is to play files with awfully synced audio, video...

    --
    Genius doesn't work on an assembly line basis. You can't simply say, "Today I will be brilliant."
  3. Embedded Mplayer by mrsev · · Score: 5, Informative

    Not many know this but texstar has a awesome package for embedding Mplayer into Konqueror. This is just awesome.

    Big thanks to the developers., for this one.

    1. Re:Embedded Mplayer by The+J+Kid · · Score: 3, Informative

      There is also an embedded Gnome 2 Mplayer called: Lumiere.

      It's just started, but already usable and quite nice. Very promissing.

      --
      Moderation: +4. Modded 70% Funny and 30% Overrated. 100% Saturated.
    2. Re:Embedded Mplayer by the_real_tigga · · Score: 4, Informative

      there is a package called mplayerplug-in which provides a plugin for all netscape-compatible browsers (including opera).

      --
      my .sig is better than yours.
  4. Re:Congrats to the MPlayer team! by Longinus · · Score: 4, Informative

    MPlayer ability to play hacked codecs is indeed a nice feature, but there's so much more the love about it, especially in the realms of performance (extremely low CPU usage), interface (sweet, sweet, command line, anti-aliased subs and osd), and flexablity (lots of other programs use mplayer, like MythTV and the mozilla-mplayer plugin that allows Linux users to watch movies in their browser). MPlayer manages to do a crap load of things without being bloated or slow.

  5. will it lose the race against xine? by Pivot · · Score: 5, Informative
    From his second posting;
    > IMHO mplayer is good enough now that it won't lost in /dev/null if i leave.
    > > Probably not, but will it lose the race against xine?

    imho we lose it already. see xine, its popularity started to grow since a month and keeps growing. while we spend our expensive time by rev. engineering codecs, optimizing code, writing demuxers, they improve the gui. then they 'steal' the others and win. we have no chance against xine... Ah, stability. Yes, in old days mplayer was rock solid while xine crashed at every second click. It has been changed: mplayer is now everything but stable (thanks to that many hacks and 10l bugs), while xine improved stability a lot...

    1. Re:will it lose the race against xine? by rjw57 · · Score: 3, Informative

      And it was the xine guys (erm... OK hands up, me) who first separated the DVD nav stuff from Ogle sufficiently to be used in other projects (including, now, mplayer).

      --
      Rich
  6. Re:Windows port? by Xugumad · · Score: 3, Informative

    According to the FAQ you can compile it on Windows using Cygwin. On the subject of ports, Mac OS X users may be interested in MPlayer OS X.

  7. Re:yes, exactly because of that by Longinus · · Score: 3, Informative

    "I merely pointed out the hypocricy of calling MPlayer an open source revolution that stomps closed source into oblivion when its core performance is enabled by closed source (unlicensed) binaries?" What bullshit. MPlayer's "core performance" remains the same whether or not it was compiled with support for Win32 codecs. I do use the right tool for the right job, and that tool is MPlayer. The ability to play Win32 codecs is merely a bonus to me, and help in a pinch whenever I have the misfortune of needing to watch a Real video clip. 99% of my videos are encoded in open codecs like XviD anyway. The point is that MPlayer rocks regardless of what codec its playing, and to say that its only value is the ability to play win32 codecs is to be completely ignorant to what an amazing piece of technology it is in it's own right.

  8. Re:Windows port? by bodin · · Score: 4, Informative

    If you need a really good mediaplayer on windows, mac or other platforms, please check out VLC http://www.videolan.org/vlc/ which is a VERY good alternative to both XINE and MPlayer. It plays video directly out of bin/cue-files and does all sorts of good stuff.

    Free of course. Sister project is free videostreaming!

  9. Re:Idea for a new media player by rjw57 · · Score: 3, Informative

    The GStreamer project aimed to do this and xine already has support for demuxer, codec, output, etc plugins (indeed all the DVD features used by xine used to exist as a totally separate project at dvd.sf.net).

    --
    Rich
  10. Oh come on... by Replicant7 · · Score: 4, Informative

    This has changed dramatically. No, seriously you are talking about the past. Which parts of the documentation do you find lacking? I'm the documentation maintainer and I will try to address the points you may make...