Slashdot Mirror


Mplayer Revisited

Joe Barr writes "It's been two years since I first wrote about Mplayer. Maybe the fury of the developers/community reaction to the fact that I dared to criticize them for their treatment of users kept me away. Whatever. Now Mplayer has a pre1 version of release 1.0 out there and it's time for another look." Newsforge and Slashdot are both part of OSDN.

63 of 353 comments (clear)

  1. Great for OSX by truffle · · Score: 4, Informative

    The OSX build of MPlayer is very useful, it's the best DivX player for OSX! Of course it plays other formats as well. Thanks MPlayer team!

    --

    ---
    I support spreading santorum
    1. Re:Great for OSX by Fred+IV · · Score: 5, Informative

      VLC is pretty good too, better for me because my mac is an older machine and the OS X version of mplayer doesn't always work well with my hardware (iBook 500).

    2. Re:Great for OSX by Anonymous Coward · · Score: 2, Informative

      Strange, that it does not work on your iBook. I'm using mplayer on 466 MHz iBook and it works better than VLC - doesn't lose sync and is way faster.

    3. Re:Great for OSX by a.deity · · Score: 2, Informative

      I've got the same iBook, and VLC works very well, with the exception of HQ DivX encodes. MPlayer OS X is a lifesaver then, as it seems to be a bit smoother. MPlayer's not full-time for me, though, since the lipsync sometimes falls out, which VLC avoids quite well. Is there an audio-sync function in MPlayer that I don't know about? Turning on the slow-media cache helps, but isn't a sure thing.

      --
      Option-Shift-K.
  2. What about other software? by Kandel · · Score: 3, Flamebait

    Sure, it's great to have a v1.0 release of MPlayer, but on the other end of the stick, Xine is not far off from hitting the 1.0 status as well. Won't this seem daunting to the end user (labelled automatically as stupid), having two different applications, with individual libraries, for doing the exact same thing.
    Perhaps some collaboration between MPlayer and Xine should occur.
    However, the fact I find most surprising, is that Microsoft hasn't stepped in argueing that the software cannot be called, "MPlayer". Perhaps it's 1.0 status may spur things on...
    Let's hope the MPlayer guys don't ship their next release as version 9.0 :P

    1. Re:What about other software? by IAR80 · · Score: 2, Insightful

      Actually I really like diversity so having both xine and mplayer as separate projects is a very good thing.

      --
      http://ebgp.net/ccc/
    2. Re:What about other software? by mopslik · · Score: 2, Informative

      the fact I find most surprising, is that Microsoft hasn't stepped in argueing that the software cannot be called, "MPlayer"

      Microsoft's product is called "Media Player". MPLAYER.EXE is merely an antiquated, conventional, DOS-format file name.

    3. Re:What about other software? by sewagemaster · · Score: 4, Funny

      Let's hope the MPlayer guys don't ship their next release as version 9.0 :P

      actually, it wont. thanks for the clue michael has told us. this version v1.0 is named mplayer revisited. when the next verion comes out v2.0, it'll be called mplayer reloaded. within the same year, v3.0 will be out and named mplayer revolutions. in between each released version, we have v2.5 mplayer reloaded extended DVD edition, and v3.5 being reloaded extended DVD edition.

      Dont forget animplayer, the game enter mplayer, the comic book to be released, and the new roleplayer game to be released!

    4. Re:What about other software? by tomknight · · Score: 2, Informative
      A comment in the article mentions:
      deb http://marillat.free.fr/ unstable main

      Tom.

      --
      Oh arse
    5. Re:What about other software? by FrostedWheat · · Score: 2

      aving two different applications, with individual libraries, for doing the exact same thing

      Gasp! There are two media players! Shocking! Seriously tho, what's wrong with that? It gives people choice!!

      If there ends up only being one way or program to do anything, then things start to resemble the way Microsoft do things.

    6. Re:What about other software? by ichimunki · · Score: 2, Insightful

      You're kidding, right? The only people who should be making any effort to make the end user experience "care free" in the way you describe are the commercial distros. Nobody makes this kind bullshit argument in any other field of endeavor. Do you ever see suggestions that Target should only carry one brand of toothpaste because consumers would find it too difficult to choose between Colgate and Crest? Hell, there's even a whole category of product devoted to people who can't make up their minds: the Variety Pack!

      --
      I do not have a signature
    7. Re:What about other software? by Qzukk · · Score: 4, Insightful

      Won't this seem daunting to the end user ... having two different applications, with individual libraries, for doing the exact same thing.

      So, you think we should all just go with one software project and kill the other? Which should we kill? Did you know that Xine did the GUI thing first? Mplayer has been the leader in figuring out how to play new formats (especially Quicktime codecs)

      So if we had killed xine, would mplayer have developed a gui without competition? If we had killed mplayer, would we still be griping about not being able to watch Sorenson encoded movie trailers?

      What future benefits will this competition bring?

      To the users, I say: Try them both and stick to the one you like. This doesn't require genius or even much intelligence. If you can't get mplayer working, then xine. If you'd rather not deal with a GUI, then mplayer. (personally, I hate hunting through a list of files for the video I want, when I could just run mplayer -fs filename.avi and get full screen goodness straight from the start without having to move widgets out of the way or get them behind the video window.)

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    8. Re:What about other software? by The+Grey+Mouser · · Score: 2, Insightful


      In other words, spread all resources as thin as possible instead of making one big kick-ass killer app. All in the name of idealist "diversity."


      You assume that adding more people to this project will automatically make it a bigger, better "killer app". That is not at all obvious, given what we know about human nature.


      All that matters is net output. That's it.


      All that matters to *you* is net output. You can hardly fault the developers for not seeing it that way. They are happy to contribute their efforts to improving media playback on linux, and have made enormous progress in that regard. Beyond that, they really don't owe anything to you or the rest of the community. But you speak as though they were salaried employees!

      Cheers,

      Mouser

    9. Re:What about other software? by Dave_bsr · · Score: 3, Insightful

      Hey, it's the overly critical guy again. I really think you might just be a great, great troll. Either that or just really frustrating. Anyways...response:

      For one, groups don't always just get along...I really don't think the xine guys and the mplayer guys would like to just drop everything and work together - both sides have thrown a couple of potshots too many - they don't like each other.

      Secondly - competition increases output. It's one of those crazy things about life that two competing groups seem to get farther than only one alone.

      Third - more people on a project does not (neccesarily) more code make - adding more developers means you have to merge maintainers, and "people in charge" - etc - it has to be very well organized to get O(n) increase in production... You can't just throw people from well-defined, properly working groups together...it doesn't work! Good people can be left out (and unused)...

      Fifth - mplayer and xine do share some libs. I'm almost positive that xine is using some of mplayer's win32 code, but i'm not sure - but the logical thing is that they are both open, and why wouldn't one project "borrow" code from another, if it was great. Emulation is the sincerest form of praise - I think that's how that goes.

      Mplayer is a great project, xine - last I checked - was...decent. I think seperately you get _more_ output - and thus having two seperate groups is better for you. *shrug*.

      --


      Who is this Anonymous Coward character, how does he post so much, and why is he always such a whore?
    10. Re:What about other software? by FrostedWheat · · Score: 2, Informative

      Two applications that do the exact same thing. Most sane people would see that as pointless and redundant. It's a waste of resources.

      Never put all your eggs in one basket.

    11. Re:What about other software? by fucksl4shd0t · · Score: 2, Interesting

      There is a world of difference between toothpastes competing in a store and the NECESSARY unification of design required for Linux to ever successfully penetrate the desktop market.

      All right, OCG, I'll bite this time. :)

      We're not dealing with commercial companies competing with each other, but that doesn't mean we're not dealing with groups competing with each other. MPlayer and Xine are in some pretty heated competition, last I heard. Either one of these projects would love to get a one-up over the other. Also, both projects just LOVE to do something that hasn't been done before, and they LOVE to make it work reliably. MPLayer, to my knowledge, is the first Linux movie player to use native win32 codecs to play certain formats, without WINE.

      That said, even in the commercial sector, there has always been lots of choices and fighting between different application developers. From the early days when we had more word processors available than we had kilobytes of ram in our computers, that hasn't changed. Why should open source be any different? I'd venture to say that the reason for all the competition is probably just that it is simply a reflection of life in the real world. In all endeavors, everywhere, there is competition. You can't do something without someone saying "I can do that better". Frequently they do it.

      You may as well say "Why have all these separate, independent commercial developers? Why not combine all of their efforts into one company that can focus on making the software the best it can be?" But we consider that bad. Why would it be any better if we made it an idealistic utopia? The Linux kernel is as good as it is in part because Linus encourages competition and lets the best code win, and getting better in part because of this.

      COmpetition is good. I will concede that there is a point where too much competition indicates the resources are really spread, and some consolidating would be a good thing, but I don't think we've reached that point here. We have two excellent media players, and they're both highly competitive with one another, so they keep getting better. Everybody benefits, no matter how much "wasted effort" you think is there. Shoe me a project that didn't have competition (such as Mozilla, which doesn't have much) that has not stagnated, become bloated, and generally sucked? Fact is, your girlfriend never looks as pretty when she's your wife. Competition is a good thing.

      --
      Like what I said? You might like my music
    12. Re:What about other software? by fucksl4shd0t · · Score: 2, Insightful

      See? You get a program that does what each one of the seperate programs do best, and only one install routine.

      Um, isn't the UNIX philosophy having a bunch of small applications that each only do one thing, and do it really well?

      Now.. what if all three groups combined their resources and put the best parts of each into one GOOD program?

      YOu say that, but we've already seen this crap in action. How much better has Internet Explorer gotten since Microsoft dominated the web browser? How much better has outlook express gotten since microsoft dominated email clients? We've seen very little improvement in many applications that exist as the sole application in its environment that does what it does (sole means > 90% users). Instead, they stagnate, without improvement. Is this what you want to have happen to free software?

      --
      Like what I said? You might like my music
    13. Re:What about other software? by InodoroPereyra · · Score: 2, Interesting
      Now.. what if all three groups combined their resources and put the best parts of each into one GOOD program?

      Well, I probably didn't make my point clear. Each of these programs use different criteria/algorithms to deal with partition tables. And it was this diversity what saved my ass. If they all got merged, they would settle for ONE path to solve a problem. And this is not necessarily good in general ... and wouldn't have probably saved my ass :-)

  3. Of course you were criticised! by 91degrees · · Score: 4, Funny

    I mean, imagine suggesting that a Linux user might not have a full and completye knowledge of the system, or that anyone should install Linux without first knowing absolutely everything about it.

    Are you an idiot? The MPlayer programmers were born with this information (which does probably make them about 12, which kinda figures).

    Rather than complaining you should be grateful and worshipful that they deigned to come down to this level, and allow us mere mortals access to their holy media player.

    1. Re:Of course you were criticised! by Anonymous Coward · · Score: 3, Insightful

      "I know it's illegal, but could you add DVD Support?"
      "Why won't it Play DVD's?"
      "I can't watch my DVD"

      That's enough to make me cynical.

    2. Re:Of course you were criticised! by curne · · Score: 5, Insightful

      Much amused.

      But I cannot say I agree. I find it refreshing that a development team develops a high end program that requires some seriousness of people to use. It is becoming a widespread myth that free software developers are little Tele-tubbie-happy people just sitting on their asses coding for hundreds of idiots that luckilly flock to their mailing lists.

      MPlayer is a fantastic program (along with other fantastic media programs running on Linux & Co) so many users want it to work for them. And I think that the MPlayer core team acknowledge that but when you for time number 796 get an email reading 'I problem compiling, Please help!!! Is it bug?' with no log or dump... well the coding gets sour. So I can understand that criticism is difficult to take. Especially when it seems as unfounded as the first review.

      --
      All interpreted languages are abstractions over Lisp
    3. Re:Of course you were criticised! by squiggleslash · · Score: 5, Interesting
      Barr was criticised for quoting the FAQ out of context (an obviously tongue-in-cheek comment was quoted as some sort of flame of end-users) and criticising a pre-release program for faults also present, at the time, in Xine which he subsequently gave a rave review (the faults in this case concerned dependencies - Xine and MPlayer had more or less the same dependencies, but he ignored them in Xine's case and made a big deal of having to find them in MPlayer's case.)

      I fully understood the frustration the MPlayer community, which in my experience has always been very helpful and very proactive trying to create something that'll be ideal at the end of it (they may be wrong in some of the directions they've taken, but I don't doubt their motives), and really found the Barr article and his apologists somewhat disappointing. Barr really seemed to write the article in order to fire up a storm, certainly the quote out of context, an aggressive maneuver which it's hard to believe wasn't deliberate, backs this up.

      --
      You are not alone. This is not normal. None of this is normal.
    4. Re:Of course you were criticised! by Namaseit · · Score: 2, Insightful

      Well first of all, UT2k3 used the Loki installer. They didnt even make it.
      Second, Mplayer is compiled from source, its not binary. Doing binary would take away so many benefits that you get with Mplayer. I

      can play a dvd and Mplayer uses 5-15% of my cpu. Divx is 3-4% and playing ogg/mp3 is 1% at most. Mplayer takes practically *no* system resources to run. Ive turned a crappy 133mhz into a network jukebox. WIth my own experiences with Xine, its very unstable. The gui that people love so much in xine is what causes it to lock up 9 times out of 10. So ill take Mplayer.

      But when it comes down to it, use what you want, i really dont care.

      --
      75% of all statistics are made up!
    5. Re:Of course you were criticised! by dvdeug · · Score: 2

      Barr was criticised for quoting the FAQ out of context (an obviously tongue-in-cheek comment was quoted as some sort of flame of end-users)

      In the mplayer documentation, there's a section named users_against_developers.html. In it, Joe Barr is personally attacked. I would never bother filing a bug report on mplayer until I had compiled mplayer by hand and had a 10k example movie file that I had checked against the standards, not with that level of professionalism on the other end.

  4. Why review only the beta version? by TheOrquithVagrant · · Score: 5, Informative

    MPlayer 0.92 is the current stable release where everything works as expected.

    MPlayer 1.0-pre1 has some nice new stuff, but even though it has one thing (support for input from v4l devices with hardware MJPEG support) which I've wanted ofr a long time, the current pre-release is much too flakey for me to use, and I've gone back to 0.92.

    MPlayer 1.0-pre1 is for writing bug-reports, not reviews.

    Unless Mr. Barr had a conscious or subconscious WISH to find things that didn't work right, i don't see why he wrote his review for the pre1 version.

    1. Re:Why review only the beta version? by iabervon · · Score: 2, Insightful

      It makes sense to review a pre-release, particularly if the review turns out to be nearly entirely favorable. Since his issue with the mplayer before was that it wasn't sufficiently polished for an end user to install, and the difference between a stable 0.n release and a 1.n release is normally assumed to be whether it had gotten to the point of being generally useable, it makes sense for him to look at whether it seems likely that 1.0 will meet this criterion.

      And it turns out that he finds it satisfactory (evidentally he didn't trigger any of the bugs you've found); he has some notes about the documentation (there's one important thing, and 50 little things to check), the install (it complains about 50 things that don't matter, but they don't prevent it from working), and setting it up (the scripts put some things in the wrong place). His notes look like things that actually ought to get fixed just before 1.0 comes out.

      It's also interesting to note that he seems not to be upset at the developers any more, and actually amused by their mention of him in the documentation.

  5. MPlayer has matured... by Valar · · Score: 5, Interesting

    MPlayer has matured, both in code and attitude over the last year or so, or at least I've found it to be true. I never really had trouble installing it in the first place (all you had to do was *gasp* read the directions and follow them), but the install has gotten easier. I find that it also works better on my PC now. Additionally, their teams seems to had lost a bit of the attitude-- a quick glance over the docs doesn't reveal any references to how stupid the average mplayer user is :). Maybe they finally realized that attitude was offending some people,and hurting the project, so they got over themselves.

  6. Spot on! by idiotnot · · Score: 4, Insightful

    I've managed to compile and successfully run GNUMach and GNU/Hurd from CVS. I know my way around building code. But mplayer is still a pain in the ass. Seriously. And when I read the forums, I didn't dare ask a question. The developers' attitudes represent one of the most valid criticisms of the Free Software world -- support is fleeting.

    As for using the software, it works pretty well, and has steadily improved. But I don't build it anymore -- I use the unofficial debian packages, and they work pretty much flawlessly.

    1. Re:Spot on! by lobsterGun · · Score: 4, Funny

      You just need to know how to ask. The trick is to phrase your question in such a way as to insult the dev team, that way they feel a duty to defend their project (This actually works on any open source project).

      Example: You are having trouble with 'foo'.

      Wrong way to ask for help:
      You ask - "Could someone please help me get foo working?"

      They answer - "STFU n00b!" -or- "Read the FAQ n00b!"

      Right Way to ask for help:
      You post - "This application sucks. Foo doesn't work worth a damn"

      They answer - "Dood! you're probably forgetting to compile with the -Dl337 flag. If that doesn't work email me at progMan@hotmail.com"

      Simple enough?

    2. Re:Spot on! by 0x0d0a · · Score: 4, Interesting

      More seriously, there *is* a wrong and right way.

      Ask a specific question. If you say "Can someone help me to get X working...", you're going to get a "no". Why? Think of what you actually just asked -- you, one of zillions of people, just said "will you commit an unknown amount of time to providing me with support for free".

      If you say "When I run foo, I get a 'RTC support not included' error. What can I do to fix this?", and you *checked* the documentation and google first, then you're likely to have a lot more luck, because the other folks can immediately respond with an answer. They just can't *do* anything with a "it doesn't work" post, and most folks are not interested in investing the time require to send out another post with a list of what information is required so that perhaps they can get a response back so that perhaps they can fix a random person's problem. You need to send out a post with enough information to allow the folks you're asking for help to answer your question without immediately needing to ask you for even more information.

      This is no different from free support for closed-source software. You'll get the same response on USENET if asking a question about Half-Life. If you're paying someone to sit on the phone and answer questions (like someone at Microsoft with an MSDN support incident, or someone at Red Hat with a commercial support package), *then* things may be different.

      It's not just a matter of *insulting* the other person -- you need to include enough information to let them do your request.

    3. Re:Spot on! by fucksl4shd0t · · Score: 2, Informative

      Ask a specific question. If you say "Can someone help me to get X working...", you're going to get a "no". Why? Think of what you actually just asked -- you, one of zillions of people, just said "will you commit an unknown amount of time to providing me with support for free".

      While you did an excellent job summarizing the points, Eric S. Raymond wrote an article that I found particularly helpful, and after reading and putting into practice what he was saying (all of which made sense) i started getting a lot more help from projects, and was actually able to contribute a lot more in general. Much more satisfying, I say.

      --
      Like what I said? You might like my music
  7. Don't flame the devs by arvindn · · Score: 5, Insightful


    Doesn't the author understand how the Linux/OSS community works, or what? Its not the devs' job to make shiny installation druids that you can click through. That's what distros are for. If you want to compile software, be prepared to do your homework. If not wait for the .deb to become available or subscribe to RedHat network etc.

    Gimme a break.

    1. Re:Don't flame the devs by goldspider · · Score: 2, Informative
      "Its not the devs' job to make shiny installation druids that you can click through."

      If they want their software to gain popularity and more widespread usage, they will.

      --
      "Ask not what your country can do for you." --John F. Kennedy
    2. Re:Don't flame the devs by curne · · Score: 2, Insightful

      A slight correction: Developers can flame other developers, since they can apreciate the problems involved.

      Idiot lusers who do not know the difference betweeen C and csh scripts should not flame developers since they will invariably make asses of themselves. They can flame the distro makers, who get paid for helping (or at least, the idiot lusers should pay them for the priveledge of flaming them).

      Geez, cant everyone just get along?

      --
      All interpreted languages are abstractions over Lisp
    3. Re:Don't flame the devs by pgrdsl · · Score: 5, Insightful
      Once upon a time, many years ago, free software was wild and untamed. When you downloaded a tar-file, it may, or may not, unpack in ".". Sometimes it was a shar(k) and you had to hope it didn't eat any of your files when you ran it.

      And then, once you had your nice shiny sources, you could compile it. After, of course, hand editing the Makefile. Oh, and the other one. And, damn, that silly config file. And then you would fix all the compilation problems because it had been developed on a different version of Unix, and used strdup.

      But, in those days, men were real men, and hackers were real hackers.

      People complained, whinged, sent patches, and things improved.

      And then, miracle of miracle, automated configure and build scripts came. There was the perl one, which asked lots of questions that nobody ever knew the answers to. Then there was the GNU configure scripts, which tried out things and found what worked.

      And, yea!, verily, time was saved all round the world. Things started to work. Porting to other platforms became simpler. Installation was tamed, and things went were you expected them to.

      What I'm trying to get at is: the same argument about "be prepared to do your homework" was used years ago pre-autoconf. Nobody would even think of going back to hand-editing all those Makefiles.

      It doesn't take a vast amount of effort to get a sane build and installation process, and the amount of time it saves everyone (including the developers themselves) is massive.

      With distros it is less of an issue for mere mortals, but the benefit any open source project will get from being easy to configure and install is that developers who are willing to chase bugs will do so - because it takes no pain to build.

    4. Re:Don't flame the devs by argmanah · · Score: 2, Insightful
      Doesn't the author understand how the Linux/OSS community works, or what? Its not the devs' job to make shiny installation druids that you can click through. That's what distros are for. If you want to compile software, be prepared to do your homework. If not wait for the .deb to become available or subscribe to RedHat network etc.
      The idea that a user should expect to be a guru and that the developer has no responsibilities towards the community is part of what prevents the open source community from achieving more mainstream acceptance.

      I respect an open source developer's right to do what he wants to his project, but I have no remorse whatsoever for him when the community exersizes their right to flame the hell out of him when parts of his product are crap.
      --
      Overrated Moderation: This posts sucks... because.
    5. Re:Don't flame the devs by patriceCH · · Score: 2, Informative

      Last time I checked, packaging MPlayer had major license problems. I believe at some time it was not even allowed to package according to a clause in the MPlayer license.

      But even now there are problems because of all the libraries which are not in the GPL or any other Free Software license. And this is a problem mainly for Debian which has pretty rigid license terms.

      Just checked and yes, there are still issues. See http://www.mplayerhq.hu/homepage/design6/news.html #debianandsusesux.

  8. well, give VLC a try by Sam+H · · Score: 4, Informative

    VLC from VideoLAN accepts almost all the formats MPlayer groks. The major exceptions are the ones for which there is no GPL-compatible implementation. It can also transcode streams into different formats, or send them to the network, serve them as HTTP, etc. It is truly cross-platform and the Windows and OS X ports are extremely popular.

    --
    God, root, what is difference ?
  9. A good GUI by er_col · · Score: 3, Informative

    For those of us who are less than happy about MPlayer's default GUI, there are far better alternatives, like KPlayer for KDE.

  10. Who is this doofus? by Ih8sG8s · · Score: 3, Insightful

    This guy's article is self congratulatory and self seeking. I don't care what run-ins he's had with the developers in the past.

    A terrible review where he actually admits to not really checking it out fully, but still manages to come to the self-affirming conclusion that he was right all along, and takes the opportunity to take a personal jab at the project.

    The only thing I learnt from this article is that the writer is bitter, and lacks tact.

  11. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  12. Were the copyright violations fixed? (yet?) by ciaran_o_riordan · · Score: 2, Insightful

    The problem I heard about MPlayer was that it illegaly contained DivX code that was under a proprietary license.

    Last time I checked was two months ago and MPlayer was still in violation of DivX copyrights. No distro can distribute it as the developer releases it. This is the real problem. This pushes it from Free Software to "cracked warez".

    (SuSE, and maybe others, do distribute it but they rip out the illegal code, so it's missing a few codecs. Debian will also be shipping a stripped, legal version soon.)

    Ciaran O'Riordan

    1. Re:Were the copyright violations fixed? (yet?) by Anonymous Coward · · Score: 2, Informative

      Please, pretty please, before you talk about something you know nothing about, get your facts straight.

      MPlayer currently doesn't contain single line owned by DivX networks. None. Nada. (In past, they used opendivx, and while it was under opensource license, it was neither GPL compatible nor free software).

      Nowadays, MPlayer uses libavcodec library from ffmpeg project. It it fully LGPL library, you can find it on sourceforge. The reason that SUSE rips it out is simple - some algorithms are patented (please note that there is a difference between owning copyright on code and owning patent on software). The patents make it impossible to ship binaries as a part of business in some contries. However, shipping source code is OK.

      So, that much for your 'warez'.

  13. Don't forget movix, the bootable mplayer by elwinc · · Score: 2, Informative

    If you're a fan of mplayer, you might want to check out MoviX which makes bootable mplayer distributions. My favorite variation is MoviX^2. You boot from the movix2 CD, eject the movix2 CD, pop in a CD or DVD with any mplayer supported format, and there you go!

    --
    --- Often in error; never in doubt!
  14. mPlayer powers Xbox Media Player and Center by seven5 · · Score: 4, Interesting

    WOO HOO for mPlayer. I remember back in the day trying to get that mutha to compile. It was a pain in the neck. But once i did it, i had VIDEO ON LINUX!!! WOW. Now it is used all over as underpinnings for other apps. Its projects like these that are so great. This is where i feel opensource shines. Instead of doing a lot of work yourself, take a project that is established and working, and extend it. Xbox media player and now Xbox media Center both use mPlayer. By using the source that was available to them, it increased time to live so to speak. It works great and supports TONS of formats. Why reinvent the wheel. Especially in video players and html renderers (KHTML, MOZ).......

  15. Re:why by c1ay · · Score: 2, Funny

    Warning!!! Your system has been infected. Windows Media Player 9.0 is known to work only when the Microsoft Windows virus is present. As to your question, you might wish to use mplayer when you get linux reinstalled.

    --

  16. Re:Windows version? Huh? by Anonymous Coward · · Score: 2, Informative

    well there is a windows version
    www1.mplayerhq.hu/MPlayer/releases/win32-beta
    i use mplayer under windows linux and osX
    i like that you can begin to watch a movie
    while your downloading it that just rocks :)

  17. mplayer's option syntax annoys me by amoe · · Score: 4, Interesting

    Why did they pointlessly violate the established (and useful) double-dash for long options convention in favour of an ugly and irregular one dash for all options? I'm aware that it's probably an imitation of the X standard, but in this day and age that's probably not a good thing to imitate. Also, it doesn't allow you to abbreviate with one-character options.

    --
    You look beautiful! Incidentally, my favourite artist is Picasso.
  18. Re:The article by squiggleslash · · Score: 2, Interesting
    I downloaded the latest mplayerplug-in from SourceForge (there was an RPM for RH 9 available at the project site) and installed it. It was time to surf. First up, CNN. I requested a news video and told the CNN site that I preferred the Real format. No luck. The sniffer script detected that I was running Linux and offered to let me download RealPlayer 8. I declined the offer, which still wouldn't have allowed me to view RealOne streaming format.
    I believe RealOne is just a wrapper, but even so, you can indeed download a RealOne for Linux from Real's website. It's fugly, and it crashes occasionally, but it does by-and-large work.

    IIRC, do the usual things necessary to download RealPlayer for Linux, select RedHat ix86 RPM format, and then look for the link. That's how it was a few months ago, I don't know if it's been made a more findable download since.

    --
    You are not alone. This is not normal. None of this is normal.
  19. mplayer suid ?!?! by SpiritC · · Score: 3, Informative

    "... I made the Mplayer binary SUID and that helped. ..."
    i dunno why he would do that but if it is about RTC then a closer look to mplayer (excelent) documentation would show this:
    If you are running kernel 2.4.19pre8 or later you can adjust the maximum RTC frequency for normal users through the /proc filesystem. Use this command to enable RTC for normal users:

    echo 1024 > /proc/sys/dev/rtc/max-user-freq

    --
    Smile... tomorrow will be worse.
  20. Illegal distribution of Win32 codecs by Anonymous Coward · · Score: 2, Interesting

    The Mplayer project's distribution of copyrighted win32 codecs is illegal.

    One needs explicit permission from the copyright holder to distribute copyrighted works.

    The Mplayer project does not have such permission from Apple, Microsoft and Real.

    The codecs are available for free (as in beer) from their respective owners, but the included EULAs do not grant permission to redistribute.

    It is obvious why Mplayer has yet to be accepted by Debian. The Mplayer team has no respect for copyright law and continues to violate the law.

  21. Barr and bias by 0x0d0a · · Score: 4, Insightful

    Won't this seem daunting to the end user (labelled automatically as stupid), having two different applications, with individual libraries, for doing the exact same thing.

    No. Xine should be installed on systems intended for non-techie end users. Mplayer is not a particularly great choice for non-techies. A'rpi is very much opposed to the idea of binary distributions (since it means that things may run slightly slower on a given system), and Mplayer can support so many things that to set up everything required for full support during a build can take a long time. It's less bad than building GNOME or KDE, but it's definitely not an "rpm -Uvh" either.

    That being said, I use mplayer exclusively, and love it to death. It's keyboard controllable, can be used without one of those godawful "fake media player" UIs, is faster than anything else in existence, and has support for just about every interface and codec under the sun (that Open Source folks can get their hands on or reverse engineer). Those of you not familiar with Barr and A'rpi (the lead mplayer developer for a long time) should be aware that the two intensely dislike each other, and have flamed each other for ages. Regardless of how good Barr is in most areas (and this review seems pretty reasonable, saying that "mplayer ain't a great choice for Linux newbies", which is definitely true), keep in mind that he's quite likely to have some bias, as A'rpi does when talking about Barr on the mplayer website. I take both with a big, big grain of salt.

    Perhaps some collaboration between MPlayer and Xine should occur.

    It does. Of course, it's full of people flaming each other for not giving sufficient credit, but the two projects have shared a *ton* of code in the past, and is the only reason either of them are as good as they are.

  22. Re:Here we go again... by dasmegabyte · · Score: 4, Insightful

    His argument:
    "I am a user savvy enough to be running linux. I am bright enough to fix problems. And yet, it was not easy for me to install this application. Therefore, it will be even harder for somebody who is new to Linux."

    Your argument:
    "What an idiot! He should have read the acoryphal poorly laid out document! Things are easy if you do all the chores perscribed to you by developers with no talent for technical writing and different systems than you!"

    My argument:
    "RTFM is not a valid complaint. Windows software installs without a manual. It does not expect you to RENAME directories after installing things to get them to work. It does not expect you to KNOW what codecs you want to use and already have them downloaded. It allows somebody to do what they need to do before hacking the source code of the underlying software. Why can't linux software do this as well. Oh right. Because we're better than them."

    --
    Hey freaks: now you're ju
  23. Don't run SUID root! by jimbrewer · · Score: 4, Informative

    Do not run SUID root if there is any other way to get the desired performance. From: http://www.securityfocus.com/archive/1/339193 Severity: HIGH (if playing ASX streaming content) LOW (if playing only normal files) Description: A remotely exploitable buffer overflow vulnerability was found in MPlayer. A malicious host can craft a harmful ASX header, and trick MPlayer into executing arbitrary code upon parsing that header. MPlayer versions affected: MPlayer 0.90pre series MPlayer 0.90rc series MPlayer 0.90 MPlayer 0.91 MPlayer 1.0pre1 MPlayer versions unaffected: MPlayer releases before 0.90pre1 MPlayer 0.92 MPlayer HEAD CVS Notification status: Developers were notified on 2003.09.24 Fix was commited into HEAD CVS at 2003.09.25 02:36:36 CEST MPlayer 0.92 (vuln-fix-only release) was released on 2003.09.25 12:00:00 CEST Patch availability: A patch is available for all vulnerable versions. Suggested upgrading methods: MPlayer 1.0pre1 users should upgrade to latest CVS MPlayer 0.91 (and below) users should upgrade to 0.92 OR latest CVS MPlayer 0.92 is available for download. -- Gabucino MPlayer Core Team

  24. Missing links? by Clith · · Score: 3, Informative
    Why are there zero links to Mplayer in this submission? Or even in the (above-score-of-2) replies? Here are some links:
    MPlayer site
    MPlayer downloads
    MPlayer for Max OS X site
    MPlayer for Mac OS X downloads
    Hope this is helpful for someone.
    --
    [ReidNews]
  25. and this bullshit too: by pr0ntab · · Score: 2, Insightful

    want a dvd? You need to use the "dvd" URL

    dvd://title#

    But this syntax

    dvd://title#/chapter#

    Doesn't work, you need this:
    dvd://title# -chapter chapter#

    Which is more typing than: -dvd title# -chapter chapter#

    And filters for -vop are applied IN REVERSE ORDER.

    How about this malarky:

    -vop detc=dr=1:ar=0,denoise3d

    commas distribute over colon, colon over equals, except for the first equals that shows a filter has options.

    urrggghh...

    Oh, and the syntax is horrible just in general. Some options only take effect when they come before or after certain things, certain ones depend on other options in weird ways (video filters, codecs, and -fps/-ofps hell).

    Still, I love mplayer. Who am I kidding. I just way too much time trying to figure out how to do things I KNOW should work, I just can't get a handle on it.

    ecasound, while having also having an insanely rich command line, is more logical.

    --
    Fuck Beta. Fuck Dice
  26. MPlayer hard to install? by Metalhead01 · · Score: 2, Funny

    emerge mplayer Wow. that was tough. I think I need a beer and a pizza to help recuperate after such a trying ordeal.

    --
    The only reason I keep my Windows partition is so I can mount it like the bitch that it is.
  27. Re:Here we go again... by the_mad_poster · · Score: 2, Interesting

    Windows software installs without a manual

    It also isn't being installed from source, rarely has anything close to the option flexibility of source-installed software, and is usually completely useless in the event that something fails in the process. I have a copy of VS6 here that bombs near the end of the installer and there's not a damn thing I can do about it, for example. I have shit installed here that won't uninstall properly and, short of removing it manually and hunting down and undoing every little registry key and config change, there's not a damn thing I can do about it.

    Why does everything have to be "the way Windows does it"? Windows sucks, that's why I use Linux and BSD. I don't WANT it to act like Windows. That's the POINT. It's NOT Windows and it WORKS, that's why I LIKE it. It's not hard to type "apt-get something". I'm sick of people apologizing for users who are too coddled and/or stupid and/or lazy to even do that - it's how you wind up with people with busted-ass systems who call you up and whine all the time that the "computer is broken". Gee - that's because you installed every damn thing you came across by double-clicking randomly...

    It's okay to make things easier to a point, but you have to put some responsibility on people for what they install. Windows doesn't, and, as a result (aong with some other issues), most Windows systems out there are hideously broken beyond repair.

    Besides, if you're going to immitate ease-of-use, immitate Macs, not Wintels.

    We're "better than them" not because we're "1337 d00dz", but because we actually make people stop and think about what they're about to do before they do it...

    --
    Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
  28. Re:What's best for DVDs? by Malc · · Score: 2, Interesting

    Like I said: I found it died a lot. I tried with The Matrix and it died three times getting to the main menu, a couple of times it died immediately on trying to play the movie, and a couple more times during playback. It just disappears without any message.

  29. Re:difficult my arse. by parabyte · · Score: 2, Informative

    Even more funny, I did the same thing last night on a Out-Of-the-Box SuSE 8.2 System; I just had to remove the useless crippled mplayer that comes with SuSE.

    At first I was a bit scared by all this stuff about installing additional codecs in the documentation, and I even downloaded ffmpeg because I follwed the documentation step by step, but later I found out it applies to the cvs checkout only, is already included in the release tarballs.

    The fact is: for most cases, the included ffmpeg and other included codecs will already play more stuff than any other player, and installation was as painless as you describe, I just had to add a symlink /dev/dvd -> /dev/sr0 amd enable DMA access for my DVD-drive to play dvds. Ah, and I had to run it as root, and you must not forget xhost + then to allow it to open a window. And Mplayer is the most blithering piece of software I know, but I found these messages were generally helpful.

    I really love mplayer because it is fast and responsive, delivers a much better quality than any windows player I used, has the freedom to jump ten seconds with arrow keys, ignories dvd no-skip zones, allows to adjust audio/video sync, to easyly correct aspect ratio, to adjust pan-scan (E/W key) and has really good deinterlacing for my kite surfing dvds.

    If there is a piece of software that make me feel liberated, it is mplayer; it is the most single reason for me to boot linux as there is nothing comparable for windows. (Yesterday I found out mplayer runs under cygwin, but I didnt try yet)

    p.

    --
    Without order, nothing can exist. Without chaos, nothing can be created.
  30. Re:or take a look at Xine by fucksl4shd0t · · Score: 2, Insightful

    But for a media player, i found Xine to be better than both. It supports all the formats that mplayer supports, it also has a browser plugin, but it handles DVDs a lot better. In fact, the DVD menus and stuff like that works exactly as with a standalone DVD player.

    Actually, it doesn't seem to support all the same formats that mplayer does. For one thing, mplayer uses win32 codecs to play some of the formats it plays. I think they both use liblavac for divx playing, and they both play all of my .avi files (I have some commercial proprietary stuff in windows that won't play most of my .avi files, but mplayer and xine in Linux play them with no problems). Xine doesn't play .asf files, but mplayer does. And I've a few mpg's that mysteriously don't play on xine.

    My main bitch about xine is how it renders the movies. For some reason, mplayer renders much more sharply and clearly than xine. Doesn't make sense to me, unless one is optimizing the display for my slow hardware and the other isn't, or one is trying harder to scale up without getting blocky and the other isn't.

    --
    Like what I said? You might like my music
  31. Re:or take a look at Xine by halfelven · · Score: 2, Informative

    it doesn't seem to support all the same formats that mplayer does [...] Xine doesn't play .asf files


    If you install the Win32 codecs, Xine will happily play all those formats you mention.

    I've a few mpg's that mysteriously don't play on xine


    I've a few mpg's that not misteriously don't play but on one of the players that i use (xine, VLC, mplayer...) and on none of the other. The "mplayer plays all files that other players won't play" myth is just that: a myth. You will always find files that are not playable on all players (or even worse, are playable on only one player).

    mplayer renders much more sharply and clearly than xine


    You are probably not using the Xv mode in Xine. If you use XShm (compatible with almost any hardware, but slower) the image is kinda blocky indeed. But any player (not just Xine or mplayer) that uses the Xv mode has the same sharpness. I actually spent some time figuring out this issue and i'm pretty sure about what i said above.

    Like i said, both players (Xine and mplayer) are pretty much the same, except that Xine handles DVDs a lot better (mplayer's implementation is only the bare minimum).
  32. My own "review" of mplayer/mencoder by Dr.Dubious+DDQ · · Score: 2, Interesting

    In short form...

    Pros:

    • Probably supports more formats and codecs than just about any other project (on just about any other platform). Though typing "mplayer /dev/random" and having it show me "Return of the King" doesn't QUITE work yet...
    • Has a HUGE array of features
    • configure script for compilation is surprisingly 'smart' about picking options for optimal operation
    • LOTS of documentation online
    • error messages are often quite informative. (I've gotten used to terse "Unable to Conflugalize the Blurglemeister. Aborting." messages, where MPlayer tends to instead say things like "Could not Conflugalize the Blurglemeister. This could be due to too slow of a CPU or insufficient memory. Try again with -no-conflugalize or -framedrop")
    • huge range of potential uses, beyond 'playing videos' (exporting to external encoders, rendering subtitles, postprocessing video, correcting framerates, etc. etc.)
    • "Cross-pollinates" with other projects, most notably FFMPeg(/libavcodec) and Xine.

    Cons:

    • Parameter syntax is somewhat non-standard
    • Sometimes hard to figure out which option to use for a specific process
    • a few holes in the documentation (e.g. details of what some of the postprocessing filters do and what the parameters for them mean, exactly)
    • Mencoder only supports .avi output (or .mpg, but this is experimental)
    • Can't 'directly' create (S)VCD-compliant video at this time (but there are scripts for doing so using mplayer and mpeg2enc/mp2enc)
    • Some options are inconsistent between mencoder and mplayer (e.g. -ofps ["adjust the framerate by copying or dropping frames"] exists in mencoder but not mplayer)

    Maybe a Pro, maybe a Con:

    • It has a GUI, but the GUI is something of an 'afterthought'. (The fact that a GUI exists is probably part of the reason so many people assume mplayer is intended to be a 'general user' program. MPlayer might be better off not even having one. On the other hand, choice is good.)
    • Can use Windows codecs for many formats that aren't 'natively' supported (complicates distribution issues and only works on i386 platforms, but at least provides a 'fallback' method for viewing some otherwise-unviewable files)
    • Is NOT a project focussed on 'end-user' applications. (From my perspective, this is why it has so much functionality - the developers 'waste' little time "making it look pretty" or "so simple even an idiot can use it", but it gets them subjected to a lot of abuse from people who resent those lacks. I worry that the abuse will discourage developers from doing anything...)
    • So many features it's hard to tell sometimes what you can and can't do with it...

    I find it interesting, incidentally, that MPlayer supports Ogg Theora better than XIPH does at the moment, in my opinion....(mplayer actually does play back Ogg Theora files generated by the Theora CVS quite nicely. Now if only Xiph would ever work on Ogg Theora and the Ogg specification again...)