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.

353 comments

  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 Psychic+Burrito · · Score: 1
      Yep, I like it too. The only two things that bothers me is
      • the fact that it takes up two dock icons and
      • when mplayer is already running and I doubleclick a movie in the finder, mplayer comes up to front, but in 80% of all cases it won't open and play the file, instead just sitting there.
      Anyway, it's free, and I like it. Pressing the left/right arrow keys to instantly jump back/forward 10 second absolutely rocks - I wished my physical DVD player had this feature :-)
    3. 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.

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

      I'll try it again when 1.0 is final, but I had stability problems using mplayer, usually as a result of trying to play a large, very high quality DivX file.

      VLC warns me that my hardware can't keep up with the file and lets me cancel gracefully. The last time I tried this with mplayer, the whole app siezed up, used 100% of my system resources, and didn't give me an opportunity to quit or close the file. I was in fullscreen at the time and had a hard time getting control back from the app.

    5. 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.
    6. Re:Great for OSX by Anonymous Coward · · Score: 0

      Yes, high-bitrate videos will bring iBook to knees, also happens to me.

      MPlayer will warn you, unfortunately the warning goes to Console.app.

      If it happens again, try pressing key 'q' or 'esc'. May take a few seconds, though.

    7. Re:Great for OSX by the_2nd_coming · · Score: 1

      how the hell do you install it?

      I download the stuff and I don't get a program.

      --



      I am the Alpha and the Omega-3
    8. Re:Great for OSX by Anonymous Coward · · Score: 0

      Are you sure he didn't mean your safe? Perhaps he wants to know the combination ;)

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

      Maybe you downloaded the source...

      Get the app here:
      http://prdownloads.sourceforge.net/mplayero sx/MPla yerOSX2b5.dmg?download

      Just drag the "Mplayer OS X 2" app where you want!

    10. Re:Great for OSX by Anonymous Coward · · Score: 0

      Actually I disagree. Mplayer does a lot of work in software that is unnecessary in this day and age. The result is that higher resolution DivX movies play very choppy on slower computers. Compare the speed of the 3ivX plug-in for quicktime, or FFusion (FFMPEG QT plug-in) to that of Mplayer and it is like night and day. I've ripped several DVDs to fairly high resolution, high bitrate DivX that just won't play without dropping frames on my iBook 700. Using Quicktime Player with the 3ivx or FFusion plug-in plays these movies flawlessly.

    11. Re:Great for OSX by Anonymous Coward · · Score: 0

      I did a very basic test between MPlayerOSX, VLC and Quicktime with the new divx plugin (so it has mp3 support), 3ivx and AC3 plugins.

      I tested it on one single divx: Vanilla Sky - the start scene. My machine is an ibook G3 800MHz with 384MB ram.

      VLC: has to drop allot of frames, not a smooth playback at all.
      MPlayerOSX: has to drop a few frames. (when it was turning over the building in Vanilla Skys, it stuttered.)
      QuickTime: very smooth playback, didn't see any frame dropped.

      Offcourse, it's bloody annoying to find and install all those plugins for Quicktime. So if you have a fast enough machine, go with MPlayer. Slower machines should behave better with Quicktime.

    12. Re:Great for OSX by code_echelon · · Score: 1

      I have also found this with MPlayer, that it seems to do more work then neccessary. I have ripped a couple of my purchased dvds and they seem to drop frames when using MPlayer, however I have tried them using Xine, Divx Player 5.0, Windows Media Player and Quicktime with the 3ivx plugin and they don't drop the frames.

      I haven't played around with MPlayer that much so maybe its something that I can change in the configuration. Currently I am looking for the best movie player for Linux. I am currently using Xine and am quite happy with that however I have noticed a few issues, does anyone have any reasons that another movie player is better for linux. I tried MPlayer on my Linux OS a little while ago and it was dropping some frames. The computer is not that fast however using Xine the movies usually play quite well. All suggestions will be appreciated.

    13. Re:Great for OSX by chregu · · Score: 1

      The following could help to at least maintain A/V sync

      -framedrop (also see -hardframedrop)
      Skip displaying some frames to maintain A/V sync on
      slow systems. Video filters are not applied to
      such frames. For B frames even decoding is skipped
      completely.

      -hardframedrop
      More intense frame dropping (breaks decoding).
      Leads to image distortion!

      man mplayer gives you more hints about tweaking mplayer ;)

    14. Re:Great for OSX by fucksl4shd0t · · Score: 1

      I haven't played around with MPlayer that much so maybe its something that I can change in the configuration. Currently I am looking for the best movie player for Linux. I am currently using Xine and am quite happy with that however I have noticed a few issues, does anyone have any reasons that another movie player is better for linux. I tried MPlayer on my Linux OS a little while ago and it was dropping some frames. The computer is not that fast however using Xine the movies usually play quite well. All suggestions will be appreciated.

      IN my experience, MPlayer is better than xine. Xine, by default, drops frames to keep A/V sync, and mplayer does not do this by default. Mplayer tends to get caught up in the userspace, so if you SUID it it should run better. I have not done this myself. The big advantage I have with Mplayer is actually it's keyboard interface. It does kind of suck sometimes (in a recent build I did Mplayer wouldn't recognize all the keys, but I'm blaming Mandrake for that), but it is really awesome otherwise. MPlayer also has the ability to specify video and sound drivers on the command line. Xine may have it, but since Xine is GUI oriented and mplayer is not, xine has interface issues that mplayer doesn't have (and vice versa, if you don't like command lines). The biggest plus to using mplayer, in my opinion, comes when you associate it with the file extensions it plays. Then you don't need a fancy gui to play movies. You play them directly out of konqueror (or nautilus, or whatever you use).

      When it comes down to it, MPlayer and Xine are the two best video players for Linux, so what you really need to do, probably, is spend some time with both of them getting more intimate with them. Then you'll find that one is better than the other, and you may disagree with me. :)

      --
      Like what I said? You might like my music
  2. Re:I've used mplayer on and off for a while now... by JimSpike · · Score: 0

    Try Xine! I like it alot!

    --
    I'm not addicted to cocain, I just like the smell of it...
  3. Re:I've used mplayer on and off for a while now... by Trigun · · Score: 1

    Xine works as well, accepts Windows Codecs, and is as easy to use. The front-end sucks ass tho, so get your keybindings set.

  4. Re:I've used mplayer on and off for a while now... by Anonymous Coward · · Score: 0

    I'm in 2 minds. Using mplayer for me is very settle-for-almost-working. It's painful in part, it's frustrating, it does MOST of what I want while always having something missing that I need, yet it's still the best out there.

    And getting abuse from developers when I dare ask for fixes is tiring, people. I'm no coder, I just want to watch video in Linux

  5. 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 Anonymous Coward · · Score: 0

      Are you involved in either project? If not, who are you to say that more collaboration is needed? Clearly, you've never worked with the children running MPlayer, or you would know why the Xine project has no interest in working with them, either.

    4. Re:What about other software? by Oxide · · Score: 0

      Perhaps some collaboration between MPlayer and Xine should occur.

      No. Having two different products means compitition. Compition means that we will have two good products that are always getting developed to be better than each other. The end user will have a "choice" between two great products instead of one slappy.

    5. 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!

    6. Re:What about other software? by Kandel · · Score: 1

      No, I'm not involved in either project, but I am just thinking of the end users here.
      Why have two good applications that essentially do the same thing, when you could merge them into one really good application. It will not only create a better product, but will create some unification in desktop video playback.
      With Linux slowly entering the Desktop market, every effort to make the end user experience that more care free must be made. The end user does not wish to ponder over whether to play their new DVD in MPlayer or Xine. They want the simplicity of Windows where they just pop it in and load up a single application. Hassle-free.

    7. Re:What about other software? by sewagemaster · · Score: 1


      you're right about xine. it plays pretty much everything - except a few wmp files here and there. just dont really understand why it hasnt been getting the 'publicity' as mplayer's been getting.

      but for some reason mplayer isnt included in the debian distribution. (only a gtk frontend, but the player is no where to be found) i've been having problems setting xine's video browser plugins. i've heard it's really easy with mplayer. probably this has to do with mplayer being packaged with proprietary libs?

      anyway if anyone knows an apt source to player and its plugin that would be great...

    8. Re:What about other software? by Anonymous Coward · · Score: 0

      You think that Windows doesn't have multiple players? WinDVD, PowerDVD or WMP? In linux, it's the same like under Windows - just pick one, your DVD will play anyway.

    9. 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
    10. Re:What about other software? by sewagemaster · · Score: 1

      doh, should have scrolled down the article...


      Just add

      deb http://marillat.free.fr/ unstable main

      to /etc/apt/sources.list

      # apt-get install mplayer-686

      That's it.

    11. Re:What about other software? by Kandel · · Score: 1

      Ok...good point. There are multiple players for Windows...but each one has their one good points and bad points. Wouldn't you prefer to have one kick ass video app, rather than 5 video apps that have their own individual good and bad points?

    12. Re:What about other software? by Anonymous Coward · · Score: 0

      Yes I would prefer having one kick ass player.

      However, the problem is, that the features that I love, others hate[*]. And vice-versa. You can't please everyone, that's human nature.

      [*] for example, I love mplayer's OSD and keyboard control. Others hate it and prefer 'mouse-controlled-everything' approach.

    13. Re:What about other software? by miletus · · Score: 1

      "Compitition" also means scarce developer resources are squandered in duplicated efforts, rather than producing something new. Plus, new Linux users get to face a bewildering array of almost complete applications in each category (e.g. I was trying to explain to a friend how to copy a CD-ROM, only to find three different GUI front ends, none of which worked as well as the command line). How is this a good thing?

    14. Re:What about other software? by mahdi13 · · Score: 1

      Remember...what you would consider a "kick-ass app" another person would consider it "crap"
      The great thing about have two (or more in this case, haven't seen mention og Ogle yet) is that the end user gets to make the final choice about which app they prefer to use.

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    15. 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.

    16. 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
    17. Re:What about other software? by BrokenHalo · · Score: 1
      To be honest, I haven't really used xine much, as I had issues with it crashing a while back. But MPlayer is truly a great program which handles every type of movie file I've come across (so far).

      The article's right where it says installation can be non-trivial, though. That's why I've still got 0.90 running on my computers. I'll get around to upgrading eventually, but to be honest, I think it's as good as it gets...

    18. Re:What about other software? by BrokenHalo · · Score: 1
      MPLAYER.EXE is merely an antiquated, conventional, DOS-format file name.

      This is true, but remember that those of us in *NIX land don't have to put a .EXE on the end of a filename to make it a program.

      "mplayer" is sufficient.

    19. Re:What about other software? by BrokenHalo · · Score: 1
      but for some reason mplayer isnt included in the debian distribution

      It might have something to do with the fact that (as it says somewhere in the documentation) mplayer sort of has to be built individually for it to work properly.

      I don't know if that's actually true, though. I wouldn't be surprised if there were licencing issues relating to those Win32 codecs that render the thing too "impure" for the Debian ethos. FWIW, it doesn't get included in Slackware either.

    20. Re:What about other software? by mopslik · · Score: 1

      "mplayer" is sufficient.

      The parent was wondering why MS wasn't going after the mplayer developers, claiming the name "mplayer" was theirs. I was merely pointing out that MS had no basis for such a claim. While MS uses the name MPLAYER.EXE on their Windows systems, I was illustrating that fact that filenames are irrelevant and cannot be used as leverage. That's it.

    21. 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.
    22. Re:What about other software? by antiMStroll · · Score: 1
      emerge xine

      emerge mplayer

      Help, I'm confused!!

    23. Re:What about other software? by InodoroPereyra · · Score: 1
      I don't consider your post "flamebait", but I have to disagree. Last weekend I fixed a bad partition table:
      1. sfdisk was the only utility to report the problem correctly (the partition table was inside the swap partition)
      2. fdisk was the only tool that would delete the incorrect partition
      3. parted was handy to recreate the swap partition avoiding the swap.

      They all do the same thing in principle. Although, you see ? Software diversity saved my ass :-)

    24. Re:What about other software? by gnalle · · Score: 1

      I believe that the authors of mplayer kindly asked distromakers not to include a crippled version of mplayer . This is why you do not find mplayer in Debian.

    25. Re:What about other software? by Anonymous Coward · · Score: 0

      You want to know why? I got a DVD drive a while back. Tried XINE... and it just wouldn't play CSS DVDs -- needed a plugin, and had me jumping through hoops and searching obscure sites with lots of blind alleys. Eventually I just said fuck it, downloaded mplayer and it worked right off. Stuck with it ever since.

    26. Re:What about other software? by sewagemaster · · Score: 1

      that's right, they've crippled xine because of DeCSS...

      because it's unpure for debian

    27. Re:What about other software? by DenOfEarth · · Score: 1

      I wholeheartedly agree. choice gives both projects strength...

      Thanks for mentioning the -fs thing...why does it seem so simple to do those things when someone else mentions them on slashdot, rather than drudgin through manuals? ah well, my love for linux is continued, as you helped me learn something new today, thus keeping my daily streak alive.

    28. Re:What about other software? by Overly+Critical+Guy · · Score: 1

      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."

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

      --
      "Sufferin' succotash."
    29. Re:What about other software? by Overly+Critical+Guy · · Score: 1

      Except that we're not dealing with commercial companies competing with each other, so your insane and bizarre toothpaste argument holds no water whatsoever.

      This is all community effort, and people need to gel resources instead of spreading them thin all the time just so they can have yet more conflicting user interfaces, skinning, and other reinvented wheels.

      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.

      --
      "Sufferin' succotash."
    30. Re:What about other software? by Overly+Critical+Guy · · Score: 1

      It also is redundant and reinvents the wheel. Instead of pooling resources, we get to listen to morons drone on about "choice" when what is required is a unification of resources so we can get away from this obsessive "let's reinvent the wheel all the time" mentality. It's like Linux users absolutely FEAR any change whatsoever.

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

      --
      "Sufferin' succotash."
    31. Re:What about other software? by poot_rootbeer · · Score: 1

      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.

      Well, Windows users don't seem to complain too much about having Microsoft Windows Media Player, Apple Quicktime for Windows, RealOne Player, and Winamp all installed on their systems simultaneously...

    32. Re:What about other software? by Overly+Critical+Guy · · Score: 1

      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)

      Uh, moron, who said anything about killing? What about merging?

      The mentality of Linux desktop users really gets me sometimes. I don't get the vehement opposition to combining resources to make killer, top-notch apps. Instead we need ten of each, all reinventing the wheel.

      --
      "Sufferin' succotash."
    33. Re:What about other software? by Anonymous Coward · · Score: 0

      You're a waste of resources.

    34. 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

    35. Re:What about other software? by ichimunki · · Score: 1

      The only thing insane and bizarre is that on the one hand you are talking about "successfully penetrat[ing] the desktop market" but you seem to think that is a reasonable goal for those not working at commercial Linux companies. I should think that for the guy(s) who make these individual programs that their own goal would be to make their program the best it can be-- why should they care about Linux On The Desktop(tm)? Insofar as merging with other projects or working together makes sense for these individuals, that's great, but unless you are going to give them a financial incentive to work together, I see no reason to expect them to do so just because you think there's some sort of "market" to "penetrate".

      --
      I do not have a signature
    36. Re:What about other software? by Anonymous Coward · · Score: 0

      You forgot about the unsuccessful fork, The AniMPlayer.

    37. Re:What about other software? by Brandybuck · · Score: 1

      Windows will never be taken seriously as a desktop system as long as it has multiple media players...

      --
      Don't blame me, I didn't vote for either of them!
    38. Re:What about other software? by mhesseltine · · Score: 1
      Two applications that do the exact same thing. Most sane people would see that as pointless and redundant. It's a waste of resources.

      So, by this logic, the availability of RealONE, Quicktime, Windows Media Player, MusicMatch, Winamp, etc. is pointless and redundant. After all, they all play video files.

      By extension, it's also pointless to have Windows Movie Maker, Adobe Premier, MGI Videowave, etc. since they all produce video files.

      Maybe we need to reconsider why there exists more than one project to fill a need?

      --
      Overrated / Underrated : Moderation :: Anonymous Coward : Posting
    39. 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?
    40. Re:What about other software? by FrostedWheat · · Score: 1

      the availability of RealONE ... is pointless and redundant

      Yes :)

    41. Re:What about other software? by Dave_bsr · · Score: 1

      or you can put fs=yes in your .mplayer/config...or when it starts, hit "f".

      --


      Who is this Anonymous Coward character, how does he post so much, and why is he always such a whore?
    42. 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.

    43. Re:What about other software? by michrech · · Score: 1

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

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

      --
      bork bork bork!
    44. Re:What about other software? by fucksl4shd0t · · Score: 1

      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.

      Considering that Windows (all flavors), MS-DOS, Mac OS (any), Amiga Workbench, et al, have ALL done this, then I really don't think users are gonna give a shit about it. The main thing is having the applications install and run out-of-the-box easily, and perform well. Otherwise, we've been dealing with shared library and static library problems for years, we're used to it.

      I'd also like to point out that last time I checked, Xine and Mplayer used most of the same libraries to do the same stuff, only using different libraries to do different things.

      --
      Like what I said? You might like my music
    45. 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
    46. Re:What about other software? by halfelven · · Score: 1

      xine-0.9.13 (the last version in the previous "stable" series) indeed had some stability issues.
      But you may try the latest pre-1.0 release, it seems to be rock stable. Also, if you install the Win32 codecs and Real, it plays all the formats supported by mplayer. Not to mention that DVD support is more evolved in Xine (handles DVD menus, etc.)

    47. Re:What about other software? by fucksl4shd0t · · Score: 1

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

      I've got three words for you:

      One Microsoft Way

      --
      Like what I said? You might like my music
    48. Re:What about other software? by UserGoogol · · Score: 1

      Windows Media Player is wmplayer.exe. Media Player 6.4 is mplayer2.exe, but in my Windows Media Player folder, I have no file called mplayer.exe on my computer.

      --
      "Never attribute to malice that which can be adequately explained by stupidity." -- Hanlon's Razor
    49. Re:What about other software? by fucksl4shd0t · · Score: 1

      or you can put fs=yes in your .mplayer/config...or when it starts, hit "f".

      I've got mplayer -framedrop -zoom associated with most video types in Konqueror, so I prefer to hit "f" when it starts. Frequent mistakes clicking the wrong movie. Also, sometimes I take advantage of opening credits and stuff to close the windows on my desktop (I have a slower computer, and MPlayer bitches at me about it all the time). In my opinion, no app should ever start fullscreen, but every app should have the ability to go fullscreen quickly and easily after it starts.

      --
      Like what I said? You might like my music
    50. 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
    51. Re:What about other software? by McLoud · · Score: 1

      Hah! and why in the hell do you think that linux or wharever os it runs should be different than windows that had hundreds of applications to do the exactly same thing with just different interfaces and sometimes none of them doing everything reasonably well in the same app? Of perhaps you forgott why we have 2 dominant desktops environments in linux?

      --
      sign(c14n(envelop(this)), x509)
    52. 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 :-)

    53. Re:What about other software? by mhesseltine · · Score: 1

      While I agree that RealONE is pointless (and obnoxious, and a resource hog, and borderline spyware); the existance of the other packages just proves the point. What would happen if RealONE was the ONE and only media player? You'd have to sell your firstborn to Real just to watch a video on your computer. You'd probably have to let the software phone home whenever it wanted to.

      This is the exact reason that choice is a good thing. And, with the software being open source, there's no legal reason that if the Mplayer developers develop some great feature, that the Xine developers can't analyze it and add the same feature to Xine or vice versa. In this case, re-inventing the wheel (which isn't actually what's happening) causes variations in design, features, etc. that create innovation.

      --
      Overrated / Underrated : Moderation :: Anonymous Coward : Posting
    54. Re:What about other software? by Doomdark · · Score: 1
      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.

      Why would it? You just happen to use one or the other? If they are exactly the same, what is the problem?

      The fact there are different gasoline station chains, which pretty much do the same thing; or banks, or supermarkets, or fast food chains; I don't feel overwhelmed by confusion. So why should availability of multiple similar apps really be a problem in that sense?!?!

      Now, there are other pluses and minuses involved; divided developer base is potential drawback... but increased competition is a definite plus. Plus there's less risk when all the eggs are not in just one basket. But your point seems like an odd red herring to me.

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
    55. Re:What about other software? by michrech · · Score: 1

      Three groups (in this case) combining resources to make one really good disk partitioning program is quite different (as they are more focused on making a good product instead of grabbing as much money as possible) than a huge company pulling anti-competitive moves to knock everyone else out of the market, you moron.

      Come back when you have a clue ready.

      --
      bork bork bork!
    56. Re:What about other software? by Shaklee39 · · Score: 1

      I disagree. Back when xbox software was maturing, xbox media player and YAMP were two seperate projects doing about the same thing, both with very skilled developers. They merged and now XBMP has become the best software (IMO) on xbox to date.

    57. Re:What about other software? by Qzukk · · Score: 1

      Uh, moron, who said anything about killing? What about merging?

      So lets see. You start with two, and when you're done, you have one. Yep. looks like Competition has been murdered here.

      The point is, mplayer has a GUI specifically because Xine had a GUI. Xine can play sorenson specifically because mplayer worked out how to do it. If they had merged before this point, you'd have xine with a gui, or mplayer with sorenson, but unless you somehow managed to keep the entire gang of coders together, and they didn't all just decide to sit on their linux platform monopoly and turn out version after version of crap like Windows Media Player has been doing since 7, you wouldn't have xineplayer with sorenson and a GUI.

      Not to mention the fact that even the best modular coding isn't hotswappable like you seem to infer. "what about merging?" you say. Merging what? The code bases are largely going to be incompatible. Even in perfectly modular, packaged code (which neither project is), you simply don't have a use for every module and widget that package X provides. Other modules and widgets that package X provides is almost, but not quite, exactly what you want, so you're still not going to use them (or in the case of open source, you stop everything you're doing to rewrite those widgets to the way you want them to be). What is compatible between them is probably already going to have been implemented. You'd wind up scrapping a majority of the code, and the half of the coders who lost out would either quit or spend their time getting re-acquainted with their new project.

      Instead we need ten of each, all reinventing the wheel.

      In a parallel universe not so far from ours, once upon a time Thag and Urg set out to invent an object that would make moving things easier. Thag beat stones together until he thought "this is the perfect shape for moving things!" Urg, seeing Thag's shape, beat stones together until he thought "this is better than Thag's shape".

      Then one day, Overly Critical Guy came and said "now, now, we only need one of these objects, now don't we?" and Thag and Urg decided to put their minds together. The result? Urg's pounded a large rock into a triangle-shaped stone, then Thag pounded a square hole into the middle of it. While the axle was born 200 years sooner in this universe, the entire dawn of civilization was set back 500 because Guy decided nobody should to try to make a better wheel.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    58. Re:What about other software? by fucksl4shd0t · · Score: 1

      Why don't you list some Free Software projects where everybody came together as friends and focussed on building the best package they could, in the presence of absolutely no competition, and succeeded in building a piece of software that makes everybody who uses it happy.

      Just one will probably suffice.

      In the meantime, consider these projects:

      GNU/Hurd

      Mozilla

      GNU/Hurd didn't have any Free competition until Linux came along, and they didn't take Linux seriously as competition. Now GNU still doesn't have a kernel that can be considered competitive, and everybody came together as one to build that kernel. You *could* argue that Linux pulled people who would otherwise have worked on Hurd, (or whatever GNUs kernel was called at the time). You could also argue that RMS chased them off by saying things like "you moron. Come back when you have a clue ready."

      Mozilla has been a dismal failure, although it is an excellent browser and an excellent development library. But since we waited 4 years for the shiny happy group of people united to make one really good browser, it's mostly irrelevant. Perhaps things would have been different if they had had competition? Perhaps things would have been different if they had accepted that IE was their competition?

      --
      Like what I said? You might like my music
    59. Re:What about other software? by Anonymous Coward · · Score: 0
      Perhaps some collaboration between MPlayer and Xine should occur.

      But then how would the OpenSource community enjoy themselves? Really, mplayer and xine fit right into the great tradition of

      vim vs. emacs

      KDE vs. Gnome

      gtk+ vs. qt

      Mozilla vs. Konqueror

      OpenOffice vs. KOffice

      ... what'd be the point if we couldn't have a good flamewar now and then? ;)

    60. Re:What about other software? by shellbeach · · Score: 1

      It also is redundant and reinvents the wheel.

      Correct. But then a lot of people who write OSS do so because they find reinventing the wheel rather fun. It's a challenge, "scratches an itch" and often leads to software that's better in some ways and worse in others. Who cares? Some people like xine because it does X, Y and Z; others like mplayer because it does A, B and C ... and I've got news for you - everyone's different. People don't always like the same things - and one enormous software suite isn't going to satisfy them anyway. As it has often been pointed out - you can't please all the cooks all of the time :)

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

      What resources?? You make it sound like developing mplayer or xine is a job for these people. Perhaps we could set up someone as supreme OSS guru who tells each opensource programmer what project they're going to work on and what they're going to do! Then no resources would every be wasted!!

      But it's not a job - it's a pastime, a puzzle, sometimes a frustration but always, ultimately, a pleasure. Welcome to the OSS world :)

    61. Re:What about other software? by Wolfrider · · Score: 1

      --Now here's where they got that deblink from:

      http://www.apt-get.org/

      --Unofficial deb repositories. Some great stuff in there.

      --
      .
      == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
  6. 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 jwinter1 · · Score: 1, Flamebait

      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.

      Don't read those messages. Procmail them to /dev/null/. But don't write pissy documentation. That's just childish.

      --
      Anything you can do, I can do meta.
    4. 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.
    5. Re:Of course you were criticised! by Anonymous Coward · · Score: 0

      The documentation wasn't pissy. It contained a tongue-in-cheek comment that Barr quoted out of context, and every Slashbot leapt upon before you can say "Al Gore said he invented the internet". It's easier to get outraged about something than it is to find out whether the facts actually match, and Barr's genius, if it can be called that, is to use that as a method to gain eyeballs.

    6. Re:Of course you were criticised! by petermdodge · · Score: 1

      If you were not to install Linux before you understood everything about it, then you, and I, and most of the Linux community except perhaps Linus Torvalds would not be installing Linux, because he is likely the only one that can say that he knows everything about Linux.

      User-friendliness is the mark of a program that truly cares about it's user base, and is an indicator of great worksmanship on the part of the programming team. MPlayer has improved, that much is for sure, but the do have a ways to go before they can rival the ease of the installs of other applications - Unreal Tournament 2003, for example. You can't tell me it's that hard to put something, even if it is source, into a binary installer! That aside, I'm sure they can make the install process easier on us.

      --


      Peter M. Dodge,
      Chief Executive Officer,
      LiquidFire Studios

      Platinum Linux - www.
    7. Re:Of course you were criticised! by 0x0d0a · · Score: 1

      mplayer dvd://

      If you want to watch other titles on the DVD, use dvd://1, dvd://2, etc.

      MPlayer does *not* have DVD navigation support (as xine and ogle do), so if you're a DVD fan and using the DVD browser interface is important to you, you may want to not use mplayer with DVDs.

      If you want to use a nondefault audio track and subtitles, you'll need to specify them. I needed -aid and -sid to watch my new copy of Ghost In the Shell in Japanese with English subtitles, rather than the nasty ol' dubbed version. Mplayer isn't going to give you a menu of said options -- you need to print 'em out with mplayer dvd:// -v and fill in the id numbers yourself.

    8. Re:Of course you were criticised! by Anonymous Coward · · Score: 0

      ...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 ...

      It's obvious that you don't run redhat then.

    9. Re:Of course you were criticised! by Zarquon · · Score: 1

      Actually it does use libdvdnav, but I haven't actually tried it to see how well it works.

      --
      "'Tis great confidence in a friend to tell him your faults, greater to tell him his." --Poor Richard's Almanac
    10. Re:Of course you were criticised! by Anonymous Coward · · Score: 0

      Writing pissy documentation may be the only way to keep sane, but it doesn't address the underlying problem. The people sending those "bug reports" don't read the pissy docs anyway.

    11. Re:Of course you were criticised! by Overly+Critical+Guy · · Score: 1

      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.

      Completely wrong.

      The widespreath my that is spreading is that free software developers don't give two shits about the user. It's all "volunteer work," and if anybody dares criticize apps, they should be burned.

      Which, of course, impedes progress. And then we wonder why Microsoft still slays on the desktop arena.

      --
      "Sufferin' succotash."
    12. Re:Of course you were criticised! by pantherace · · Score: 1

      um, yes broken, unsupported, and you have to specifically enable it... just to have it broken. Mplayer g1 will never support dvdnav properly. That is part of the reason for mplayer-g2 (which eventually will)

    13. Re:Of course you were criticised! by Dave_bsr · · Score: 1

      on the desktop, MS can't even touch either xine or mplayer with their programs. You'd think, with all their money, that they would start paying for audio codecs so users wouldn't need to install 5 different media players. You'd also think that they could write fast code so that WiMP doesn't run like a turtle compared to either mplayer OR xine on my 3-year-old hardware. I don't know why MS is "slaying" on the desktop, FAIConcerned, the war is over, and Linux wins hands down. Viruses, Security, Stability, Matching apps (crossover office, if you must, but SO and Textmaker and Abiword and...), Performance...and you can't tell me KDE doesn't look sweet all themed out. You can't tell me that.

      If only we could just get users to start with something Linux-y so it isnt' such a jump...

      --


      Who is this Anonymous Coward character, how does he post so much, and why is he always such a whore?
    14. 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!
    15. 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.

    16. Re:Of course you were criticised! by petermdodge · · Score: 1

      How does it being released in binary take away any of your benefits, unless you're going to modify the source code? In that case you're not likely to use the binary anyway, but for those of us who don't like taking another 5 minutes to tailor automake files to work on their Linux distro, a binary would be preferable, especially in .deb or .rpm

      --


      Peter M. Dodge,
      Chief Executive Officer,
      LiquidFire Studios

      Platinum Linux - www.
  7. Is it just my ... by rzei · · Score: 1

    ISP or is newsforge.net already down? Could someone do some karmawhoring or mirror, google doesn't have a cache of this document yet it seems.. :(

    -rzei

  8. Re:I've used mplayer on and off for a while now... by Anonymous Coward · · Score: 0

    http://www.hadess.net/totem.php3

  9. 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 Anonymous Coward · · Score: 0

      Stop to think for a minute. When you review something, and I mean really review it, things take time. Then, the writeup also takes time. So ya know, maybe he started things a while back and just got the entire review finished.

      It's kinda like taking it to the silly extreme and asking why he didn't use last night's CVS version to review

    2. Re:Why review only the beta version? by kafka93 · · Score: 1

      That's nice. But it's also an answer to the _opposite_ of the question that was asked.

    3. Re:Why review only the beta version? by Jeff+DeMaagd · · Score: 1

      The reviewer does acknowledge at the start that it is a pre-release.

      And yes, reviewing the full 1.0 would be better, but pre-release versions are supposed to give a good idea of what the release version will look like.

      It looks to me that he's found problems that are greater than what bugfixes will help. A prerelease should not have wholesale organizational problems in the software, heck, in my opinion, all the Windows betas I've seen are better than this.

    4. Re:Why review only the beta version? by mahdi13 · · Score: 1

      Yes, it's a pre-release...
      Yes, Joe wrote a review based on it
      Joe liked it and was only disapointed by the install...which I agree, still sucks :)

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    5. Re:Why review only the beta version? by Anonymous Coward · · Score: 0

      And if he was reviewing MPlayer 1.0 you'd say everyone knows point releases are buggy.

    6. Re:Why review only the beta version? by Anonymous Coward · · Score: 0
      as only disapointed by the install...which I agree, still sucks :)

      cd /usr/ports/x11/mplayer && make install

    7. Re:Why review only the beta version? by Anonymous Coward · · Score: 0

      Wow Brain! Is that really how to compile a program in Linux?? Your a FUCKING GENIUS!!

      Dumbass, it's how they have the fonts, codecs and GUI skins as completely seperate packages and the install will fail if you didn't read ahead in the instructions to find out these were needed BEFORE you compile mplayer!!

    8. 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.

    9. Re:Why review only the beta version? by MikeFM · · Score: 1

      Hey Pinky, I think his example was FreeBSD - Not Linux. I know such things are hard for you to grasp.

      You listed the problem completely right. You fail to read the instructions so you find completing the task difficult. Try reading the instructions and maybe you'll find that things go together easily.

      If you're a complete dumbass just use the prepackaged version. For debian that means, at most, adding a line to your sources. For RedHat that means downloading a couple rpm's and doing a quick 'rpm -U *.rpm'. Even compiling from source I've never ran into a problem. It all works easily if you have any clue what you're doing and bother to read the instructions.

      MPlayer does seem odd to use at first if you've only used programs like Xine, RealPlayer, or Windows Media Player but once you get over the bump of having to learn to use the command-line you'll find that MPlayer is a much more powerful program than your wimpy lil GUI programs. Want a pretty frontend anyway? Go download one. MPlayer is especially designed to make it easy for other developers to make their own frontends for it.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  10. 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.

    1. Re:MPlayer has matured... by Zardus · · Score: 1

      I find it really strange that everyone found mplayer that hard to install back in the day. I remember grabbing it when there were hate quotes about the GPL on their front page and they were selling anti-GPL merchandice, and even back then it took maybe five minutes to start it compiling, and five more to track down and download the win32 codecs. IIRC, there was just some script, like script/build.sh or something that did everything for you.

      I'm pretty sure I'm not just talking about a later version than the one Joe Barr reviewed last time, either. I remember reading his review when it first came out and thinking to myself how strange it was that he had such trouble installing it.

      --
      You can mod your friends, you can mod your nose, but you can't mod your friend's nose.
  11. 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 squiggleslash · · Score: 1
      About the only problem I've had compiling MPlayer has been if I wanted a particular feature that isn't default. You do ./configure, make install, and then find you forgot to ask for support for Windows codecs or something; and generally that's been getting better.

      There are aspects I don't like about MPlayer, notably the fact it has to be compiled by end users in the first place, but I think it's generally pretty solid as far as compiling it goes - and I use Slackware, I'm not running the same RedHat clone 90% of the planet's running.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:Spot on! by mchappee · · Score: 1


      I don't get it. I compile/install mplayer often. ./configure autodetects everything except user preferences such as GUI support, LFS. What doesn't work when you enter ./configure && make && make install? There have been a lot of posts proclaiming mplayer's compile-time surrleyness, and I'd like to know what's wrong with it. Is it not finding your libraries and/or headers?

      Confused.

      Matthew

      --
      /. finds me to be 20% Troll, 80% Funny
    4. Re:Spot on! by Anonymous Coward · · Score: 0
      LOL

      Somebody mod this up please

    5. Re:Spot on! by pikk · · Score: 1

      This isn't fair. Every day many developers, users (and me too) answer many questions, both when they are motivated and when they are idiotic. Most of the times users are satisfied, and only in rare cases developers use a bad language or insult users. As for building mplayer being difficult: in 1 year time it never failed for me, without running anythinh else than ./configure && make all install

    6. 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.

    7. Re:Spot on! by CableModemSniper · · Score: 1

      I don't get it, am I extradinarily lucky or something? Everytime I've installed mplayer its all always been the traditional ./configure (although I usually throw in some funky options like aalib support); make; make install.

      Short of ocasionally copying windows codecs to /usr/lib/win32, thats all I've ever had to do. I don't see how this is any worse then any other project distrubuted as source.

      --
      Why not fork?
    8. Re:Spot on! by Hawke · · Score: 1
      A friend of mine wrote a nice little rant on this subject, and so I shall refer you to it.

      http://obsequious.net/blog/tech/?permalink=2003080 8a.txt

    9. 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
    10. Re:Spot on! by 0x0d0a · · Score: 1

      Thank you. This is indeed a good, spot-on resource that I hadn't seen before. I was quite satisfied by the fact that his points seemed to be similar to my own. :-)

    11. Re:Spot on! by fucksl4shd0t · · Score: 1

      You're welcome.

      I wanted to thank you for giving the link to the US war crimes document. I've been wanting my wife to read it for awhile (we've been starting to follow the primaries and are looking at the candidates for all the things we don't like about the Bush family, so having this information will certainly help), but I couldn't remember where I found the link originally. When I read this reply of yours I clicked on the link, curious to see if it was the document, and lo and behold, it was. So I sent the link to my wife so she can check it out herself, now. :)

      --
      Like what I said? You might like my music
  12. Re:MPlayer ROCKS! by Anonymous Coward · · Score: 0, Funny

    Putting a blacklight in your basement and playing boom-chicka techno crap does not a nightclub make.

  13. 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 jj_johny · · Score: 1

      No you should flame the devs. Here is the simple math, for every problem that they leave in the finished product, the developers spend huge amounts of time wading through their mailbox and message boards with the same questions. So unless you are going to require that only developers download your code, the overall support equation says that you should cover your bases - make a resonable install, document cleanly and have some technical writers on your team.

    3. Re:Don't flame the devs by xanadu-xtroot.com · · Score: 1

      Its not the devs' job to make shiny installation druids that you can click through. That's what distros are for.

      Is there an ebuild for that?

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    4. 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
    5. Re:Don't flame the devs by vadim_t · · Score: 1

      emerge mplayer?

    6. Re:Don't flame the devs by CrosseyedPainless · · Score: 1, Funny

      shiny installation druids

      Now that evokes an interesting image....

    7. 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.

    8. Re:Don't flame the devs by Anonymous Coward · · Score: 0

      Yeah! I work for a bakery and those bastards actually expect ME to cook for their customers! I say, if I went through the effort of coming up with the receipe and give them all the ingredients, they should be smart enough to do the rest themselves. And God help them if they have a problem following my directions! All I hear is "How long do I have to preheat my oven?" "How do I crack eggs without getting the shell in there?" Fucking N00BZ!

    9. 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.
    10. Re:Don't flame the devs by Anonymous Coward · · Score: 1, Insightful

      It's very simple:
      If you want to create a well-engineered product for widespread use, you'd better get your act together and make a simple install procedure, maybe validating it doing user tests, etc. This happens in the real world outside the nerdy OSS community.

      If you just want to prove yourself and how well you hack codecs and don't give a d*mn about who will use it afterwards, you just don't excercise due dilligence.

      The Mplayer team obviously chose the latter.

    11. Re:Don't flame the devs by b-baggins · · Score: 1

      Question: What kind of developer thinks that making an easy install is NOT part of a development project?

      A) A lazy one
      B) A stupid one
      C) A Linux elitist one
      D) All of the above

      --
      You can tell a great deal about the character of a man by observing those who hate him.
    12. 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.

    13. Re:Don't flame the devs by 0x0d0a · · Score: 1

      You're getting paid to stand in the damn bakery each day.

      If you want to say "I'll pay $100 bounty via PayPal to whoever correctly ansers my question first", as you would if you went to Microsoft with a Word or Visual Basic issue and expected support, you're likely to have better luck. If you're paying for support, *then* you can say things like "foo doesn't work, and I'm upset". You aren't, so you can't.

      Hell, if you don't have a dedicated support package and you're using a general piece of horizontal market software, all the tech support people are going to tell you is "reinstall", then "return it" if their list of eight checklisted items (equivalent to an open source FAQ) doesn't provide an answer.

      That's just how software is.

    14. Re:Don't flame the devs by Qzukk · · Score: 1

      If you want to create a well-engineered product for widespread use, you'd better get your act together and make a simple install procedure

      Right.

      You came up with the idea, you work on it.

      I want to be there though when you get the Nobel Prize for the first psychic installation procedure ever.

      The author of the article whines that make install didn't produce ~/.mplayer/* ...

      So make install is supposed to psychically know what users are going to run the software? Maybe make a copy in every /home/*/.mplayer/* ? Oh, and while its at it, it will figure out what language you speak (maybe from locale...) and how crappy your eyesight is so it can download and automatically install the appropriate language and size fonts. Not only that, but this install process will also psychically work out your aesthetic preferences (for every user of the system!) and download and install the appropriate skin, too.

      Yep, I see a bright future ahead for you, soon-to-be-a-Laureate.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    15. Re:Don't flame the devs by pgrdsl · · Score: 1
      What you might expect to happen (as it does with, for example, netscape, kde, gnome, anjuta, acrobat, etc) is that the application creates the directory itself on first run.

      And many applications do figure out what language you speak, and customise themselves to it (yes, via locale).

      And some applications do look at your existing configuration/preferences and use it. (Yes, there should be more.)

      But I wouldn't expect any build/install system to do it - it is a runtime thing, and I would expect the application to do it.

    16. Re:Don't flame the devs by curne · · Score: 1

      "Easy Install". You make that sound so absolute.

      Who should that install process be "easy" for? If I find it easy and you do not, is it easy enough? Should my Mother be able to install it? Even though the complexities of the program are too difficult for her to understand?

      In MPlayer's case, it is my honest opinion, that the compilation process is mostly as easy as it can be given the circumstances. MPlayer combines software modules from countless sources and makes it all play nice inside one little binary. I think the complexity of the situation awards some understanding.

      --
      All interpreted languages are abstractions over Lisp
    17. Re:Don't flame the devs by Hatta · · Score: 1

      You don't have to be a "guru" to install mplayer. Just read the README and you'll be fine. I seriously don't see the problem here. I don't see why people think debian is so hard to install either.

      --
      Give me Classic Slashdot or give me death!
    18. Re:Don't flame the devs by rleibman · · Score: 1

      Perhaps, but of all the applications I've compiled, very few were set in such a way that I could VERY easily create proper RPM packages for them (with the spec file and such), I love those.
      Then there are those that come with almost no instructions, you compile, and don't even come with a 'make install' so I have to guess where the best place is to put binaries that were thrown all over the build directory (e.g. QCAD).
      Open Source developers should make it easy to compile their applications into packages. It doesn't add that much more work to them, and makes it more likely that distros pick them up.

    19. Re:Don't flame the devs by nutshell42 · · Score: 1
      Yes but mplayer has perhaps the most informative configure-script I've ever seen. At the end it prints out what's gonna be installed and what isn't and it's easier to track down missing libraries for mplayer than for any other app I've ever compiled.

      In fact it's easier to compile mplayer than it is to compile any of the competing media players for Linux and it already was that way when Barr wrote his first article bashing mplayer while praising xine which was worthy of the "Emacs-Vi-Flamer's Award" but of little relevance otherwise.

      Are the MPlayer developers assholes? Sometimes
      But that doesn't mean that people writing that the MPlayer devs are assholes can't be assholes too =)

      (After reading that new article it seems to me like both sides have matured since the last round of their mutual bashing)

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    20. Re:Don't flame the devs by fucksl4shd0t · · Score: 1

      Who should that install process be "easy" for? If I find it easy and you do not, is it easy enough? Should my Mother be able to install it? Even though the complexities of the program are too difficult for her to understand?

      I would define an easy install as "You can try to do it without reading the instructions, but don't expect shit to work. You can read the instructions, follow them to the letter, and everything works as expected."

      IN my experience, MPlayer is one of the easiest projects to install from source (Audacity coming in about even, possibly easier). Just because you don't get some fake wannabe installshield installer doesn't mean the installation is hard.

      In MPlayer's case, it is my honest opinion, that the compilation process is mostly as easy as it can be given the circumstances. MPlayer combines software modules from countless sources and makes it all play nice inside one little binary. I think the complexity of the situation awards some understanding.

      I have never failed to successfully install mplayer by reading the instructions. I've even gotten to where I don't read the instructions anymore, I've done it enough times and it doesn't change *that* much. Really, the only bitch I see about MPlayer's install is the same bitch about installing software distributed as source: using the commandline. While I think there can be some improvement, I still don't see any reason installing software has to be graphical. Why is it so unreasonable to expect people to use the command line to install software? That's something you don't do every day. Most people don't even install software every week. Hell, it's been months since I installed a new piece of software on my computer. Installing software is part of administering your computer. It's not something idiot end-users should be doing all the time. It *is* something that requires a little bit of understanding, the kind of understanding that can be gained by reading the instructions. If a user can't be relied on the read the instructions, what can he be relied on to do? Is he going to not read the instructions and then DoS the mailing list with questions that are answered in the instructions? Users all the time complain that the documentation isn't good enough, but do really take the time to read the fucking manual? Or do they just glance through, look at the index/table of contents, and then bitch that it's not good enough?

      That said, documentation is one place MPlayer can use improvement. The answers are in the docs, but they can be pretty hard to find occasionally. Soon I'm going to start working on making svcds again, and I'm going to use MPlayer for it. When I get it down and I know what I'm doing, I'm going to write up my experiences and try to create a guide for idiots to make svcds under Linux. There are several available, but none of them hit the mark quite right. All of them are useful, however.

      --
      Like what I said? You might like my music
    21. Re:Don't flame the devs by fucksl4shd0t · · Score: 1

      Beautiful post, man. The parent outlined a set of impossible to achieve goals, and you showed him how they've already been achieved. Beautiful. And you managed to put your finger on my only serious problem with MPlayer, the fact that it doesn't create ~/.mplayer if it doesn't exist. I think it should also create default config files in that directory, possibly just copying a default from its base, that are well-commented enough that I can hack them without having to read the documentation, but not expect shit to work unless I read the docs.

      --
      Like what I said? You might like my music
    22. Re:Don't flame the devs by Minna+Kirai · · Score: 1

      If not wait for the .deb to become available or subscribe to RedHat network etc.

      It was not long ago that the mplayer developers absolutely forbid anyone from making a binary distribution of their software. The non-GPL license allowed copying as source code ONLY.

      Flames leftover from that time may have valid bases, as they represented a true obstacle towards a non-expert installing the program.

    23. Re:Don't flame the devs by JCholewa · · Score: 1

      > 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.

      Um ... did you actually read what your respondee actually said?

      He said that the user doesn't have to be a guru. Here's the layout he described:

      Developer makes the source code.
      Gurus compile the source for themselves, if they want to.
      OS vendors (Mandrake, Debian, Gentoo, etc..) compile the source and package them nicely.
      User just runs the OS vendors' package installer.

      That way, it works far more nicely for end users than it does, for example, in the win32 world. I, an end user, have to install mplayer? Simply run the Mandrake Installer, search for "mplayer", click its checkbox, click "Install", and it's installed, totally. Alternatively, I type "urpmi mplayer" as root in a terminal window, which is even easier. This beats, hands-down, the Microsoft method of searching, downloading, running, clicking Next, choosing components, choosing install directory, choosing Program Manager group, clicking Next, clicking Finished, rebooting.

      So, pbbblllllt! ;)

      --
      -JC

    24. Re:Don't flame the devs by Qzukk · · Score: 1

      is that the application creates the directory itself on first run.

      The fact is that it does. Well, ok, so it produces an empty config instead of a commented-out one, but mplayer's been capable of creating the directory on the fly for a while now.

      All that it needs is comments in the config, and the language, eyesight, and artistic taste detection routines.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    25. Re:Don't flame the devs by xanadu-xtroot.com · · Score: 1

      emerge mplayer?

      Well... I meant the shiny installer part...

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    26. Re:Don't flame the devs by vadim_t · · Score: 1

      ok, then how about kemerge, kportage, portagemaster?

  14. 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 ?
    1. Re:well, give VLC a try by Anonymous Coward · · Score: 1, Informative

      You are right, But unfortunately VLC crashes very regularly on both linux and windows.

  15. Just a question... by doublebackslash · · Score: 0

    am I the only one who read pre1 as perl spelled rather poorly?

    --
    md5sum /boot/vmlinuz
    d41d8cd98f00b204e9800998ecf8427e /boot/vmlinuz
    1. Re:Just a question... by Anonymous Coward · · Score: 0

      Yes.

  16. Re:FP by Anonymous Coward · · Score: 0

    The school or the grain? Or are you talking about adding type R stickers to things?

  17. The article by Anonymous Coward · · Score: 1, Informative

    Mplayer revisited

    Friday October 03, 2003 - [ 06:00 AM GMT ]
    Topic - Free Software

    - by Joe Barr -
    It's been almost two years since I wrote about Mplayer, an open source movie player for Linux and other platforms. Rereading that story today, I see I was wrong when I predicted that Mplayer's popularity wouldn't last. It continues to rank as the most popular project on freshmeat.net. I recently downloaded pre-release 1 of Mplayer 1.0 to see how much things have changed, if at all, since then. What I found is that while some things have changed, others have not.

    In December of 2001, Mplayer had the rep of playing more codecs than any other movie player for Linux. The list of codecs - both audio and video - that it supports today is quite impressive. And if you add the mplayerplug-in you can leverage Mplayer's repertoire and play the most popular video formats used online in Mozilla, Galeon, Netscape, and maybe Opera, too.

    Mplayer also had the rep of being a tough install and of being even tougher on users - noobs or not - who were having problems with the install. In fact, I used a comment from a frustrated user posting on freshmeat.net for the title of my first article and called it "Mplayer: the project from hell." Let's start with the install issue first and save the other for last.

    Buried deep in the Mplayer documentation - in the section on installation - are a few lines of text that make the process seem completely trivial. They read as follows:

    Features:

    * Decide if you need GUI. If you do, see the GUI section before compiling.
    * If you want to install MEncoder (our great all-purpose encoder), see the MEncoder section.
    * If you have a V4L compatible TV tuner card, and wish to watch/grab and encode movies with MPlayer, read the TV input section.
    * There is a neat OSD Menu support ready to be used. Check the OSD Menu section.

    Then build MPlayer: ./configure make make install

    At this point, MPlayer is ready to use. The $PREFIX/etc/mplayer/codecs.conf file is needed only when you want to change its properties, as the main binary contains an internal copy of it.

    Actually, there is a little more to it than that. And a lot of reading in those docs is highly recommended before you begin. Here's how I installed Mplayer from the pre-1 1.0 source code on Red Hat 9.0 running Ximian Desktop 2.

    I began by going through the list of requirements and making sure that I had not just each app noted, but an acceptable release of each. Except for gcc, that is. I ignored the rants and held steady with gcc-3.2.2-5 shipped by Red Hat.

    Then I was ready to download: I grabbed mplayer-1.0pre1 and the codecs I thought I needed plus a skin or two from the downloads page on the Mplayer site. I created an mplayer directory in my home directory, then used bunzip2 to decompress each of the downloads and then ran tar, which unpacked them and stowed them away in their own directories. For neatness, I created a separate tar directory and moved the tar files themselves there afterwards.

    Then I entered the mplayer-1.0pre1 subdirectory tar had created and ran the configure script with the gui option: ./configure --enable-gui. The script ran, but it complained about not having found a Win32 codecs directory, among a long list (more than 50 items) of other things.

    I had downloaded the Win32 codecs, but they were needed in a directory I didn't have. No problem. I changed to su, created a /usr/local/lib/codecs directory, and moved the win32codecs directory there. Then I ran the configure script again. This time there was no complaint about missing Win32 codecs.

    Then I went through the configure.log and checked every one of the 50 items it had noted as deficient or missing. None of them were critical. Many didn't even apply to me as they were for different platforms completely. So I started make and took a break.

    I came b

    1. 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.
    2. Re:The article by Isaac-Lew · · Score: 1

      I've only been able to get Real Player 9 to work about 25% of the times I've installed it. You can install the Real Player 9 codecs for Real Player 8 (have to hunt for them on Real's site tho).

    3. Re:The article by benwaggoner · · Score: 1

      Yeah, he had it completely wrong.

      RealOne is the new player, RealPlayer was the old player. They both play RealMedia, and they can both use the current set of codecs and all.

      Real is actually doing a nice job of reconnecting to the *NIX community.

  18. 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.

    1. Re:A good GUI by Hatta · · Score: 1

      Mplayers default GUI is none at all. And it's the best ever.

      --
      Give me Classic Slashdot or give me death!
  19. 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.

    1. Re:Who is this doofus? by BrokenHalo · · Score: 1

      You have a point. In the article, Barr seems to indicate that his main problem with the earlier release is that he didn't RTFM. It does seem churlish for him to continue to berate the developers for his own laziness.

    2. Re:Who is this doofus? by Overly+Critical+Guy · · Score: 1

      Clearly, you hate when anything involving Linux is criticized. Tough.

      --
      "Sufferin' succotash."
  20. But its illegal by Anonymous Coward · · Score: 0

    Firstly, this uses Win32 Codecs. Most of the ones I've seen have a clear EULA that forbids use on other operating systems. Secondly, it supports MPEG playback. MPEG is a patented algorithm. They do not have a licence. Thirdly, it was created by reverse engineering. Clearly this is an EULA violation.

    Their responses to criticisms suggests are very similar to street trader's responses when you suggest that their good may be stolen. Rather than being congratulated, these people shopuld be taken away and locked up.

    1. Re:But its illegal by Doomdark · · Score: 1
      Mr. Coward, why did you bother wasting everyone's time by writing that bunch of nonsense? Are you just trying to learn how to troll? If so, have a look at more succesful and entertaining enterpreneurs in that field, before continuing.

      Win32 codecs CAN be used, but are not included by default. If users choose to use them against EULAs (assuming EULAs were found legally binding), its users' choice.

      Secondly, as to MPEG, MPEG is _NOT AN ALGORITHM_. It's a video/movie compression standard; standards can not be patented. There may exist patented algorithms for MPEG encoding/decoding; if so, it's up to patent holders to enforce said patents, if such exists; and then it's up to developers to act accordingly.

      Thirdly, you are ASSUMING mplayer is based on reverse-engineering; and that if it is, there are EULAs associated with parts RE'd; and further, that said EULAs would have any enforceability. There's nothing automatically wrong with RE in the first place, and even more draconian laws (DMCA) have clauses specifically allowing RE when working on interoperability issues.

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
    2. Re:But its illegal by yerricde · · Score: 1

      There may exist patented algorithms for MPEG encoding/decoding

      What if the patent's claims are broad enough to cover any algorithm that results in a conforming bitstream?

      --
      Will I retire or break 10K?
    3. Re:But its illegal by Doomdark · · Score: 1
      What if the patent's claims are broad enough to cover any algorithm that results in a conforming bitstream?

      Personally I would wonder if patent was too broad to have been granted in the first place... but in reality that doesn't seem to matter. :-/

      Now, proving that there can be no algorithm that produces conforming bit stream sounds like a pretty challenging theoretical CS problem to me; even in specific cases such as MPEG encoding. Thus, I'd say that even though one could say that it may be impossible to implement an algorithm that doesn't infringe on certain patent(s), this thinking can only serve as a starting point. After that it has to be proven that certain implementation does indeed infringe on specific patents.

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
  21. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  22. 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'.

    2. Re:Were the copyright violations fixed? (yet?) by AKnightCowboy · · Score: 1
      Debian will also be shipping a stripped, legal version soon.)

      Or just throw this in your sources list in the mean time:
      deb http://marillat.free.fr unstable main
      I would imagine Debian would official throw it into non-free or provide some kind of wrapper script to go out and download the codecs in question.

    3. Re:Were the copyright violations fixed? (yet?) by eviltypeguy · · Score: 1

      Nevermind the fact that in the US and other countries that recognize pure software patents, it's illegal to use GPL'd MP3 based software. Since the GPL allows commercial use of software under it's license, and Fraunhoffer prohibits that without paying them first...

    4. Re:Were the copyright violations fixed? (yet?) by timeOday · · Score: 1

      Woudn't mplayer have to dump dvd support to come completely clean? I'd rather keep it the way it is. Not because I'm a crook, but I'd rather copy DVDs to my laptop's harddrive and use the drive bay to hold an extra battery when I fly... so shoot me.

    5. Re:Were the copyright violations fixed? (yet?) by Goodbyte · · Score: 1

      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.)

      This is sometimes worse than not shipping at all. I feel sorry for the developers of mplayer who get tons of mail from users complaining about "mplayer can't play X" when all that is needed is for the user to build from source himself

    6. Re:Were the copyright violations fixed? (yet?) by Abcd1234 · · Score: 1

      Woudn't mplayer have to dump dvd support to come completely clean?

      Err... why? Mplayer doesn't contain any proprietary code for decoding DVDs. It relies on an external library (libcss) to provide this functionality. So, no DVD support is not a problem.

    7. Re:Were the copyright violations fixed? (yet?) by Dr.Dubious+DDQ · · Score: 1

      "DivX Copyrights"? I don't recall there being any code from "DivX" in MPlayer at all, though there is still support for the old "divx4linux" codecs (deprecated in favor of Xvid and/or ffmpeg's libavcodec support for mpeg4.)

      Again - this isn't an 'end-user' program. Use Xine - there are plenty of pre-built packages for it.

      And, seriously, if you NEED Mplayer to play something, the ./configure script that comes with the source code is amazingly smart compared to most. No options needed, and './configure' figures out the necessary optimizations and available codecs on its own.

  23. 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!
  24. Re:Xine by Anonymous Coward · · Score: 0

    I don't understand the people that love xine. It has one of the worst interfaces under the sun. Sure it looks cool, but horribly unfunctional. MPlayers interface actually *works*. Even when using the Xine skin.

  25. Well it is Open Source.... by kikensei · · Score: 1

    maybe its better to pitch in and help write the documentation for the project than to lambaste the devs for poor documentation. Regardless, its available precompiled on nearly any distro. Worked fine on Slackware 9.1 by going to linuxpackages.net (the home of all slack packages) downloading, and rning instllpkg mplayerx...

    1. Re:Well it is Open Source.... by casings · · Score: 1

      compiling it for slack 9.1 worked well for me.

      no problems and have every codec i could want... good riddance wimp 6-9!

  26. Windows version? Huh? by xNullx · · Score: 1

    Did anyone else ever notice the "UNUSABLE FOR WINDOWS!" message next to the win32codecs in the downloads section? That seems to imply mplayer actually has a windows version, probably confusing for some people.

    1. Re:Windows version? Huh? by Anonymous Coward · · Score: 0

      No, that 'UNUSABLE FOR WINDOWS' applies to binary windows codecs, not to mplayer. When installing windows codecs, you have to put stuff into registry and this package doesn't do that.

      MPlayer by itself builds nice with mingw. It is kick-ass windows player...

    2. 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 :)

  27. 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).......

    1. Re:mPlayer powers Xbox Media Player and Center by Intocabile · · Score: 1

      Yeah but remember when they got realy mad because the source wasn't available. The program was still in its infancy and they totally overreacted.

      XBMC will be pretty darn good when it reaches the polish XBMP 2.4 is at now. They are reninventing the wheel with this one but XBMP was full of bloat and this complete rewrite will allow them to make the program faster and much more modular.

  28. Win32 needed by Apreche · · Score: 1

    mplayer is awesome. It plays anything and everything. I would love nothing more than to have a version of mplayer for windows. I've heard of people running it under cygwin, but I haven't been able to make it compile. I got it under gentoo, and it rules. Go mplayer go!

    --
    The GeekNights podcast is going strong. Listen!
    1. Re:Win32 needed by Anonymous Coward · · Score: 0

      I managed to build it with mingw. It rocks!

    2. Re:Win32 needed by Anonymous Coward · · Score: 1, Informative

      here we go again you can download mplayer for windows binaries
      www1.mplayerhq.hu/MPlayer/releases/win32 -beta/

      and yes they do rock thats the only player im using in windows

    3. Re:Win32 needed by rafael2k · · Score: 1

      MPlayer works nicelly with win32.
      I compiled it with CYGWIN using -O3 optimization
      ( -O4 don't work)

    4. Re:Win32 needed by Anonymous Coward · · Score: 0

      There definately is a windows-version. I use it.
      Works great.

      It once was announced on the mplayer page but since then, it seems to be burried somewhere.

      Some posts above someone mentioned this link:

      www.mplayerhq.hu/MPlayer/releases/win32-beta/

      Not sure if it is the correct one though.

  29. What homework? by Omicron32 · · Score: 1

    If you want to compile software, be prepared to do your homework.

    What homework?

    emerge mplayer

    ??

    1. Re:What homework? by BrokenHalo · · Score: 1
      Ah, a Gentoo troll.

      I often wonder what this is all about. On the one hand I see an argument for a distribution that has everything compiled from source (of which I would thoroughly approve if I didn't have to maintain computers of more than one architecture). And on the other hand, I see numerous posts from individuals who don't want to get their hands dirty and do their own compiling.

      This trite emerge stinkyfinger that we see trotted out in this type of discussion is no more enlightened than rpm -U stinkyfinger.

      And no, I'm not a RedHat zealot (I prefer Slackware).

  30. difficult my arse. by K. · · Score: 1

    Funnily enough I installed 1.0prewhatever last night.

    I downloaded the source, typed ./configure
    make
    su -c "make install"

    And I was done.
    (I didn't bother downloading any skins or anything posh like that. CLIs are good enough for the likes of me.)

    Mind you, that was on Slackware 9. But even so, I think yon reviewer may be taking the piss a bit. Why did he expect a CVS build to work as cleanly as an official one. Isn't the point of a CVS version being available so people can see and help with a work in progress>

    --
    -- Proud descendant of semi-nomadic cattle-herders.
    1. Re:difficult my arse. by sghbirch · · Score: 1
      I also downloaded the MPlayer 1.0pre1 source from their site, did configure/make and was up and running in a few minutes with no problems at all.

      My computer is running Debian 3.0 (woody) and runs MPlayer like a dream.

      I just wish the Debian folks would get together with the MPlayer developers and agree on a suitable package that satisfies the Debian Social Contract but does not alienate the MPlayer folks. It would be a terrible shame if MPlayer does not make it into the next release of Debian.

      BTW Xine is in debian.

    2. Re:difficult my arse. by Hatta · · Score: 1

      What's the big deal if it doesn't? That's not stopping anyone from grabbing the source and building it themselves, which is what they should be doing. And no, it's really not as hard as people think it is.

      --
      Give me Classic Slashdot or give me death!
    3. 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.
    4. Re:difficult my arse. by i_am_nitrogen · · Score: 1

      I really love mplayer because it is fast and responsive, delivers a much better quality than any windows player I used

      While the still image quality of all the Linux players is much better, the A/V sync code seems to be very poor, especially for playing back 24p DVD's with S/PDIF audio output. Smooth pans are anything but smooth. It almost looks like they're trying to sync to 30fps, and just tossing out frames from the 24fps at about the right place, rather than displaying them at a continuous 24fps. Mplayer's -autosync 120 option helps with that quite a bit, but there are still noticable skips now and then. Does anybody know how to deal with these problems in Xine, Ogle, or Mplayer?

  31. 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.

    --

  32. Installation by AdamHaun · · Score: 1

    Gentoo makes the installation completely painless, although configuration can sometimes be a pain in the ass. I'm happier editing config files than dealing with make, though.

    With all the complains about the GUI setup, you'd think there'd be more people using the completely painless command line version:

    mplayer
    (file magically works perfectly)

    I watch my videos in fullscreen anyway, so GUIs just get in the way. The only thing they seem to add is random seek, which is a useful feature, but not what people seem to be complaining about.

    --
    Visit the
  33. doh by K. · · Score: 1

    Forgot the "and then I copied the codecs into the appropriate directory" stage, but that wasn't exactly rocket science.

    --
    -- Proud descendant of semi-nomadic cattle-herders.
  34. Re:why by Anonymous Coward · · Score: 0

    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.

    But I thought Linux couldn't get viruses

    *rimshot*

  35. 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.
    1. Re:mplayer's option syntax annoys me by vesamies · · Score: 1

      Maybe they don't want to have an option for every character in alphabet. If so the extra dash is just extra typing. It's hard to debate what is ugly, but the double-dash is just a gnuism and no more standard than the single-dash.

    2. Re:mplayer's option syntax annoys me by Anonymous Coward · · Score: 0

      No, the single dash followed by a word violates the getopt standard used by most POSIX programs, while a double dash followed by a word doesn't. The double dash is a GNUism only in the sense that GNU used to use a single dash, but changed when it was pointed out what the standards say.

    3. Re:mplayer's option syntax annoys me by amoe · · Score: 1
      Maybe they don't want to have an option for every character in alphabet. If so the extra dash is just extra typing.

      All real geeks shorten all options to the point where they're one character. :-)

      It's hard to debate what is ugly

      True. But if anything, the double dash is more intuitive to the untrained eye, because of its use in quotation attribution and such. Prefixing things with a single minus sign makes no sense to people unraised on Unix.

      --
      You look beautiful! Incidentally, my favourite artist is Picasso.
    4. Re:mplayer's option syntax annoys me by Anonymous Coward · · Score: 0

      How the FUCK did this bullshit get modded to +4, Interesting?! Funny how a "perl monk" only likes options in a format easily supported by that disgusting kludge of a language.

    5. Re:mplayer's option syntax annoys me by Anonymous Coward · · Score: 0

      pwned.

  36. Speaking of open source projects... by The_Sock · · Score: 1

    I'm starting a project on source forge, and can use all the help I can get.. It's called "amount of time it takes for half of a radioactive substances atoms to decay 2"

    We've already got a lot of good source code up but we can use some help... especially with artwork as we have none except some scattered images we found, er, created.

    Look us up on http://www.sourceforge.net.

    Thanks in advance.

    The AOTITFHOARSATD 2 Team.

    --
    For a good time call www.sawkie.com
  37. Why's it always the assholes who pass the test? by PapaZit · · Score: 1

    It seems that a lot of the innovative "best of breed" open source projects are run by utter assholes: Mplayer, Qmail, OpenBSD, etc.

    I suspect that it's not coincidence. Building concensus and playing well with others means making compromises. Compromises are the enemy of innovation. It's the people who take their ball and go home who crack the mold. They go off in "unprofitable" directions. Most of them labor in obscurity. A few of them turn out to be right and manage to produce something useful.

    --
    Forward, retransmit, or republish anything I say here. Just don't misquote me.
    1. Re:Why's it always the assholes who pass the test? by Anonymous Coward · · Score: 0

      Simply because they are doing what they are good at, coding? And that answering inane support questions take time away from what they are good at?

      I would rather someone work on getting things right than spend time making it easy to install. Someone else can do the install.

      Having a crusty exterior will keep people away. Sounds like a good strategy for getting coding done.

      Derek

  38. Re:Here we go again... by g00set · · Score: 1

    Agreed...

    From the README:

    Unpack the codecs archives and put the contents in a directory where MPlayer will find them. The default directory is /usr/local/lib/codecs/ (it used to be /usr/local/lib/win32 in the past, this also works) but you can change that to something else by using the '--with-codecsdir=DIR' option when you run './configure'.


    And the author who refuses to read the README:

    Then I was ready to download: I grabbed mplayer-1.0pre1 and the codecs I thought I needed plus a skin or two from the downloads page on the Mplayer site. I created an mplayer directory in my home directory, then used bunzip2 to decompress each of the downloads and then ran tar, which unpacked them and stowed them away in their own directories. For neatness, I created a separate tar directory and moved the tar files themselves there afterwards.

    Then I entered the mplayer-1.0pre1 subdirectory tar had created and ran the configure script with the gui option: ./configure --enable-gui. The script ran, but it complained about not having found a Win32 codecs directory, among a long list (more than 50 items) of other things.

    I had downloaded the Win32 codecs, but they were needed in a directory I didn't have. No problem. I changed to su, created a /usr/local/lib/codecs directory, and moved the win32codecs directory there. Then I ran the configure script again. This time there was no complaint about missing Win32 codecs.
    --
    ... and furthermore ... I don't like your trousers.
  39. 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.
  40. Re:Xine by Anonymous Coward · · Score: 0

    Bwaahaahaa. MPlayer trolls, now I've seen everything.

  41. Can't install? by koi88 · · Score: 1

    Did you download the binary version for Mac OS X? It's available here: http://mplayerosx.sourceforge.net/
    I coudn't find information about it now, but it probably requires OS X 10.2.
    I love this program, but I also use VLC, which you can get from videolan.org. Most videos look better in mplayer, but some (esp. with 2 audio tracks, i.e. two languages) play only in VLC.
    I hope I could help you...?

    --

    I don't need a signature.
  42. Duh... by Roadkills-R-Us · · Score: 1

    Maybe because that's supposed to be the closest thing to what the official 1.0 release will be? You know, the thing that's for real users, not developers, hackers, experimenters, and folks with way too much time on their hands? People who just want to see a video, not solve open source puzzles?

  43. Off to jail you go, criminal. by Anonymous Coward · · Score: 0

    bubba is waiting for you!

    1. Re:Off to jail you go, criminal. by The_Sock · · Score: 1

      bubba is waiting for you!

      Where hopefully he'll teach me when to use an apostrophe correctly. I hate being a grammer nazi on myself.. but damn.

      Look for us under our new name..

      amount of time it takes for half of a radioactive substance's atoms to decay 2

      I should mention.. It's a game. A first person shooter. Just so you know.

      --
      For a good time call www.sawkie.com
  44. Re:Spot off! by TheAcousticMotrbiker · · Score: 1

    Oddly enough I've never tried compiling GnuMACh, but mplayer compiles these days with a straight ./configure; gmake; su -;gmake install

    The tricky part seems to be to ensure you have the codecs mplayer needs, and have them in a palce where mplayer can find them (/usr/lib/win32) Oh, and you need to have a version of gcc that is know to work with mplayer.

  45. 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.

    1. Re:Illegal distribution of Win32 codecs by gid · · Score: 1

      The Mplayer team has no respect for copyright law and continues to violate the law.

      The way I see it, that's ok. Most of the team is from Hungray I believe, probably where they don't have software patents, so why should they care when they just want to make the best player out there. Without mplayer other projects wouldn't be where they are today. They might not have done all the greatest code breaking etc to play certain formats, but they were the first to encorporate them, allowing the playback of Sorenson encoded quicktime files, real audio/video file, vp3, etc. I think Xine allows they playback of these files too, but it's uses MPlayer's win32 codecs that they distribute!

      It would be nice if someone would get ahold of the MPlayer code now and fork it. Splitting off the offending code into modules, so countries with software patents can distibute binaries. I'd do it myself, but I'm too busy rewriting Linux.

    2. Re:Illegal distribution of Win32 codecs by Anonymous Coward · · Score: 0

      >The way I see it, that's ok.

      The way I see it, you don't understand the difference between copyright law and patent law.

      >Most of the team is from Hungray

      Hungary is a signatory to the Berne convention and the WIPO copyright treaty.

      http://www.wipo.int/treaties/ip/index.html

    3. Re:Illegal distribution of Win32 codecs by gid · · Score: 1

      s/software patents/to abide by certain copyrights/

      It's all legal mumbo jumbo anyway that I really don't very much care about, nor do I have any real interest in doing so.

    4. Re:Illegal distribution of Win32 codecs by Ella+the+Cat · · Score: 1

      The parent post is word for word identical with a post appearing below the newsforge article, which has received many replies. Anyone interested in the parent might find the newsforge replies interesting too. I'm intrigued by the tone it adopts, terse and to the point, formal. Curious.

  46. Re:MPlayer ROCKS! by dasmegabyte · · Score: 1

    Don't tell disco granny!

    "Dumb Dumb?"

    That's my club name.

    --
    Hey freaks: now you're ju
  47. simple GUI by lscoughlin · · Score: 1

    I crave a simple gui. The skins for mplayer suck.
    i want 1 window. 1. Does any one remember the zen of windows media player 7? 1 window, with unobtrusive and simple controls. No nasty borders, no ugly hard to use skins, no craptacular multiple window where is the widget to make it stop hunting garbage; no how the fuck to i open another file from here? confusion.

    Sigh.

    -T

    --
    Old truckers never die, they just get a new peterbilt
    1. Re:simple GUI by moyix · · Score: 1

      Maybe you want this skin?

    2. Re:simple GUI by dbs_flac · · Score: 1

      I totally agree with you. It took me ages but I found two that I like - gxine and kaffeine, do a google and you'll find them. They both do want you want.

  48. 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.

    1. Re:Barr and bias by wampus · · Score: 1

      Building mplayer isn't so bad... i just emerge it and away it goes... a few minutes later it spits out a binary. Only problem is that mplayer is one of a few apps that ignores my CFLAGS, but I understand that it doesn't like heavy optimization.

      Of course, n00bs aren't using gentoo, but I doubt it would be hard to roll a src RPM for whatever distro's use those now.

    2. Re:Barr and bias by fucksl4shd0t · · Score: 1

      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.

      All true, however, I don't think it's unreasonable to shoot for a general-purpose way to make ./configure && make && make install easier for boobs. Er, newbies. When that is done, building MPlayer will be a breeze. Just point and click what you want to enable or disable, and the app will tell you what's missing. Some work on the configure script for mplayer might help some, I haven't look too closely at it to be sure, though.

      Point is, I don't think it's unreasonable that MPlayer shoot for being easy to use by fools and mothers alike. I don't think they have, so far, and I don't know if they will, but I see no reason MPlayer should stay "for advanced users only". That's just where it is *now*.

      "You're looking at now. Everything you see there is happening now."

      "What happened to then?"

      etc.

      --
      Like what I said? You might like my music
    3. Re:Barr and bias by halfelven · · Score: 1

      Mplayer is not a particularly great choice for non-techies


      Well, as long as you install the GUI, it should be quite usable by non-techies as well.

      mplayer [...] is faster than anything else in existence


      Actually, if you look at objective reports, you'll see that reality is a bit different. Quite a few people (non-biased observers) report that mplayer is by no means the fastest player available. E.G. on my system (AthlonXP/1800, GeForce2) actually it's Xine which has the lowest CPU usage almost any time.

      Also, the "ours is the fastest player ever" is the most useless bit of the mplayer propaganda. If your CPU usage is below 5% no matter what's the player, who cares what's the "fastest" player. In my case, mplayer has a slightly higher CPU usage (and i did follow the build instructions to the letter) but that doesn't prevent me from using it every now and then (but in most cases i use Xine, especially when it comes to DVDs, since it has a far better DVD support - it can handle DVD menus properly).

      mplayer [...] has support for just about every interface and codec under the sun


      We mustn't forget that Xine plays all those formats as well. It's only a matter of installing the right codecs (Win32, Real, etc.).
    4. Re:Barr and bias by Anonymous Coward · · Score: 0
      Well, as long as you install the GUI, it should be quite usable by non-techies as well.

      What? You can install a GUI to build it?

  49. The easy way: by Anonymous Coward · · Score: 0

    emerge mplayer. Done =]

  50. 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
  51. Why make it hard? by macemoneta · · Score: 1
    yum install mplayer

    That's all it takes. I installed yum from FreshRPMs, and no configuration was required.

    If you issue the following two commands:

    1. chkconfig yum on
    2. service yum start

    then any software you have installed will be kept up-to-date automatically, every night. It doesn't have to be hard to use Linux. Why do people insist on making it appear harder than it is? To frighten noobies?

    --

    Can You Say Linux? I Knew That You Could.

  52. Can we call this a review? by smartdreamer · · Score: 1, Troll
    Where is the review?!? Did I miss something or this "5 years Linux user" just wrote some text to prove he doesn't know how to install a software?

    Come on, don't write something like this... please! If you have nothing constructive to say, shut up.
    To be listened by several brings you responsabilities.

    1. Re:Can we call this a review? by Dr.Dubious+DDQ · · Score: 1

      Not sure why this got marked 'troll' - the poster has a point.

      Okay, maybe the way it was said was 'insensitive', but still...

      Joe Barr's article really DOES boil down, roughly, to "yup, MPlayer sure does handle a wide variety of file formats, but the developers are poopyheads for not being user-friendly and having a nice GUI and for making me compile from sources, and they're mean to me."

      I have to admit, I'd be pretty irritated too if, after all the work to make the ./configure script as "smart" and automated as it is, someone came along and complained that they had to click more than once to do the install...especially when so many of those people pop onto the mailing list and start making demands contrary to the goals of the project. ("you MUST make a better GUI","You'll NEVER be the most popular player if you don't change [whatever].", etc.)

      (Why use MPlayer if it's too hard to install? Xine is a fine project, and unlike MPlayer which is designed for 'power users' rather than 'end users', Xine's goals are explicitly aligned with making things easy for end-users....)

  53. Warning by 0x0d0a · · Score: 1

    This build does not contain all available options in mplayer. There's no mga or xmga support (which I use), for instance. If you want the goodies, you have to do the build yourself.

  54. Ok, I checked, MPlayer does have problems by ciaran_o_riordan · · Score: 1

    If it infringes a patent that is not licensed for zero-cost use, it cannot be distributed under the GPL.

    GPL, section 7:
    "If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all."

    I asked a question and gave the basis for my question. The ffmpeg library does infringe a patent. The patent has not been enforced for decoding before, but that doesn't mean it will not be enforced in the future (say, when an IP firm buys the patent), and it has been enforced for encoding, so a programmer that receives this code cannot do what she likes with it.

    1. Re:Ok, I checked, MPlayer does have problems by Anonymous Coward · · Score: 0

      As parent stated, in some countries, distributing the program violates patents. In other countries, there's no such thing as software patents so ffmpeg is perfectly justified in being GPLed. The issue comes when ffmpeg is sent to people under the jurisdiction of a patent for which the person sending doesn't have a right to grant patent interoperability. Just like it's perfectly legal in the US now to distribute GPLed GIF source code, but we can't distribute it to other countries that still have the patent.

    2. Re:Ok, I checked, MPlayer does have problems by juhaz · · Score: 1

      Good thing that not all of us live in the promised land of nutcase patents.

      MPlayer doesn't have problems, it's not developped in the US. People who distribute where it's encumbered may have problems, which is why it and lots of other software in same position (mp3 players) is absent from redhat for example.

    3. Re:Ok, I checked, MPlayer does have problems by yerricde · · Score: 1

      I hope you're not implying a suggestion that people emigrate from countries whose corrupt legislators have allowed national patent offices to grant overly-broad patents on algorithmic inventions.

      --
      Will I retire or break 10K?
  55. gstreamer by hey · · Score: 1

    I prefer the idea of gstreamer ...
    you define a graph to play your content. You can even describe the graph on the command line ;-).
    mplayer uses Windows DLLs - yuck.
    Just one problem ... when I tried gstreamer and mplayer last month (on RedHat 9) mplayer worked much better. For example, gstreamer claimed to play Quicktime but didn't. I know I was in trouble when gst-launch-ext (sp?) -- the script that plays files based on their extensions -- said .mov was invalid!

  56. 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

  57. FreeBSD's ports by Anonymous Coward · · Score: 0

    Difficult installation? cd /usr/ports/multimedia/mplayer && make install clean and you're done. What's so hard about that? </gloat>

  58. Re:Here we go again... by 0x0d0a · · Score: 1

    The script ran, but it complained about not having found a Win32 codecs directory, among a long list (more than 50 items) of other things.

    This has a bit of Barr bias. Nothing's "wrong" -- Barr's system just doesn't have things like Realplayer installed, so mplayer is saying "I won't be able to play .rm files because you don't have realplayer installed." Of course, clarifying that would weaken his point that his onging grudge war with A'rpi (ex-mplayer lead, who is equally responsible for the A'rpi-Barr flamewar).

  59. GUI Look by Alan · · Score: 1

    Sadly both xine and mplayer have horrible GUIs by default. Totem on the other hand, which uses the xine libs for it's video playback, has a nice clean GUI that is actually usable. Personally I use mplayer from the command line out of habit, but the lack of a gui that doesn't suck would be a nice option.... I think even jwz ranted about this some time back /me puts on mod-proof undies

  60. Re:Here we go again... by 0x0d0a · · Score: 1

    It does not expect you to KNOW what codecs you want to use and already have them downloaded.

    Try playing DivX when you lack support, mate. And at least with Mplayer, you'll get a vaguely helpful message -- not with Windows Media Player.

  61. Re:why by Anonymous Coward · · Score: 0

    Yup. WMP9 is to Windows what emacs is to everything. Pretty soon, there'll be WMP mathematical simulation packages and WMP embedded systems. After all, music isn't worth listening to unless the computer has to spend clock cycles calculating colored lines to its tune.

  62. What's best for DVDs? by Malc · · Score: 1

    What's the best way to watch DVDs? Do any distros even support this out of the box? Presumably they would have ship with DeCSS. I tried to get playback working under Mandrake 9.1 the other day, and after several frustrating hours I ended up with something that couldn't even match Windows 4 years ago. It requires adding in the PLF sources, but the latest version of the Xine player didn't seem to have all the packages available; VLC worked, but kept dying silently (core dump?); MPlayer seemed to require too much command line, and didn't seem to support DVD Menus anyway. I didn't get as far as trying Ogle (or whatever it's called) as I was too annoyed by then.

    Oh what's going on with Livid? Their web page doesn't seem to have seen much activity in a couple of years. And finally, I was thinking of dumping Mandrake and switching to Debian Unstable on my desktop... anybody know how things like MPlayer square up there?

    1. Re:What's best for DVDs? by sik0fewl · · Score: 1

      I don't remember the exact packages that I needed to get dvd working in xine, but this should help. If you install all these packages (or their equivalents) and their dependencies I think you should be okay.

      I think only mandrake rpms have the xine-* packages, other package systems might just all be combined into the xine package. (I don't recall exactly, but I remember it for some reason)

      $ rpm -qa | egrep "css|dvd|xine"
      libxine1-1-0.beta4.1mdk
      libcss-0. 1.0-5
      xine-plugins-1-0.beta4.1mdk
      libdvdread3-0. 9.4-1mdk
      libdvdread2-0.9.3-4mdk
      libdvdcss-1.2.6- fr1
      libdvdread3-devel-0.9.4-1mdk
      libdvdcss-devel -1.2.6-fr1
      xine-ui-0.9.18-1mdk
      xine-dvdnav-1-0.b eta4.1mdk
      --
      I remember when legal used to mean lawful, now it means some kind of loophole. - Leo Kessler
    2. Re:What's best for DVDs? by Patik · · Score: 1

      VLC is great on any platform.

    3. 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.

  63. boom-chicka? by Anonymous Coward · · Score: 0

    Maybe you're thinking of funk or something. Techno just goes boom boom boom boom.

  64. Hard to install? by StormReaver · · Score: 1

    For Mandrake 9.1, it was a simple matter of "urpmi mplayer" to get the basic MPlayer installed. Finding the Windows DLLs so MPlayer could play Sorenson QuickTime files (and presumably others) was harder, but doable through Google. Installing them so MPlayer could use them was reasonably easy (create /usr/lib/win32 and copy the DLLs there), though adding an import function to the GUI that would automatically extract and copy the files would have been better for the less technical users .

    For those of us who got tired of doing so many source installs which required fighting with the install process, waiting for your distributor to do the integration work for you makes even something as notoriously difficult to install as MPlayer nearly painless.

  65. Re:Install is easy! by Anonymous Coward · · Score: 0

    For cheezor's sake, why?

    That would bend the RPMs over and force them to take it anally. I mean, serriously. I can't imagine the extent that RPM HELL would be enflamed by that.

    Get over it, use Debian, eh?!

  66. 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]
  67. 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
    1. Re:and this bullshit too: by Overly+Critical+Guy · · Score: 1, Insightful

      And people wonder why this shit isn't mainstream yet?

      Honestly. I'm not trolling...

      --
      "Sufferin' succotash."
    2. Re:and this bullshit too: by Dr.Dubious+DDQ · · Score: 1
      And filters for -vop are applied IN REVERSE ORDER.

      Yes, but -vop is deprecated in favor of -vf, which is NOT applied in reverse order. I'm not sure what's so hellish about -fps and -ofps (-fps means "play at this framerate", -ofps means "correct TO this framerate, dropping or copying frames as necessary". Very handy when I mis-type the tv capture line and end up capturing at the wrong framerate...

      While I tend to agree that the syntax for some of the options is unusual (especially the complicated ones that are really sets of parameters to pass to OTHER 'programs', e.g. libavcodec), I'm willing to put up with it. It IS confusing and a pain in the butt sometimes, there's no denying that, but I've been able to get a huge variety of things to work with it, and in my admittedly frequent trips through the documentation to try to figure out new features, I can see a lot more there that I've hardly touched. MPlayer reminds me a lot of Regular Expressions in that respect - not necessarily intuitive to learn, but very powerful if you're willing to deal with it.

      I do have to agree with you on the DVD syntax, but I think that's partly due to the ongoing shift in syntax. Originally, as I recall, the syntax was "-dvd", much as TV capture was "-tv on[:other-features=whatever:etc]". (tv capture is now also tv:// instead). Hopefully the new syntax will be expanded and work as you suggest later [dvd://title/chapter] - it would be consistent with other URLs [mms://whatever/whatever.wmv or http://some.host.net/quicktimevideo.mov or whatever] then.

      What Joe Barr and company seem to refuse to acknowledge is that MPlayer is NOT really written for 'normal end-users'. At all. Just as it seems, it really WAS written for 'nerds' and a conscious decision to forgo 'user-friendliness' in favor of functionality. Joe Barr and company refuse to accept this, and complain as though the developers are out to "get" end-users, and trying to treat the developers as though they are paid technical support, or a commercial software company that should be desperate to please end-users. I tend to sympathise with the developers on this - they've put out an amazingly functional though difficult to use program, and made it available for 'anyone that wants to use it', and their "reward", for the most part, is people popping onto the mailling lists regularly to DEMAND that they stop working on what they're doing and make pretty GUI interfaces or change the commands or explain how to do things (that are already explained in the surprisingly-complete-for-an-open-source-project online documentation) and "they'd better change their ways if they want to 'take over' the media player 'market'."....

      I see how regularly that comes up in the mailing lists, and fully understand the fact that the developers have run out of patience for dealing with it...

      It's like having people complain that GCC is too hard to use because C is complicated, and why can't GCC have a nice GUI and compile in some form of drag-n-drop LOGO instead...or popping onto the Perl-developers mailing list to yell at the developers because Perl is hard to read sometimes and why can't they be like Python instead [when Python itself is already available to the complainers to use...]

      Anyone who complains that MPlayer is too hard to compile and install is NOT the target 'market' for MPlayer. Seriously. Those people should be using Xine or similar programs, which ARE written for the 'end-user' "market" (and Xine is quite nice - and 'cross-pollinates' features with ffmpeg and MPlayer, so they all will tend to support much of the same set of codecs at time goes on.).

      I, for one, WELCOME our MPlayer developer overl....wait, did I just type that? Damn. I've been reading too much slashdot....

    3. Re:and this bullshit too: by amoe · · Score: 1
      And people wonder why this shit isn't mainstream yet?

      Joe User isn't expected to use the command line. Anyway, even if he does, the syntax to do simple things is simple: mplayer -dvd 1 to play a DVD.

      --
      You look beautiful! Incidentally, my favourite artist is Picasso.
    4. Re:and this bullshit too: by Anonymous Coward · · Score: 0

      The correct syntax is (as of mplayer 0.90):

      mplayer dvd://1

      Of course you will need to add -cache. If you don't add -ao you won't get no stinkin audio.

      The ironic part was that if you wanted a gui you still had to specify all those options and "-gui" on the command line as well.

  68. OS X by jafac · · Score: 1

    On OS X MPlayer is about the only media player that will balls-out play just anything. Bottom line, this is what it's all about. That's the killer-app of video as far as I'm concerned. The program that does not make it the user's concern what format, what encoding method, or who copyrighted what. Don't hassle me with technical crap. When I want that, I'll open a term window. But when I'm going throug video clips, I certainly don't need that kind of hassle. (often, my right hand is covered with lotion at this point :)

    However, there are a couple of clips I've tried playing that'll hang MPlayer in a very ugly way, often taking Finder with it, occasionally taking the whole system along for the ride. (especially if that clip was on a CD). Granted, these files are almost certainly corrupted in some way. And every one of them that hangs MPlayer won't even open for other media players (quicktime, WiMP, VideoLan).

    --

    These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  69. 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.
  70. Re:Here we go again... by bperkins · · Score: 1

    RTFM is not a valid complaint.

    I'm sorry, you lost me right here. When installing code of dubious legality downloaded from Hungary with a miriad of stolen codecs and swiped protocols that is under furious development from a bunch of cankankerous weirdos, RTFM is certainly a valid complaint.

    mplayer is not, and probably never be production quality software. Since (insert distro here) will never package it, it will always suck.

    You don't have to RTFM for Windows, but since ther e is no TFM, or source for that matter, if things are screwed up, it's damn hard to fix it.

    So my response to you: Get your grubby click and drool mits off my operating system!

  71. I don't believe you by Ender+Ryan · · Score: 1
    If you can successfully get GNU/Hurd from CVS up and running, installing MPlayer should be easy as pie.

    You only need a few things. MPlayer source. Win32 libs. Put win32 libs in /usr/lib/win32, extract MPlayer source, ./configure && make && make install. There are a couple extra libs you can compile mplayer against but they aren't necessary.

    It had some problems on old systems, pre gcc-2.95.3, other than that I have never seen any problems getting it up and running on any distro on any hardware.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  72. Re:Install is easy! by Anonymous Coward · · Score: 0

    What's the matter Debian troll? Scared because the only reason to use Debian is now available on the better linux distro?

    Pfft. Get a life dickwad nobody cares about your lame distro. You and the other 3 people who use Debian can go have a circle jerk now.

  73. 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!
  74. installation of mplayer by penguin7of9 · · Score: 1
    Reading through the comments on freshmeat.net, it seems that the Mplayer installation still draws the most flamage.

    End-users shouldn't have to compile mplayer. That's what we have Linux distributions for. They package things so that software that can be installed with a single command (three commands if you are not set up for it):
    # echo "deb http://marillat.free.fr/ unstable main" >> /etc/apt/sources.list
    # apt-get update
    # apt-get install mplayer
    Mplayer necessarily has lots of dependencies, and you can't blame its developers for that.

    Of course, mplayer doesn't just ship with many Linux distributions out of the box in the first place (or is crippled) probably because of software patents and DCMA concerns. So, blame that this is even an issue on the USPTO and RIAA.
  75. Re:why by Anonymous Coward · · Score: 0

    HAHAHAHAlolololololol that iz teh fnny1111!!!!!!!1111

  76. Re:Here we go again... by Goodbyte · · Score: 1

    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."

    Have you ever tried to install a windows program that is distributed as a source package? Before switching to Linux I tried several and couldn't make a single one of them work (and I did spend some time fixing the compliation errors by reading through and correcting code).

    I do not claim MPlayer is easy to build by the average user, but once you have a working configuration, it is quite easy to upgrade. Instead try to install sun-java from source, that is a project which could be much easier to build, but you never hear any complaints there.

  77. Biggest pet peeve w/MPlayer by ndogg · · Score: 1

    My biggest pet peeve about MPlayer is the fact that it lets audio and video go out of sync, and then proceeds to complain that the machine is too slow, when I know many times that such is not true. Synching audio and video under Linux is not impossible because all aRTs players (Noatun, Kaboodle, etc.) do this, and they do so at full-screen, and they handle files that MPlayer complains about. aRTs may not have as much support for codecs as MPlayer does, but the ones that it can play, it plays very well, much better than MPlayer ever does.

    --
    // file: mice.h
    #include "frickin_lasers.h"
    1. Re:Biggest pet peeve w/MPlayer by vesamies · · Score: 1

      I've seen this too, in that case the -framedrop option might help. Also check the CPU is not running other stuff in the background ;)

    2. Re:Biggest pet peeve w/MPlayer by ndogg · · Score: 1

      That doesn't always work. In spite of the CPU doing other things, aRTs players still play the files just fine, unlike MPlayer.

      --
      // file: mice.h
      #include "frickin_lasers.h"
  78. urpmi mplayer by Anonymous Coward · · Score: 0

    urpmi mplayer mplayer-gui w32codecs

    gmplayer fantastic pr0n vid

  79. Re:Xine by norite · · Score: 1
    I tried the version of Xine that came with my SuSE 7.3 distro. it was crap - It completely locked up the computer, and I had to literally pull the plug out of the PSU to turn it off! (no i don't have it on a network, so i could not rlogin & kill the process) All that I can think of is that there's a severe clash with the video card - Diamond Stealth IIIS540 (savage chipset)

    There's no way I'll try Xine ever again if that's the result!! Then again, perhaps this chipset is supported now...

    --
    -- Fuck Beta
  80. Windows Port (was Re:Windows version? Huh?) by rufus+t+firefly · · Score: 1
    Did anyone else ever notice the "UNUSABLE FOR WINDOWS!" message next to the win32codecs in the downloads section? That seems to imply mplayer actually has a windows version, probably confusing for some people.

    That's because there *is* a Windows port of it, and it's located on their server. Try ftp://ftp.mplayerhq.hu/MPlayer/releases/win32-beta .

    --
    "He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
  81. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  82. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  83. Don't get me wrong... by pr0ntab · · Score: 1

    I'm the hugest linux geek there is.

    I write command-line utils, no wait, CGI SCRIPTS in C.

    because of this, the hodge-podge nature of the command line, and the maddening spottiness of the manpage DRIVES ME INSANE!!!! moreso than it might someone who was comfortable with a command line, and cuts and pastes from examples, maybe with a little experimentation.

    But I'm a power user, and I'm grating up against it, and I don't like it.

    How can I know that a script that I kick off that encodes a DVD chapter by chapter into ump-teen formats, with offsets the cut off the trailers (but of course -ss and -endpos use DIFFERENT UNITS) and subtitle redirection, and capture AC3 in one place, while stereo second langauge track goes somewhere else, and the video is noisy, so I have to apply video filtering...

    Well, christ, I mean, I'll never know if it's working right until I do a few dry runs, and then sometimes I have to tweak the scripts.
    With ecasound, at least I can structure my command line into sections that I can move around and comment out without so much fuss (even if I have to tweak the scripts)

    My biggest gripe is how there's three different de-telecine filters, and each of them has some quirk that always fucks me up.

    pullup is nice, but you can't set the output frame rate, nor use 3-pass encoding because the audio gets out of sync (you MUST encode in pass2, and you have to let it pick the output framerate)

    detc never works reliably, but at least you can set the framerate.

    ivtc, I have no idea what that does, but I never got it to work.

    Eh, I'm done bitching.

    Using it (to it's fullest extent) is hard. Building it is easy in comparison.

    --
    Fuck Beta. Fuck Dice
    1. Re:Don't get me wrong... by Dr.Dubious+DDQ · · Score: 1

      Wait, you write CGI scripts in C, and this is driving you insane? I'd say you're already there! :-)

      Seriously, though. Yup, I have to agree, there ARE a lot of annoying quirks and inconsistencies in the parameters, and I, too, find myself re-trying things to figure out how to get them to work...but I CAN get them to work, which is the point (as far as I have been able to tell, there just isn't a project out there that has the same bewildering range of functionality that MPlayer does. Well, not in the 'media player' category anyway.)

      I think of MPlayer/mencoder as sort of the "vi" of media players - the command syntax isn't necessarily intuitive, and a lot of people hate it, but it packs a surprising amount of functionality into its minimalist interface...(disclaimer - I say this as someone who barely knows how to use vi, so this analogy may be completely broken...)

      'course, while we're on the subject of "pet Mplayer peeves", mine is features that exist in either one or the other of mplayer or mencoder, but not both. -endpos and -ofps would be really handy when using mplayer to export video to an external encoder (such as mpeg2enc - though this may soon be unnecessary if (S)VCD/DVD-compatible mpeg files become generate-able from mencoder soon)...

    2. Re:Don't get me wrong... by Sancho · · Score: 1

      My biggest gripe is how there's three different de-telecine filters, and each of them has some quirk that always fucks me up.

      That's amazing. My biggest gripe is that TV is sent with incorrect telecining, making it difficult if sometimes impossible to recover the progressive frames.

      IVTC (de-telecine) is nearly impossible to do perfectly in an algorithm. You can get good results, but you almost never get perfect results. There are a few guides out there for manual IVTC, but AFAIK they are Windows-only. I don't know of any Linux tools to do manual IVTC, which is unfortunate, because you can get beautiful results.

    3. Re:Don't get me wrong... by Ella+the+Cat · · Score: 1

      (but of course -ss and -endpos use DIFFERENT UNITS)

      Are you sure? (I just looked again at my wrapper script, you had me worried.) The units are the same (seconds) but -ss is relative to the start and the -endpos value is relative to the -ss value. I guess you know this, I'm posting just in case anyone else scratches their head over this. I consider mplayer to be like a crossword puzzle with half the clues missing, you know it can be done, getting there is half the fun.

  84. or take a look at Xine by halfelven · · Score: 1

    VLC is pretty cool, yeah. Especially if you wanna broadcast video on a LAN.

    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.

    1. 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
    2. 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).
    3. Re:or take a look at Xine by shellbeach · · Score: 1

      But any player (not just Xine or mplayer) that uses the Xv mode has the same sharpness.

      But mplayer has a whole host of post-processing options that can make the standard picture much nicer ... Can Xine do this also?

    4. Re:or take a look at Xine by halfelven · · Score: 1

      Yes. It's called Chain Reaction.
      It has several deinterlace algorithms, unsharp, denoise, resize, some other filters borrowed from TVtime (that's another very cool media application), etc.

  85. Re:Here we go again... by dasmegabyte · · Score: 1

    Have you ever tried to install a windows program that is distributed as a source package?

    Why on earth would I want to do that? Windows' biggest success is the inclusion of everything I need to do to run a binary program already in the OS on a single (more or less) hardware architecture. There is no real advantage to compiling source rather than running a binary unless you are a developer interested in extending the application, and we developers should expect to have to jump through a few hoops. Those hoops help us acquire an understanding what's going on with a program. All they do for end users is confuse the shit out of them.

    Windows has taken uniformity to a new level, and in the process has acquired a reputation for oversimplification, poor performance and general bloat. Recompiling a program that uses Windows API calls may not have much effect on performance or stability, because most applications rely heavily on calls to APIs we can't touch. Linux, on the otherhand, is at its best when used as a minimalist architecture. Everybody want to squeeze the maximum performance out of applications because they can...and that's why you felt the need to compile from source, despite there being a number of great binaries from Sun.

    I've got no problem with wanting minimalism (shit, my favorite server runs a gentoo kernel with support for little else than a keyboard and an ethernet card), but when you've got a highly advanced application like a media player, I think you should really err on the side of ease of installation. I mean, reading this article...this guy performed more steps to run MPlayer than I did to BUILD my gentoo kernel...would it really kill these guys to take a few days to write an autodetecting installation that by default provided users with a 100% working beta?

    Judging from what I've read about that team, probably. And that's why so much open source software is still flunking the newbie test...developers are providing what the developers want, and not what new users need, because after the community gets large enough it no longer needs to attract them. Projects get BORED of newbies and their sycophantic pleas to use their software. It's elitism, plain and simple, RTFM is developer speak for "Talk to the hand."

    --
    Hey freaks: now you're ju
  86. Re:Here we go again... by Anonymous Coward · · Score: 0

    That's interesting. I have installed VS6 on so many boxes so many times (as a consultant constantly switching clients and machines, that's just part of life) since 1998 that I've lost track. I have never had a single problem with it.

    Your assertion that VS sucks because you don't get the code is ridiculous, since the install works 99.99% of the time for 99.99% of people who install it.

    That there's a problem between the chair and the keyboard and you can't figure out how to fix whatever problem is preventing you from installing it is another matter altogether, and believe me, you don't need "the code" to fix those things.

    So I'd recommend you apply this same fantastic elitist attitude to yourself and RTFM before blabbing about how "Windows sucks" because you can't figure out how to make it work.

  87. Re:I've used mplayer on and off for a while now... by Anonymous Coward · · Score: 0

    Maybe he's only smelt it alittle.

  88. MPlayer? by _Sexy_Pants_ · · Score: 1

    What, next you're going to tell me that people are using TEN again! What's wrong with Gamespy?

    --
    Look it's a joke about my sig IN MY SIG! LOL!
  89. Re:Here we go again... by salesgeek · · Score: 1

    RTFM is not a valid complaint. Windows software installs without a manual

    With the exception of late 80s and early 90s games that required the third word on third line of the fifth paragraph on the 13th page to install, I have NEVER seen a piece of software, open or closed source that required a manual in order to install.

    There simply isnt a way to:

    if Manual != Present fuxor installation else roxor

    Of course, the installer has to know what to do to make the install go...

    --
    -- $G
  90. Re:Here we go again... by chadruva · · Score: 1

    First at all, MPlayer is easy to compile, just the usual ./configure && make & make install. I have done this from old versions (even from the 0.90pre)

    Your problem is not having all the libraries installed, Mplayer comes already with a bunch of libraries bundled (libavcodec, libfaad, etc.), but mplayer cannot bundle all the windows binary codecs, imagine that!, everyone will be suing mplayer for distribuying those codecs. Then, the user legally downloads them and uses with mplayer. End of story, illegal use of codecs bypassed, everyone is happy now.

    --
    C-x C-c
  91. Re:Here we go again... by the_mad_poster · · Score: 1

    Your assertion that VS sucks because you don't get the code is ridiculous,/p>

    Are you an idiot? Oh wait.. that's not even in question here - you're posting anonymous coward without posting anything that would be necessary to keep your identity secret - you most obviously are either an idiot or a troll. Where did I assert that Visual Studio sucks because I don't get the code? Visual Studio sucks because it's a lousy toolset surrounding a bunch of shitty languages that are built on a half-assed API to a system that only runs right a quarter of the time.

    since the install works 99.99% of the time for 99.99% of people who install it

    And you got those statistics where? Your ass? The 100 homogenous machines you installed a single version of VS on? Glad to know that in your make-believe statistics I get to be the .01%.

    And, I figured out how to make Windows work just fine. You use these tools called fdisk and format, then you go get a real operating system that actually runs right and install it. Like DOS.

    As far as your assertion as to the problem between my keyboard and chair, I must say that the words of an anonymous coward who apparently works as a Help Desk technician - the lowest common denominator of IT jobs - installing half-assed tools on half-assed systems cut me so deeply that I simply can't express my anguish.

    Give me an address and I'll mail you a quarter, kid. Come back and talk to me after you've purchased a decent system and gotten a real job.

    By the way - I respond to anonymous cowards once and once only if they have no reason to post AC. Don't expect a response no matter what sort of troll you post next.

    --
    Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
  92. Xine compared to mplayer by halfelven · · Score: 1

    advantage I have with Mplayer is actually it's keyboard interface


    You can control xine-ui with keyboard shortcuts as well. Moreover, there is a text-mode interface that you can use if you don't like the GUIs.
    Read the docs before making uninformed comments.

    MPlayer also has the ability to specify video and sound drivers on the command line. Xine may have it


    Xine does have it. It's the -V and -A switches. Please read the docs.

    Xine is GUI oriented


    No. Xine is a library, not a player. Whatever interface you build on top of it, it's your decision, Xine doesn't care. Indeed, the existing interfaces seem to generally be oriented towards GUI, but there is at least one text-mode interface.

    The biggest plus to using mplayer [...] comes when you associate it with the file extensions


    That's ridiculous. You can associate extensions with any player, and the results are similar.
    1. Re:Xine compared to mplayer by fucksl4shd0t · · Score: 1

      You can control xine-ui with keyboard shortcuts as well. Moreover, there is a text-mode interface that you can use if you don't like the GUIs.

      It's been unreliable on my system. In fact, Xine has generally been unreliable on my system. Nevertheless, it gets used fairly regularly, so it's not like I never use it. The fact that I don't like the GUI isn't a general problem with GUIs, it's a problem specifically with Xine's, and it's independent of skin. Buttons mysteriously stop working, volume being one of them. I also have a problem with the fact that Xine's volume button is independent of the mixer device. MPlayer uses the mixer directly, so if my wife watches a movie with MPlayer, and turns the volume down so it doesn't wake up the baby, then I have to open aumix (or another mixer) to restore the volume for Xine to play the sound audibly.

      Read the docs before making uninformed comments.

      Dude, my comment wasn't uninformed. I was trying to provide what I had experienced to another poster. Such rudeness is not needed.

      Xine does have it. It's the -V and -A switches.

      LIke I said, Xine may have it. THerefore:

      Please read the docs.

      YOu use "please", but don't come off at all being polite or helpful.

      That's ridiculous. You can associate extensions with any player, and the results are similar.

      I said:

      The biggest plus to using mplayer [...] comes when you associate it with the file extensions

      On my system, Xine takes about 5 seconds to start up when you click on a movie file. MPlayer starts up in less than 1 second. Also, after starting, Xine takes another 2-4 seconds to start the movie. I suppose it's filling it's buffers. MPlayer starts the movie immediately upon opening the window. Xine really does choke on about 1/3 of my movie collection, whereas I have not yet found a file MPlayer couldn't play. I'm not saying there aren't any, I'm only saying that it has played everything I've thrown at it, including stuff that high-dollar windows media players (and WiMP) couldn't play.

      If it weren't for the tone of your post, I'd probably be more inclined to--as you say--read the docs for Xine, but I must say that you have completely failed to convince me I should bother. Mplayer's man page tells me everything I've needed to know, and quickly. I've never even seen docs for Xine.

      --
      Like what I said? You might like my music
    2. Re:Xine compared to mplayer by halfelven · · Score: 1

      a problem specifically with Xine's, and it's independent of skin. Buttons mysteriously stop working


      I hope you're not insinuating that mplayer is faultless. It regularly has issues with full-screen mode, on several different Linux distributions. It loses A/V sync when playing DVDs more easily than any other popular DVD player (Xine, Ogle). etc.
      I'm not saying that Xine is faultless either. But AFAICT, there's no clear "winner" in the crashing contest.

      I also have a problem with the fact that Xine's volume button is independent of the mixer device. MPlayer uses the mixer directly, so if my wife watches a movie with MPlayer, and turns the volume down so it doesn't wake up the baby, then I have to open aumix (or another mixer) to restore the volume for Xine to play the sound audibly.


      You probably never saw the "restore volum level at startup" option in xine. But since you said you never read the docs, it's not surprising.

      my comment wasn't uninformed. I was trying to provide what I had experienced to another poster


      I can see that, but you didn't present the information as personal experience (in that case it would have been ok), but as objective truths (which it wasn't). Hence my (arguably rough) tone.

      Xine takes about 5 seconds to start up when you click on a movie file. MPlayer starts up in less than 1 second


      I do agree with you that Xine takes a bit longer to start than mplayer. But in my experience the ratio is more like 3/2 not 5/1. Either you're exagerating, or something on your system is very different than on mine.

      If it weren't for the tone of your post, I'd probably be more inclined to--as you say--read the docs for Xine, but I must say that you have completely failed to convince me I should bother


      Not a big loss, from what i can see.

      I've never even seen docs for Xine


      You probably keep your eyes tightly shut, or read very selectively, otherwise i can't explain how you can miss the big honking Documentation link on their webpage.

      So much for objective comments...
    3. Re:Xine compared to mplayer by fucksl4shd0t · · Score: 1

      I hope you're not insinuating that mplayer is faultless.

      Eh? Not at all. If you read any of the rest of this discussion, you may have stumbled across posts where I agreed with problems with MPlayer and even added my own.

      I can see that, but you didn't present the information as personal experience

      Let's go over some of the phrases and sentences in my original post, shall we?

      • IN my experience, MPlayer is better than xine
      • The big advantage I have with Mplayer
      • Xine may have it
      • The biggest plus to using mplayer, in my opinion,
      • When it comes down to it, MPlayer and Xine are the two best video players for Linux, so what you really need to do, probably, is spend some time with both of them getting more intimate with them. Then you'll find that one is better than the other, and you may disagree with me. :)

      I made every attempt to show that I was presenting subjective experiences and not objective experiences. Really, with all the trash you've been talking about reading, perhaps you should practice what you preach.

      You probably keep your eyes tightly shut, or read very selectively, otherwise i can't explain how you can miss the big honking Documentation link on their webpage.

      There is one particular piece of information I have yet to convey. I have not used Xine except as the rpm provided with Mandrake. I have never looked at their website. I haven't needed to. The Xine packaged with Mandrake runs great out of the box, and I've never needed to go looking for documentation for it. I did not like the interface(s) provided, and I didn't like some of the other things. I saw a link to MPlayer from a discussion here in slashdot and went to check it out, and that's how I started with MPlayer.

      Now, to close, I'll leave you with two quotes from this most recent post of yours. This should safely leave four fingers of your own pointing back at you.

      So much for objective comments...

      You probably keep your eyes tightly shut, or read very selectively,

      --
      Like what I said? You might like my music
  93. CPU usage with Xine, mplayer, etc. by halfelven · · Score: 1

    Indeed, i noticed the same thing. On my system (AthlonXP/1800, GeForce2, Red Hat 9) i constantly get lower CPU usage from Xine than from mplayer, even though the mplayer documentation is so proud about their supposed "lowest" CPU usage among all players. It's actually funny...

    1. Re:CPU usage with Xine, mplayer, etc. by Josh+Booth · · Score: 1

      Are you using gmplayer (the mplayer GUI) or just mplayer? Actually, I haven't used Xine in almost a year, but I know that gmplayer takes about 4.5% of the processor time on my Athlon 1333 MHz when idle and a similar increase while playing. Freaky. It doesn't affect playback much as far as I can tell, but I don't use the GUI much. Also, although I haven't compared them recently, other posters have an say that Xine has trouble rendering sometimes and also that it allows frame dropping by default, while mplayer does not (there is a -framedrop switch, though). Meh, I like mplayer, even if the manpage is worse than BASH's (just because it is so hard to tell what section you're in).

    2. Re:CPU usage with Xine, mplayer, etc. by halfelven · · Score: 1

      I almost exclusively use the text-only mplayer.
      That is, when i do use it, because usually it's Xine which plays my media files.

  94. Xine browser plugins by halfelven · · Score: 1

    The browser plugin included in the gxine GUI is trivial to install, just copy the right file into the Mozilla plugins directory (or your browser's plugins directory if you're not using Mozilla). No issues whatsoever, neither on my system, nor reported by other users on the mailinglist.

  95. 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...)

  96. Re:Xine by halfelven · · Score: 1

    That is a known issue. SuSE ships a broken Xine package. I've seen a lot of reports on that.
    Red Hat also shipped a broken version a while ago.

    Don't use the version shipped by SuSE. Go to the website and download the latest release. It works without problems.

  97. Re:Install is easy! by legoburner · · Score: 1

    how lazy ;) I prefer to take it that little bit further when I install mplayer on gentoo and get a KDE gui on the front of it with the lengthy command:
    emerge kmplayer

  98. Open Source isn't for the users by Anonymous Coward · · Score: 0

    Open Source is for the developers. If you want developers that will do what you ask them to, go pay money to a commercial vendor.

    As for getting mplayer installed, I've never found it to be anything other than trivially easy when using the FreeBSD ports collection. Then again, I found lots of things to be a huge pain in the butt on the major Linux distributions, or I never would have tried alternatives.

    1. Re:Open Source isn't for the users by 91degrees · · Score: 1

      That's true, to an extent.

      Being polite and civil is for humans though. Granted, the comment in the FAQ was a joke, but some open source developers do really have that level of disdain for their users. If you don't believe me, look for criticisms of Smoothwall.

      Also, it seems that a lot of these developers are producing software purely for recognition though. They like having the fame of being responsible for a well known project. If they don't want to help, they should stop offering help. Someone else will be able to help.

  99. MPlayer works fine for me. by MikeFM · · Score: 1

    When I first started trying to use MPlayer I got annoyed because it wouldn't run for me.. then I actually read the directions and presto it worked. Amazing. My problem was that I hadn't bothered to find out that you need to tell MPlayer the audio and video drivers you need.

    Installing was never a problem for me. I've installed on several computers from source, rpm, and deb and all have went off without a hitch. Again just follow the directions and everything works. The config script located all the codecs I had installed by itself.. even some that I'd put in unlikely places.

    I don't like GUI programs for watching DVD's so after a first attempt at using it (which worked) I just stopped using it. Why would you need a GUI? The whole OS is your GUI. I setup Nautilus to open movies in MPlayer and installed the plugin patch so MPlayer would work with Mozilla. That works very well for most use. When I rip a DVD I have it also build a script that tells MPlayer how to play the movie to the best of it's abilities. My ripping program then adds an option to my 'Videos' menu to make playing the movie as simple as running any other program.

    I don't have a problem with speed for playback and I'm using a 933Mhz C3 CPU with no fancy video card to boost things along. If you're Athlon can't keep up I'd say you've probably selected the wrong audio/video drivers or are trying to do something fancy you need not do.

    Perhaps you should wait for the stable release to do your review? Reviews on pre-releases aren't really an honest look at what a program can do. Obviously it has faults.. that is what pre-release canidates are for. :)

    --
    At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  100. mplayer for windows.. by Anonymous Coward · · Score: 0

    is here: ftp://ftp.mplayerhq.hu/MPlayer/releases/win32-beta
    it works perfectly for me

  101. Well ideally by Sycraft-fu · · Score: 1

    It should be so simple you don't NEED to read a readme to install it. It is possible, as Windows shows with it's installers. I've also seen more than one installer under Linux this simple. Devs really should strive for this. Don't make users go throug any unecessary steps or do preinstall reading. Just have them run the installer, and give them nice on screen prompts.

    It may seem silly to a geek, but it makes a difference to many neophytes. They are easily scared and/or intimidated and hence each barrier, no matter how trivial, makes them more likely to fail. Try and make it as simple as possible, and it really will help Linux with the mainstream.

    1. Re:Well ideally by Hatta · · Score: 1

      mplayer's installation follows the usability maxim "simple things should be easy; complicated things should be possible" Compiling a functional mplayer is as easy as ./configure; make; make install.

      But mplayer is a complicated program and its install is aimed at flexibility. So if you want extra features like a GUI or an OSD you have to take a couple extra steps. In the windows world they'd just compile everything in and that leads to a lot of bloat.

      If you're just going to do that what's the point of having the source at all?

      --
      Give me Classic Slashdot or give me death!
  102. Re:Here we go again... by Anonymous Coward · · Score: 0
    you most obviously are either an idiot or a troll

    I pissed you off, so I must be a troll. Check.

    Visual Studio sucks because it's a lousy toolset surrounding a bunch of shitty languages that are built on a half-assed API to a system that only runs right a quarter of the time.

    That's a great summary. I guess you use the VS equivalent in Linux... oh, wait. Never mind. And anyway, "a quarter of the time"? What was it about statistics again?

    You use these tools called fdisk and format, then you go get a real operating system that actually runs right and install it. Like DOS.

    HAHAHAHA!!! You kill me man. You are so '1337'. Edlin all the way, eh?

    I must say that the words of an anonymous coward who apparently works as a Help Desk technician

    And you got this from where? Your ass? Oh, right, if I'd logged in as "TehCodeMaster2003" you'd be all impressed, of course. You'd know exactly what I do for a living.

    Don't expect a response no matter what sort of troll you post next.

    Once and only once. That's impressive, eh.

  103. Re:Xine by norite · · Score: 1

    Thanks very much...I'm downloading it now....

    --
    -- Fuck Beta
  104. mplayer, article by portscan · · Score: 1

    I have been using both mplayer and xine on Gentoo [GNU/]Linux for quite some time, and I have recently become quite frustrated with mplayer. Yes, its support of many different formats is commendable, but I find it losing the synchronicity of the audio and video tracks WAY too often. I have recently brought xine from back-up to primary player, and use mplayer only when xine does not support the video file I am trying to play, which is rare. xine is fast, polished, and less buggy than mplayer in my experience. Is there any reason to bother with mplayer at all for formats that are supported by both?

    As a side note, am I the only one who finds these articles to be pretty immature? This guy is just complaining left and right (especially in the first one). And inserting the piece about how playing video files in mplayer required getting video files from gnutella? Come on...

  105. Re:Install is easy! by Anonymous Coward · · Score: 0

    Ha ha, "get a life" from someone who flames about OS preference.

  106. Trolling for dollars by Anonymous Coward · · Score: 1, Informative

    I'm a self-confessed Joe Barr apologist -- and one of those fucking red hat lusers that mistakenly tried to compile a version of mplayer as well. Boy what was I thinking?

    Save some of your disappointment for the mplayer developers. I found my visit to my proctologist to be more pleasant at the time than dealing with Arp'i's ego.

    This is what Joe Barr ran into when he tried to coimpile mplayer circa 2001 (reposted from freshmeat).

    ------- http://freshmeat.net/projects/mplayer/?topic_id=12 7%2C128

    [] Compile warning
    by Christian Rose - Nov 26th 2001 14:47:10

    When trying to compile MPlayer 0.50, I get:

    $ ./configure
    You can get detailed help on configure with: ./configure --help
    Please wait while ./configure discovers your software and hardware environment!
    Detected operating system: Linux
    Detected host architecture: i386
    Checking version of gcc ... 2.96, bad
    Please downgrade(upgrade) gcc compiler to gcc-2.95.2+ or gcc-3.0+ version!

    Note: gcc 2.96 is RedHat's UNOFFICIAL (it can be found only on RedHat sites, or
    in RedHat-based distributions) and BUGGY gcc release. gcc 2.96 is TOTALLY
    unsupported by us, because it simply SKIPS or badly compiles some MMX codes!
    Important: this is NOT an MPlayer-specific problem, numerous other projects
    (DRI, avifile, etc..) have problems with this shit too. DO NOT USE gcc 2.96 !!!
    If you don't want to downgrade, use the --disable-gcc-checking option to avoid
    this check, but DO NOT SEND BUGREPORTS OR COMPLAIN, it's *YOUR* fault!
    Get ready for misterious crashes, no-picture bugs, strange noises... REALLY!

    On the other hand, when I check http://www.bero.org/gcc296.html, I notice this:

    asm( [...] "packuswb %%mm0, %%mm0 # B6 B4 B2 B0 | B6 B4 B2 B0\n\t"
    "packuswb %%mm1, %%mm1 # R6 R4 R2 R0 | R6 R4 R2 R0\n\t"
    "packuswb %%mm2, %%mm2 # G6 G4 G2 G0 | G6 G4 G2 G0\n\t"
    [...]
    )

    While this is not exactly commonly found code, it's one of the perceived gcc 2.96 "bugs" most talked about. This code used to be in MPlayer, causing it to miscompile, and its maintainers to add loud and blatantly wrong statements to their documentation. The reason this code miscompiles (only the packuswb %%mm0, %mm0 instruction is executed) is that recent versions of gcc, starting with 2.96, support both the Intel and AT&T variants of x86 assembly.
    The pipe character is an actual symbol in the Intel variant, therefore its use in asm() constructs (even comments in asm constructs) is illegal.
    This has since been fixed in the MPlayer code - unfortunately its maintainers didn't remove their unjustified comments about gcc 2.96 at the same time.

    Seems not very nice of the MPlayer people to provide completely unjustified loud warnings like that.

  107. Polite request for Xine folks cf MPlayer features by Ella+the+Cat · · Score: 1

    MPlayer supports my DC10+ card (as does mjpegtools of course). I'm not aware Xine does. For those who don't know, DC10+ is an MJPEG-in-hardware card with composite and SVHS ins and outs.

  108. Re:Install is easy! by Anonymous Coward · · Score: 0

    I love how with any story, even one NOT about debian, some stupid crotchbite fucktard debian user makes it a point to bring up debian. THIS is why people fucking hate debian users. News flash... DEBIAN IS SHIT. MOST PEOPLE HATE IT. IT SERVES NO PURPOSE. If you want easy Linux, there's mandrake. If you want commercially supported Linux, there's redhat. If you want bleeding edge high performance, there's Gentoo. If you want top of the line stability for a server, you should be using FreeBSD and no Linux at all. So debian is a USELESS distro that fills NO NICHE at all. FUCK DEBIAN.

  109. How does mplayer play proprietary divx? by sacrilicious · · Score: 1

    Given that the divx algorithm is proprietary (it is, right?), how does mplayer play divx files? Does it invoke a binary supplied by divx.com, or does it include source from divx.com, or does it reverse engineer it? I ask because I'm concerned that someday soon I won't be able to play my divx files, or at least not without pay per view fees headed to divx.com...

    --
    - First they ignore you, then they laugh at you, then ???, then profit.
    1. Re:How does mplayer play proprietary divx? by Anonymous Coward · · Score: 0
      Does it invoke a binary supplied by divx.com

      Bingo.

      You should install that before compiling if you want divx support.

  110. Re:drop frames = trade off by Anonymous Coward · · Score: 0

    I'd rather it drops frames then go out of sync.

    Mplayer is my favourite player hands down..Quicktime isn't even in the dock here..

  111. Barr has an unhealthy fixation ... by juhaz · · Score: 1

    ... for compiling things.

    If he wants the install to be easy, why not just install an rpm (he was using RH9) and be done with it?

  112. The issue is... by pr0ntab · · Score: 1

    -ss works by guessing how many frames to skip by the framerate in the header (but this can change in realtime, and often does, especially during playback if you're using pullup filters).

    Meanwhile, -endpos only counts "output" time during playback or encoding.

    This means segments corresponding to -ss 0 -endpos 60, -ss 60 -endpos 60, and -ss 120 -endpos 60 are not necessarily back to back 1 minute long chunks, but can arbitrarily overlap.

    -ss positioning can be precise, in that you can specify a frame or byte amount to skip. Unfortunately, -endpos is always measured in units of time. This means you can never guarantee a seamless segmentation using those options unless you recode the video into a constant fps format that is de-interlaced FIRST, then segment it.

    It would be nice if you could do -endpos as a "secondary" -ss where encoding when stop when a certain point in the input stream is reached. At least, using this method, the segments would be back to back, and guaranteed monotonic no matter how the parameter is used.

    Perhaps call it endpos, and call the old, time-based endpos -maxtime?

    --
    Fuck Beta. Fuck Dice
    1. Re:The issue is... by Ella+the+Cat · · Score: 1

      Hey, thanks, I've learned something! Unfortunately for me :( because I've been trying to script (using Tcl) a tool to take mjpegtools editlists and use mencoder to produce a compressed movie from an MJPEG movie (huge!) plus mjpegtos editlist directly without needing an intermediate (again, huge) MJPEG file. It sort of works, so your post might explain its quirks. What fun! Good suggestion too, let's hope some mencoder folks are reading this.

  113. Proof by yerricde · · Score: 1

    Now, proving that there can be no algorithm that produces conforming bit stream sounds like a pretty challenging theoretical CS problem to me

    Actually, it might be a lot harder. There exists an algorithm that produces a conforming LZW bitstream yet produces larger output than the uncompressed input. Likewise, it might be possible to make an unquantized MPEG file out of I-frames without infringing any patent, but it's not useful, given a definition of "useful" in terms of SNR for a given data rate.

    However, if somebody does manage to prove that there exists a useful compressor algorithm that does not infringe the purported essential MPEG patents, Kleene's realizability interpretation along with the Curry-Howard isomorphism allow anybody with access to the proof to convert it into the algorithm.

    --
    Will I retire or break 10K?
  114. Xine does not work under OSX by Anonymous Coward · · Score: 0

    Te posts on this thread are about OSX. Mentioning Xine does not make sense because Xine does not work under OSX. As far as I know right now there are three different types of players for OSX.

    Players which use the Quick Time engine, for example cellulo.

    The OSX implementation of videolan, done by the vlc developers.

    The OSX port of Mplayer. It seems tht this port is not done by Mplayer developers,but by a guy from the Czech Republic.

  115. Re:Xine by Wolfrider · · Score: 1

    --Did it work???

    --
    .
    == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??