
Quicktime Under Linux With MPlayer 267
Sark writes: "The latest version of the controversial MPlayer program for
Linux supports Quicktime .mov files with the latest codecs.
Apart from the closed source program Crossover, this is the first
open source program that seems to work. Check out the Mplayer
homepage for more info." According to
formats page, Sorenson
Quicktime is still not gonna happen any time soon.
No sorrenson? =( (Score:1)
Re:No sorrenson? =( (Score:2, Interesting)
avifile [sourceforge.net] uses some wine source to utilize win32 dll's to play stuff like windows media video. what prevents them from adding the windows dll for sorenson to it?
i've unfortunately been too lazy to fire off an e-mail and ask them how difficult it would be to add it to the project, else i'd think of doing it myself (unfortunately, i'm not a kung foo master yet ... in fact, i'm almost inept as a programmer ... but i'll whine about that later).
speaking of which, has anybody else thought of this as a possible solution?
huh? (Score:2, Interesting)
Whats the point?
[shamelessly lifted from a post in a different article]
Quicktime is a wrapper format for a number of codecs, just like AVI. An actual Quicktime file is almost invariably encoded in the Sorenson file format, which is is exclusively licensed to Apple. MPlayer can probably never play this format!
Xanim Supports Quicktime (Score:5, Informative)
Re:Xanim Supports Quicktime (Score:2)
MPlayer + Quicktime = schweeetttt (Score:4, Informative)
I really love the GCC 2.96 RedHat warning, if you havent built it yet, HEED that warning.
Is there no chance the RIAA et al can shut this down being out of hungary? I hope not its becoming a wonderful piece of software.
Congrats to the guys making MPlayer happen !!
Re:MPlayer + Quicktime = schweeetttt (Score:3, Insightful)
While I do not doubt that gcc 2.96 has bugs, in my experience it's not worse than most gcc versions I used during the years, and much better than quite some of them, especially in C++.
I also did a bit of google-ing about this warning in mplayer, and AFAIK some people were a bit angry that 2.96 has been singled out (probably just because it's a RH release) I wonder if the reasons for so prominently warning people about 2.96 are at least in part political...
Because of support (Score:2)
I subscribed to the mailing list for a while, and the reason it got singled out is because every couple of days someone would complain that mplayer didn't compile. And the reason for that? Because they were using gcc 2.96.
Who reads warnings from 'configure'? That's right, not many people at all. So having the luser type in a statement that they know what they are doing is far better than letting them "click-thru" something you can be sure they didn't read.
Re: RIAA/MPAA shutting this down, eh? (Score:1)
Uhmm... While I'm trying not to troll here, why on earth would the RIAA/[MPPA] try and shut this down? Does it allow piracy? No. (Well, I suppose you could use quicktime for pirated films, but I can't think why you'd want to)
Does it infringe anyone's intellectual property? Not as far as I can tell, mplayer most of it's codec modules as seperate .dlls. (I suppose if apple has a patent on the quicktime format as a whole, they could come after mplayer, but that seems unlikely, and it certainly would'nt involve the RIAA/MPAA).
I've lost count of the amount of times I've seen someone on slashdot make some misinformed comment about the RIAA/MPAA/DMCA, they seem to be considered as the generic bad guys, who will spoil ALL your fun, even if it's not in any way related to them.
</rant>RIAA break your glowstick, RIAA eat your candy.
Re: RIAA/MPAA shutting this down, eh? (Score:1)
If you think the MPAA/RIAA are ONLY concerned about stopping piracy you are the one who is misinformed, yes it is a concern to them and a main one, its about making MONEY period and the Artists themselves know this. BEYOND piracy are ownership issues that are being fought out even no. The RIAA/MPAA is a party to this as well. CONTROL is another issue the RIAA is driven twoard, the DeCSS, (or POSSIBLE use of that code MUST be unacceptable to them) otherwise why go to the lengths in cutting links and removing code thus far ?
That is why I was curios, if they had any legal flak as of yet or if they are even succeptable , MPlayer being in
Re: RIAA/MPAA shutting this down, eh? (Score:2)
In any case, it won't matter. The horse is out of the barn already. The RIAA/MPAA can close the barn door (in the US, maybe), but they won't ever catch the horse again. To paraphrase someone's famous quote about the Internet, open source software interprets authoritarian oppression as damage... and routes around it.
Re:MPlayer + Quicktime = schweeetttt (Score:1)
It works fine for me on Redhat 7.1 with gcc-2.96-85. Really, they just have a problem with Redhat period, and I don't think they think much of anyone using Redhat linux. I wonder what real consequences derive from using this version of gcc. I've had no problems with mplayer.
It's a great program once its up and running, though. Best video playback on linux.
Re:MPlayer + Quicktime = schweeetttt (Score:2)
/dev/fb0 ? (Score:1)
$ mplayer test.mpg
(about 11 lines of output snipped)
Detected video codec: [mpeg12] drv:1 (MPEG 1 or 2)
fbdev: Can't open
Sorry, selected video_out device is incompatible with this codec.
I would suppose this has something to do with the framebuffer? What do I need to do to get this going on a fairly stock RH install? Thanks.
Re:/dev/fb0 ? (Score:1)
mplayer -vo xv test.mpg
Or check your
Re:/dev/fb0 ? (Score:1)
MPlayer 0.50 (C) 2000-2001 Arpad Gereoffy (see DOCS!)
Reading
font: can't open file:
font: can't open file:
Playing test.mpg
Invalid video output driver name: xv
Use '-vo help' to get a list of available video drivers.
(are those font files the culprit? Do I really need them if I don't have vids with subtitles?)
so i tried: mplayer -vo help and get:
MPlayer 0.50 (C) 2000-2001 Arpad Gereoffy (see DOCS!)
Available video output drivers:
fbdev Framebuffer Device
null Null video output
odivx OpenDivX AVI File writer
pgm PGM file
md5 MD5 sum
mpegpes Mpeg-PES file
so I tried: mplayer -vo fbdev test.mpg
but still get: "fbdev: Can't open
Any suggestions?
Re:/dev/fb0 ? (Score:2)
You may still have problems with audio, depending on your desktop environment. I don't know if esd poses any problems, but with KDE I have do run
mplayer -vo x11 -ao sdl test.mpg
If you don't have sdl and you have problems, you could always just chuck the audio with
mplayer -vo x11 -ao null test.mpg
Re:MPlayer + Quicktime = schweeetttt (Score:1)
I have TWICE 2 DIFFERENT Machines, Its SCREWY as hell, SCREWEY is a technical term that means just plain act strange, crashed, skitters, all kinds of wierdness, on occasion, sometimes its fine,
I built it with 3... and guess what NO PROBLEMS that I had with the RH 2.96 on the SAME MACHINE.
Work great with one, work schitzy with the one they warn you about
Have you even read the MPlayer warning ?
Re:MPlayer + Quicktime = schweeetttt (Score:1)
Yup. Works like a charm, thanks. On two different machines.
BTW, when it gives that asinine prompt to type "gcc 2.96 is broken" or whatever, you can type "gcc 2.96 works just fine and the mplayer developers don't have a clue what they're talking about" and it'll go through. Makes me feel a bit better when building it
Re:MPlayer + Quicktime = schweeetttt (Score:1)
Don't Bitch at MPlayer; Blame Apple! (Score:1, Interesting)
Re:Don't Bitch at MPlayer; Blame Apple! (Score:4, Interesting)
The Sorenson codec is owned by Sorenson [sorenson.com] and Apple pays for it. If you want to get a legal player for a non-Win/Mac platform someone will either have to
1. reverse engineer the codec(legally questionable and hard)
2. write a wrapper that uses another OSs Code (crossover does this)
3. legally licence the code and release a player (anyone?)
4. actually get sorsen to let people have their source(or detailed specs) somehow.
the best thing to do is just start using a codec that already lets people have their source and is on par with the best VP3 [vp3.com]
Re:Don't Bitch at MPlayer; Blame Apple! (Score:1)
> their source(or detailed specs) somehow.
...which conveniently ignores the fact that Apple remains the sole exclusive licensee of the "spec" in question. Apple is firmly in control of this situation, regardless of what excuses might be made for them.
Re:Don't Bitch at MPlayer; Blame Apple! (Score:1)
Re:Don't Bitch at MPlayer; Blame Apple! (Score:2)
Re:Don't Bitch at MPlayer; Blame Apple! (Score:2)
4. actually get sorsen to let people
These two are actually the same problem: Apple pays Sorenson for an exclusive license to the codec. If it isn't Quicktime, it can't use Sorenson.
Thus, the options are either convince Apple to release Quicktime for *nix (Quicktime for OS X runs way up in the Cocoa/Aqua layers, not down in BSD, so it doesn't count), or convince content producers to use another codec (MPEG4, some day).
Re:Don't Bitch at MPlayer; Blame Apple! (Score:2)
reverse engineer the codec(legally questionable and hard)
Try ILLEGAL. You can reverse engineer things protected by copyright, but you cannot reverse engineer patented algorithms.
2. write a wrapper that uses another OSs Code (crossover does this)
Of questionable legality.
3. legally licence the code and release a player (anyone?)
This ignores the real issue. Apple has exclusive licensing to the Sorenson codec. Steve Jobs will NEVER allow a linux player, and this patent has over a decade before it expires. Both Apple and Microsoft want to keep other OSs out of the home/desktop market. Banning streaming media from them is part of the plan. You can expect the next moves from Microsoft will be changing to WMF 2.0 (also patented), and then lease the servers dirt cheap to take over the market from Real and Quicktime.
None of this helps open source users, because the battlefield requires patented protection just to play. And Media Players will only exist for viable desktop market, and linux doesn't matter enough yet. At least Real is backed by AOL, so there is a chance Real will become the de facto standard. But I doubt it. Microsoft can give away WMF servers with the amount of profit they make, and flood the server market with WMF. At that point it is all over.
Re:Don't Bitch at MPlayer; Blame Apple! (Score:2)
It is all about market control and blocking alternatives other than Windows and MacOS. The server even exists for linux. Just no player.
This is not about the amount of effort it would take to port the Sorenson codec to linux. Quicktime players already exist, and their authors are willing to code it at no cost to Apple.
Apple, however, will not allow this to occur. Patented codecs like WMF 2.0 and the Sorenson codec are not ALLOWED in linux simply because that is one more thing keeping Unices from becoming viable desktop alternatives of the future. And these streaming media patents have a LONG LONG time to go before they expire.
Real, however, actually provides support for other OSs (by supporting a player coded by the linux community).
How can anyone have a web standard that is not open and provided with cross-platform support ? These moves by Apple and Microsoft have two aims - to control the streaming server market and to block free operating systems from the desktop market. Period.
Re:Don't Bitch at MPlayer; Blame Apple! (Score:2)
There should certainly be enough there to get started. And, in countries that do not support algorithm patents, this would be legal.
It is non-trivial to reverse engineer such a codec, though. It would be a massive effort.
Re:Don't Bitch at MPlayer; Blame Apple! (Score:2)
I'd really liked an unencumbered codec to win.
Barring that (and that seems unlikely), I'd like a codec supported cross-platforms to win.
And if that fails, the market has failed me. I do not use Windows or MacOS, and anything else will simply not be seen by me.
Controversial? (Score:4, Insightful)
Re:Controversial? (Score:1)
Re:Controversial? (Score:1)
Some of the questions in the FAQ do come across as a bit testy, yes. However, this is understandable, because the person who wrote it (Gabucino) is the one who gets ALL the newbie questions. So, yes, he can get annoyed ;) However, everyone I've ever talked to on the mailing list is consistently friendly and helpful.
The only reason that anyone could really call MPlayer controversial is because they had some lisencing issues a while back, because of incompatible lisences in (if I remember right) the OpenDivX portion of the program.
Re:Controversial? (Score:1)
Re:Controversial? (Score:4, Insightful)
"The MPlayer gang seems to relish nothing more than belittling their users and reminding them of just how little they know about Linux and computing in general. I don't know about the rest of you, but I suffer enough of that on my own. I do not need any outside assistance to reinforce that point of view.
Naturally, I was drawn to the project like a moth to a flame. Bring it on, I thought. Whatever it takes, I'll get it installed. I won't be asking that infantile band of RTFM-spewing bozos who maintain it for help, either. My own hardheadedness is probably the only reason I sit here today with MPlayer installed, with a custom GUI skin enabled no less, barely more than a full day after I started."
http://www.idg.net/go.cgi?id=620307 [idg.net]
Why not look at Open Soruce programs? (Score:2)
Non-Sorenson Quicktime in only useful for people making movies under Linux.
Many people put in a bloody large amount of time and effort into getting newcomers to the platform. Telling someone they're an idiot because they don't know how ldconfig works undoes that hard work and pisses me off. Its possible to answer newbiew questions withotu being a fuckwit, but the mplayer team would rather serve their own egos. Especially if mplayer was packaged like most Linux programs (the mplayer team forbid this) the postinstaller would do that anyway.
Ogle, Xine and Avifile are also more well designed, with most options avaliable via the GUI and command line switches rather than compile time options.
The MPlayer team have also yet to respond to Bero's response [bero.org] re: their GCC 2.96 claims, leaving something on their web page which has seemingly been proven to be technically false.
Furthermore, telling me in captial letters that MY SYSTEM IS TO SLOW TO PLAY THIS MOVIE when I'm fairly sure a 900 Mhz Athlon with 640MB of RAM is capable of playing a VGA res DivX is worth a laugh or two.
When there's a billion better players out there which don't go out of their way to be rude to people and Open Source licensing, why use Mplayer?
Re:Controversial? (Score:2, Insightful)
There is no law that says they must be all sweetness and light to users who give them no thanks half the time, no help almost all the time, and no money all the time.
They wrote the software, it is a priveledge they gant you to be able to use the software they put so much time into. Be thankful you get that priveledge, but don't expect the be waited on hand and foot.
Xanim has done this for a while... (Score:5, Informative)
Come again? (Score:1)
Re:Come again? (Score:1)
Of course MPlayer is not the "first open source program that seems to work" with Quicktime, that's completely laughable nonsense, as others have pointed out.
Where are the Debian packages? (Score:3, Interesting)
You know, if Linux video software would come as Debian packages, I would be really happy. Currently, if I want anything with avifile or something, I need to compile it myself - and I don't want to mess with the source because avifile API isn't exactly solid yet and source that compiled yesterday doesn't work today. Linux video support Isn't Here, dammit.
The mplayer author seems to be aware of the Marillat's unofficial .debs... and now whines that people are violating his "thou shalt not distribute Binaries" lisence.
I don't want to compile the package myself. I want binaries.
Source-only distribution is fine, as long as you let somebody make the pre-built binaries available so that we lazy bastards can use the program. I know I can compile mplayer if I'm positively motivated, but I know my mother couldn't.
This is why I'm considering using VideoLanClient instead of mplayer - at least it's under GPL and I'm able to get "official" Debian packages for it.
Re:Where are the Debian packages? (Score:1, Troll)
--
Mod me down
Re:Where are the Debian packages? (Score:1)
Obviously you've never built mplayer... or used Slackware 3.2 where I needed to build everything interesting from source if I didn't want to use year-old stuff. You kids have Stow to manage /usr/local, back in the day we needed to spend a day to nuke something installed to /usr/local - and we liked it! =)
You know, the fact that I can just say "apt-get install whatever" to get my favorite software is a Good Thing. Don't get me wrong - I just wished to say that I hate duplicate work, installing pre-alpha-grade development libraries, and working with package source dependencies.
Zillions of people out there download, build and install mplayer from source - while downloading prebuilt binaries would be much nicer and more convinient for everyone.
I know, Real Men build the whole system from scratch. Those people are real artists. Now, would you please get me a distribution aimed for mortals?
Where are the binary packages? (Score:1)
Also, Mplayer configures itself based on what libraries you have installed on your system (ffmpeg, OpenDivX, SDL, win32 codecs, etc). Including all these libraries would be redundant, including none would build an Mplayer that can't play movies ( which would be worthless). This could be overcome if Mplayer built video decoders as plugins that could be loaded at run-time, but it doesn't.
Lastly, all the decoding and video output is optimized at compile time for MMX, 3D-now, SSE or whatever CPU-specific speedups it detects. If the build host has an Intel chip and you have an AMD, the player would crash and burn on your machine. This could probably be overcome by adding CPU-detection code, but including a different version of every decoder for every CPU would add unnecessary bloat.
Re:Where are the Debian packages? (Score:2)
Re:Where are the Debian packages? (Score:2, Informative)
/Janne
Re:Where are the Debian packages? (Score:1)
Re:Where are the Debian packages? (Score:5, Informative)
Secondly, to be really useful, MPlayer requires several dlls, and codecs. These codecs either come from the windows dlls, or from closed source projects like the DivX(tm) MPEG-4 Codec.
Distribution of these is prevented by their license. There are just links to them on the mplayer page. It is best if you compile mplayer yourself.
Also, as a christmas gift, teach your mother the "./configure; make; make install" trick
Re:Where are the Debian packages? (Score:3, Informative)
./configure && make && make install
next time. that way, if configure dies, make doesn't try to run. and if make dies, make install doesn't try to run. you'll be happier.
Re:Where are the Debian packages? (Score:1)
Hell, if you're feeling saucy, you might even teach her how to make perfect debian packages out of the MPlayer source. It's really very easy, especially since they've been kind enough to provide the scripts...
fakeroot debian/rules binary
One command. Yes, it really is that simple
Re:Where are the Debian packages? (Score:1)
MPlayer forbids packages and isn't OSS (Score:2)
GFair enough, but that's an architecture problem that the team should hopefully fix soon.
Secondly, to be really useful, MPlayer requires several dlls, and codecs. These codecs either come from the windows dlls, or from closed source projects like the DivX(tm) MPEG-4 Codec.
So? Many (read most) Linux players do this: Avifile, Xine, etc. They can still be packaged - stick freshrpms.net in your sources.list on your redhat box and APT away. They just separate the DLLs from the software if necessary.
Unlike the Open Source players, though, Mplayer uses non Open Source code in its actual binaries apparently. So yeah, ignore the web page claiming its open source and read this Mplayer therefore does not meet the Open Source Definition or the Free Software Freedoms list and shouldn't bother claiming to be Open Source. [mplayerhq.hu]
Re:Where are the Debian packages? (Score:1)
Re:Where are the Debian packages? (Score:1, Informative)
mplayer is illegal to use in binary form, and will likely always be that because of the stupidity of it's authors.
Re:Where are the Debian packages? (Score:1)
Aviplay is tied to the (binary only) win32 codecs. Anyone who really cares about the politics of licensing would find that an unacceptable solution too.
Re:Where are the Debian packages? (Score:2)
Sheesh. I guess you'll have to build a C
interpreter. (Is it even possible to run
C as an interpreted language? I have to
think about this.)
Re:Where are the Debian packages? (Score:1)
deb http://marillat.free.fr/ stable main
Xine (Score:3, Informative)
xine.sourceforge.net [sourceforge.net]
Re:Where are the Debian packages? (Score:1)
Re:Where are the Debian packages? (Score:1)
mplayer - The Ultimate Movie Player
apt-cache show mplayer
Package: mplayer
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 2540
Maintainer: Dariush Pietrzak
Version: 0.50-1
Depends: libc6 (>= 2.2.4-4), libglib1.2 (>= 1.2.0), libgtk1.2 (>= 1.2.10-2.1), libncurses5 (>= 5.2.20010310-1), libpng2 (>= 1.0.12), libsdl1.2debian, libstdc++2.10-glibc2.2 (>= 1:2.95.4-0.010810), xlibs (>> 4.1.0), zlib1g (>= 1:1.1.3), debconf, libconfhelper-perl
Description: The Ultimate Movie Player
MPlayer is a movie player for Un*x. It plays most MPEG, AVI and ASF files,
supported by many native and Win32 DLL codecs. You can watch VCD, DVD and even
DivX movies with MPlayer.
.
MPlayer supports a wide range of output drivers: X11, Xv, DGA, OpenGL,
SVGAlib, fbdev, AAlib, GGI, SDL . You can use SDL and thus all the SDL
drivers. Same goes for GGI.
There are some low-level card-specific drivers (e.g. Matrox). Most of the
drivers support either software or hardware scaling, so you can enjoy
movies in full screen mode.
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 2540
Maintainer: Dariush Pietrzak
Version: 0.50-1
Depends: libc6 (>= 2.2.4-4), libglib1.2 (>= 1.2.0), libgtk1.2 (>= 1.2.10-2.1), libncurses5 (>= 5.2.20010310-1), libpng2 (>= 1.0.12), libsdl1.2debian, libstdc++2.10-glibc2.2 (>= 1:2.95.4-0.010810), xlibs (>> 4.1.0), zlib1g (>= 1:1.1.3), debconf, libconfhelper-perl
Description: The Ultimate Movie Player
MPlayer is a movie player for Un*x. It plays most MPEG, AVI and ASF files,
supported by many native and Win32 DLL codecs. You can watch VCD, DVD and even
DivX movies with MPlayer.
.
MPlayer supports a wide range of output drivers: X11, Xv, DGA, OpenGL,
SVGAlib, fbdev, AAlib, GGI, SDL . You can use SDL and thus all the SDL
drivers. Same goes for GGI.
There are some low-level card-specific drivers (e.g. Matrox). Most of the
drivers support either software or hardware scaling, so you can enjoy
movies in full screen mode.
.
MPlayer has nice, big antialiased shaded subtitles (7 supported types!)
with Hungarian, English, Cyrillic, Czech and Korean fonts, and OSD.
It works for me atleast. Im using unstable.
MPlayer has nice, big antialiased shaded subtitles (7 supported types!)
with Hungarian, English, Cyrillic, Czech and Korean fonts, and OSD.
Re:Where are the Debian packages? (Score:2)
Linux is stable and fast(compared with MSanything).
developers need to relize that most people with computers do not know how to compile, don't want to learn, they want it to work.
you say "how hard is it to type configure && make && make install" this is very intemdating for people, espcially since most computer users don't even know about those commands.
I say to you: How hard is it to create an installer that does the for the user? Evin if binaries are illegal to distribute do to some dumb ass liscense, the installer can do the compiling in the back ground and just display a progress bar.
If you want Linu to bew successfull, you must look at the big picture and ask yourself, "What can I do to make it easier for the average user?"
Even if a program the average user uses is a little bloated because of it. Those of us that can compile a more compact binary will.
Re:Where are the Debian packages? (Score:2)
The nice thing about Linux is it's diversity in all possible ways. There certainly are people working on products that will get Linux more into the mainstream (like Mandrake), but why should every developer commit himself to that same goal?
It is in the developer best interest to develop products anybody who can click a mouse can use.
More people use linux, the more paying jobs there will be for linux developers.
a working computer is useless if the user can't get to the apps easily.
Anybody who says they want linux to be the desktop OS, but doesn't write there app in a way to make it friendly to the average computer user, is foolish.
Its the responsibility of anybody who wants Linux to be mainstream, to make an effort to do so.
Yes a working product is the main goal, but putting out a shell script that autoated the build process isn't really that difficult. Might take 5 minutes to do? That just lazy, and with all respect to Larry Wall, laziness is not a virtue.
Re:Where are the Debian packages? (Score:2)
Please.
Not to mention that any recent (>7.0, iirc) RedHat, Mandrake, or Slackware copy of GNU's 'tar' program can decompress bz2 with a flag (-y on slackware, -J on redhat, and I forget for Mandrake). BZ2 might not be your personal favorite, but it's quite far from non-standard. Not to mention the fact that it's also BSD-licensed. It doesn't really get more free than that.
Other users have mentioned _why_ the MPlayer developers refuse to allow others to distribute binary distributions, but basically, it boils down to this.
1. Code that is compiled on the local machine will generally run faster than lowest-common-denominator compiled packages.
2. Some of the codecs that MPlayer uses are linked in during compile time, and are not Open Source/Free Software, so it's questionable to redistribute them (at best; in some cases, it's outright illegal).
3. The codec architecture in MPlayer is not dynamic, it's static. So the 'mplayer' binary that you end up with has all of those codecs loaded in, and it can't pick up new ones without a recompile. Chalk it up to over-optimization or bad design, but that's the fact.
I'm not saying that this is a textbook case of how to write, package, and distribute software, but it's definitely not a textbook case on how not to do it.
Dammit, I fed a troll again. : /
Controversial? (Score:2, Interesting)
Lee
Re:Controversial? (Score:4, Informative)
The short version:"They're a bunch of arrogant elitist bastards". (The article's opinion, I've never tried to install mplayer).
Re:Controversial? (Score:2)
Re:Controversial? (Score:2)
>>>>>>>>>>>>&g t;
Only because most people who use Linux are nerds. Honestly, can you say that typing
Re: (Score:1)
Re:Controversial? (Score:1)
And the attitude. Well, they have correct attitude. Instead of writing thousand times the same things, they wrote they once, and the are giving RTFM tips for everyone. That's is good! Documentation is for reading.
If you have problem - look ina FAQ, read documentation, grep documentation. You will find answer. And, damn, the source is readable. I solved one of my problem with reading source.
Mplayer is really great project (although iconv from cp1250 to latin2 still doesn't work
Re:Controversial? (Score:2)
You know, I never read the article that is cited here. I did some research on my own about 2 months ago, when I was looking for a video player for my new Linux boxes. And I came to a conclusion that appears to be roughly similar to what people are saying about this article: in short, the MPlayer developers are rude, condescending, and foul-mouthed. I think that is their right. They made it, they can do/say whatever they want about it. But I also think it is legitimate for people to then say "I don't want to associate with these people." And why should you have to, when there is an excellent alternative [sourceforge.net] that also plays Quicktime video (sans Sorenson), and comes in RPM format [puc-rio.br] for SuSE, Red Hat, and Mandrake. So you can get an equally-good player, with more courteous developers to back it up, and with no need to compile unless you enjoy that sort of thing. This is market competition at work, and it appears to me that Xine may be a winning alternative.
Re:I think the linuxworld guy expected far too muc (Score:2)
If it is beta software then I think they should be more up front about the beta-ness than simply having a sub 1.0 number and disuade non-coders from trying it before being as insulting as they can be _after_ they suffer through all this.
A direct quote of something else:
"Q: I'd like to compile MPlayer on Minix !
A: Me too."
What is the point of doing that? They could either be less terse or not have such a worthless item. I know it looks like a dumb request but they don't have to respond with dumb answers.
Re:Controversial? (Score:1)
No, they should merely be polite.
This is news? (Score:5, Insightful)
The only thing I can see is if they can use the Windows binary code to decode the Sorenson without the huge performance hit of running the entire player within a Wine context, and having the added benefit of XVideo availability for Sorenson playback. But it doesn't look like this will be the case.
More noteworthy is the VIVO support and xanim support, the VIVO support is a first (AFAIK) under linux natively, and the xanim support really helps bridge the gap between new and old-school media playback, xanim gets a lot of those files that have been overlooked in the "new wave" of media players for linux...
Also, another nit-pick, the crossover plugin, as such is not so much a player, but a nicely done wine modification within which the Windows Quicktime player runs... You can use the latest Wine CVS repository in much the same way (outside a browser at least).
Okay... (Score:4, Insightful)
Sorenson, of course, is owned by Apple, and they are as likely to make it open-source as Microsoft is to release the next Office under the GPL.
Now, mplayer will play
If you want QuickTime under Linux, with the Sorenson codec, your only option is Crossover (which works quite nicely, and has given me many minutes of movie-trailer viewing bliss).
Re:Okay... (Score:3, Informative)
And Wine CVS with the Quicktime player (basically what crossover is....) is a valid, free option.. I have verified it to work (though the UI is a bit quirky on redraw, the movie displays fine)... Of course it won't embed in a browser, but works fine stand alone...
Re:Okay... (Score:3, Informative)
The Sorenson codec is owned by Sorenson [sorenson.com] and Apple pays for it.
Re:Okay... (Score:1)
Apple effectively owns the Sorenson Codec.
Re:Okay... (Score:2)
Sorenson, of course, is owned by Apple, and they are as likely to make it open-source as Microsoft is to release the next Office under the GPL.
Now, mplayer will play
And the amusing thing is that:
1. A large number of the codec DLLs you need to run MPlayer and play those formats are owned by Microsoft, Intel, On2.com, etc etc etc.
2. MPlayer don't have the rights to distribute these codec DLLs in any form. Yet it's Microsoft code. (Check the win32-codecs file on their download site; look at the version info... it's all in there. They apparently stripped the copyright info from the DLLs, and that's it).
3. They've not paid the royalties on the patents either.
Isn't this llegal?
Simon
Xine does Quicktime too (Score:3, Informative)
hmm (Score:1, Interesting)
MPlayer ownz j00! (Score:1)
Its the first player i got DVDs to play with
and now its got QuickTime support.
These guys kick ass, quit your bitchin, and go
You dont need crossover! Wine runs quicktime! (Score:1)
arrogance (Score:1)
Let me quickly point out something: Red Hat Software has done a hell-of-a-lot more for free/OSS (and particularly Linux) than the developers in question have ever done.
Console-mode playback (Score:4, Insightful)
Re:Console-mode playback (Score:2)
All three: BIOS calls for VESA, SVGAlib for...VGA, and AAlib for true terminal. Of course AAlib is strictly text, but the quality is surprisingly good for a bunch of letters, to say the least.
and I just got.. (Score:2)
I do like the fact that this gives Linux yet another avenue for media. This added in with xmovie, gtv, quicktime under wine, xaniam, and now mplayer. I love choices..
Lets give Sorenson some feedback then (Score:2, Insightful)
Apple to move away from Sorenson, will support MP4 (Score:3, Informative)
CASANOVA: It's the center of our universe. The Sorenson video CODEC has been an integral part of QuickTime since we had QuickTime 3. Sorenson is exclusive to QuickTime, a proprietary format, that has just produced incredible quality both for download of movie trailers and real-time streaming over the Internet. They've done incredibly well. And we're going to continue working with the Sorenson guys. We're not shutting that off. And people will probably opt to use Sorenson in some cases. But certainly the center of the work we do is going to be around standards.
Everything Apple does--from the Unix bases of OS X, to FireWire being IEEE 1394, to USB to all the various facets of what we do, from AirPort being 802.11--we want to make sure that every piece of our architecture and infrastructure are based on industry standards. QuickTime is no different. Our streaming protocols are RTP/RTSP as defined by the IETS; and now
MPEG-4 continues the lineage of the MPEG family. MPEG-1
And the AAC audio component for music will likely replace MP3 as the default and brand new audio standard on the Web because I'll tell you what,
Earlier [last] week, with Real Networks announcing their support for MPEG-4, we found that to be a sudden and abrupt change in direction for them, but nonetheless a welcome one. We're really happy here at Apple, and as members of the Internet Streaming Media Alliance--the ISMA--we're really happy that Real had decided to make this change in course. Real is a big company, at least from an Internet media streaming perspective, and their stamp of approval on MPEG-4 gives the whole space more momentum.
The rest of the interview can be found here...
http://www.creativemac.com/2001/12_dec/features
Re:Apple to move away from Sorenson, will support (Score:2)
Because... (Score:3, Insightful)
Linux may be "superior" to Windows in one or more ways -- but what matters is being able to get the job done. And if I can't view a client's QT movie under Linux, Linus doesn't get the job done. And that's why it's important that Linux support QT...
Re:Because... (Score:1, Funny)
Cheers
Re:Why bother with Quicktime? (Score:2, Funny)
What a great idea! Why didn't I think of that? Next time I see some movie online that I'd like to watch, I'll just play it in my MPEG player regardless of how it was encoded by someone else!
Re:Why bother with Quicktime? (Score:3, Interesting)
There are several reasons the Quicktime format can be more useful than straight MPEG. One of the best (but sadly underused) features is text tracks [google.com], which allows subtitles, descriptors for the disabled, etc. Another is the ability to overlay static sprites (for example, TV channel logos) onto the video layer. This kind of stuff can improve image quality and save bandwidth at the same time.
Re:Why bother with Quicktime? (Score:1)
And can easily be removed ;)
Re:Why bother with Quicktime? (Score:1)
Re:Phil Donahue, liberal moron, kidnapped at 68 (Score:1, Funny)
:-)
Re:As much as I like Linux.... (Score:2)
Re:As much as I like Linux.... (Score:2)
But today, everything works:
So while I agree that it's not perfect yet, Linux certainly is no longer in the multimedia-darkage anymore. Sorenson is pretty much the only thing still not working. (unless you are willing to pay a small amount for Crossover, which I did)
BTW, I would recommend aviplay, it's friendlier than mplayer and included in most distributions.
[cough] (Score:1)
http://allmacintosh.xs4all.nl/preview/206564.html
http://www.afterdawn.com/software/video_software/
Re:As much as I like Linux.... (Score:1)