> * Chrome was supposed to drop H264 support a >1 year ago in favor of WebM. It never happened.
This is pivotal. A big part of why WebM looked like it could win was Chrome's announced support for it and the dropping of H.264. It looks like Chrome has backtracked on that - over a year passed, no follow through on Chrome's promise to remove H.264 - so it is forcing Mozilla to reconsider it's position.
Does anyone know more about Chrome's current stance?
It could've been slowed down a lot if Google made Youtube in WebM by default by now. But they didn't, and that's probably because they don't think it's ready yet. Too bad. They might've missed their chance, or they will miss it if they don't do it very soon.
How was Google supposed to do that? Flash (still) doesn’t support WebM, so there wouldn’t be any fallback. Google surely isn’t arrogant enough to make YouTube videos not accessible to more than half of the browsers out there.
There was and still is no realistic way for Google to switch to WebM. Not exclusively. (Yes, they can also encode their videos in WebM but h.264 versions are always necessary.)
You don't remember what the original argumentation was. Firefox is free, Mozilla can't afford the patent licensing, that's all. If you own a h.264 license and want to use it with your software, feel free. By buying a phone or windows 7 you get the license to use a h.264 codec. Microsoft already brought support to Firefox ( http://www.osnews.com/story/24137/Microsoft_Brings_H264_to_F... ), now it's happening on Android. It's one thing to promote open standards - that's great and Firefox is doing that with WebM - but it's another thing to completely disregard existing capabilities and put the user back in the stone age of the internet.
You don't remember what the original argumentation was. Firefox is free, Mozilla can't afford the patent licensing, that's all.
This is still entirely true (note that "afford" in the above should be read in the "free license" context, not monetary). For the same reason, Chromium has no H264 support. Patented codecs don't mix well with free software. They took a stance here based on their philosophy, that much should have been obvious.
> You don't remember what the original argumentation was. Firefox is free, Mozilla can't afford the patent licensing, that's all.
IIRC, there were other reasons not to support using the OS codecs. H264 license fees are not an issue when you just use the codecs the OS provides, as they are already covered by the OS or codec vendor. With all the Google millions that Firefox gets each year, the license fee should not really be a problem anyway.
What I understand from it, is that it would take a lot of effort to use system codecs for different video formats, while still providing the complete set of HTML5 video functions for every format.
I never really bought this argument since IE, Safari and Chrome appear to handle this just fine, if you have Perian installed for example, you can even play HTML5 WebM directly from Safari. So I think we can safely conclude there were no other arguments for Mozilla's decision not to support H264 through system codecs, besides ideological ones.
Personally, I think this is great news. Everyone should just stop complaining about the supposed H264 patent issues, standardize on it, and move on. The patents have never been a problem and they never will, you only need to pay license fees if you make money off of H264, in which case you should just pay up, technology like this doesn't fall from trees. The moment WebM/VP8 would gain any traction at all on the internet, it would prove to be a patent minefield just like H264, as you simply cannot make a modern video codec without violating any patents these days.
Even if you accept the MPEG-LA's assurances that there are no practical issues with H.264 decoders (and it is worth noting that the terms for decoders almost certainly wouldn't be as generous as they currently are without the pressure created by WebM), that was never the fundamental problem.
The real issue with the H.264 patents and why it is anathema to any libre ecosystem is the impact of the H.264 patents on video creation, encoding and distribution. Here's a thorough discussion of the issues (created by someone who actually took a substantial amount of time to talk to a representative of the MPEG-LA for clarification):
"Related to point #2, it may not be possible to release an H.264-encoded video under, for example, a Creative Commons license that allows commercial usage. More precisely, should you release your H.264-encoded content under such a license, it would not be legally usable under such a license. This cuts out a large portion of options related to how you may share your creative content."
I find the idea that we should standardize on a video codec with that sort of usage restriction completely incomprehensible. I just do not understand how people can accept a data format whose licensing doesn't just constrain people who produce encoders, decoders and other related tools and technology, but also constrains end users.
Firefox may be free, but Mozilla is not poor. Their foundation received about $120 million last year. In their most recent negotiation with Google, it was reported that Mozilla would receive $1 billion over the next 3 years from search engine fees.
They can probably afford to pay the license for themselves, but Firefox is "libre" software, licensed (among others) under the GPL. If Firefox requires an H264 license to be usable, it's not a real open source project any more.
Mozilla certainly have the ability, but I agree that for principle's sake they shouldn't license it.
I would modify what you've said, software can be open source and be totally laden with patents, but free software (especially GPLv3) probably can't.
Continuing my argument: Claiming Mozilla are poor as the GP did is a bad argument. Claiming that the software can't be re-distributed is a slightly less bad argument, but only for larger distributions.
The pool sets certain payment stages. If your distribution of the codec has fewer than 100,000 users there is no license fee payable at all.
Also ,the license fee for h.264 is capped at $6.5 million, so Firefox can distribute it to anyone and any smaller project (less than 100,000 users) can distribute it as well.
It's the mid-sized redistributions that can have trouble, because they will lack Mozilla's money but have larger user bases that might trigger the fees.
In fact, even if Mozilla did pay a non-royalty-free patent license to include the codecs in Firefox, that license would probably be incompatible with the GPL/LGPL, meaning it would no longer be possible to distribute Firefox under its current MPL/GPL/LGPL tri-license. (I don't know the MPL well enough to know whether Firefox would still be distributable under the MPL alone.)
They made their position. Obviously, no one except them (and possibly Opera) cares enough about the problems they pointed out with h.264. There's no point is fighting a lost battle and lose most of their user-base over it.
This is on Android initially. Cheaper android devices (anything less than ~ 200 dollars) don't ship with H264 decoders built it, nor does Cyanogenmod. You have to install something off the Market, which is hard since they're often chipset/ARM version specific...
mozplugger has long played every media format ever by hooking into system ffmpeg/mplayer tooling, on firefox/iceweasel. likewise most minimalist webkit wrapers (midori, surf) just seem to use gstreamer/ffmpeg too, which has clean-roomed free support of even nasty old codecs like realvideo. arguing over what is officialy 'shipped' when the browser supports plugins, Xembed and so on is kind of a pointless tempest in a teapot