Slashdot Mirror


Google To Drop Support For H.264 In Chrome

Steve writes "Google just made a bold move in the HTML5 video tag battle: even though H.264 is widely used and WebM is not, the search giant has announced it will drop support for the former in Chrome. The company has not done so yet, but it has promised it will in the next couple of months. Google wants to give content publishers and developers using the HTML5 video tag an opportunity to make any necessary changes to their websites."

16 of 765 comments (clear)

  1. Market Share? by JohnG · · Score: 5, Insightful

    Does Chrome really have the market share required for this move to have any effect on the decisions of web designers?

    1. Re:Market Share? by diegocg · · Score: 5, Informative

      Yes, note that firefox doen't ship H.264 either. In Europe, Firefox + Chrome share is 52.69%, IE 37.52%.

      Also, Google owns Youtube and is working to make every video available in VP8.

    2. Re:Market Share? by suv4x4 · · Score: 5, Insightful

      Does Chrome really have the market share required for this move to have any effect on the decisions of web designers?

      Yes. Chrome is rapidly eating market share: in just about 2 years since launch, it's at 13.5%. This is twice the share of Opera and Safari combined. But the decision to drop H.264 doesn't put Chrome "versus the world", as they already had Firefox and Opera in their camp (which also lack H.264). Opera + Safari + Chrome make over 50% of the browsers used today, in market share.

      This is substantially different than the previous situation, where Google, Microsoft and Apple all had a H.264 browser, and Firefox looked like the odd one out, while Opera was quietly awaiting the market to decide (they'd have no choice but support H.264, if Firefox did it).

      However, the battle is still not over for H.264. The common wisdom is that Google is pushing their WebM standard and that's why they drop H.264. If they really think it's that simple, they have not done their math right.

      The growth is with mobile devices. The leaders among them is Apple with iOS, and Google with Android, both of which come with hardware support for H.264, and no WebM hardware support (future support in... theory, but I can say, count Apple out). So what are web content owners left to do? Maybe encode all content twice: WebM and then H.264. Imagine the hassle of, ironically Google's very own, YouTube, having YET another version of every single video they have in their library: FLV, H.264 and now WebM.

      No, actually web authors will opt for the simplest choice, that's least amount of work: the same H.264 video everywhere, making use of hardware support for H.264 in mobiles, exposed via HTML5, and ... Flash on the desktop, which also support exactly the same H.264 videos.

      So, in attempt to push WebM, Google may end up accidentally (or not..?) cementing Flash's position on the desktop as the video player for the foreseeable future.

      I used to think Flash will considerably fade away once IE9 becomes mainstream (which comes with GPU accelerated renderer and H264 support), but now things are suddenly interesting again for Adobe.

  2. Re:Open standards by msauve · · Score: 5, Insightful

    And the open alternative to Flash is....? (Other than the subset provided by HTML5/WebM)

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  3. Chrome+Firefox by mrsam · · Score: 5, Interesting

    Google is obviously betting that WebM in Chrome and Firefox can carry enough weight to compete against H.264 in MSIE, Opera, and Safari.

    Google, obviously, has enough web-surfing based data to factor into this judgement call. Whether or not Google is right on this call, one thing is certain: Google wouldn't do this unless they were fairly confident in WebM's chances against the looming patent trolls.

    This, I think, is the noteworthy aspect of this bit of news. A patent troll going after WebM will now have to expect to have to deal with Google's well-funded lawyers.

    1. Re:Chrome+Firefox by synnack · · Score: 5, Informative

      Actually, Opera also supports WebM, so using VP8 only will get you Firefox, Chrome and Opera, wich is over 60% of the market.

  4. Re:Pretty soon... by tweak13 · · Score: 5, Informative

    It doesn't get around it. Unless you live somewhere enlightened enough to not allow software patents, it probably isn't legal to use without a license for the patented tech.

  5. Re:Great! Less choice! by poetmatt · · Score: 5, Insightful

    or the reality of "We've decided to stop supporting formats for things that aren't free", would be a more simple answer.

  6. Re:A really nasty trick by Anonymous Coward · · Score: 5, Insightful

    Will people please stop citing an x264 developer's rant as an "expert opinion" on the video quality or patent risks of WebM? Next thing we'll indulge the musings of a Coca-Cola Company executive on health issues related to PepsiCo products.

  7. You lost me by KingSkippus · · Score: 5, Insightful

    H.264 is not a free codec and consequently, you have to pay if you wish to encode content in it or decode content encoded with it. They just are gracious enough not to charge you for streaming it. Consequently, it's not supported by Firefox natively nor in any other browser that cares about being sued and can't or won't pay.

    Google's motivation is obviously to try to establish an open source, free (as in speech) codec as the web standard for video. That way, we won't have the silly issues you mention above. So why are you not happy with this move?

    Keep in mind that browsers like Firefox, Konquerer, Seamonkey, etc., because they are open source, cannot legally integrate H.264 into its browser. On the other hand, there is nothing stopping Microsoft, Apple, Opera, and Google, and anyone else who wants to from integrating WebM into their browsers. It simply boils down to an administrative decision to do so.

    So if you want your web-based video to "Just Work," you absolutely must support WebM. Or more precisely, you absolutely must not support H.264 unless MPEG releases it to the public domain or under a free (as in speech) license, which I think there's exactly zero chance of happening.

    1. Re:You lost me by Bogtha · · Score: 5, Insightful

      If the Mozilla foundation wanted to support H.264, they'd release a plug-in that ties into codecs installed on the system.

      MS did exactly this.

      Of course Microsoft did that. That's exactly what they want. If Firefox did that too, then you'd end up with the situation where Firefox users running on Windows would be able to view H.264 and Firefox users on a Free operating system would not. And all the websites with "Firefox" as a tick box on their compatibility checklist would happily tick it and be on their merry way. Meanwhile, bye-bye cross-platform web. Can't possibly think why Microsoft would like that and Mozilla wouldn't.

      --
      Bogtha Bogtha Bogtha
  8. Re:Pretty soon... by KingSkippus · · Score: 5, Interesting

    What makes this decision even more annoying is that Google are part of the H264 patent pool. They have more to lose by removing support for it.

    No, they don't. Can you imagine how much better life would have been had PNG been established early as the de facto image standard on the Internet instead of GIF, and later, JPG? Aside from the superior feature set, there never would have been any of the silly threats of massive lawsuits, no need to pay someone royalties to implement an editor, etc.

    Google isn't just smart, it is freakin' brilliant with this move. If they can help to establish WebM as the de facto standard for Internet video, they don't have to be part of the H.264 patent pool. Also, people can write video editors and other utilities galore for Chrome with no viable threat of being sued.

  9. Re:H.264 is dirt cheap. H.264 is everywhere. by 10101001+10101001 · · Score: 5, Interesting

    The maximum bite for an encoder/decoder is 20 cents a unit.

    And with a maximal of 6 billion units, that works out to around 1.2 billion (ignoring things like having multiple units (one on the computer, one on the smart phone, one on the game system, etc)). Care to pay that for everyone?

    MPEG LA is geared for licensing production and distribution of H.264 video on a commercial scale. They don't give a damn about your wedding videos until you become a national franchise.

    Ie, if I put my wedding video on youtube in H.264 and it becomes popular and gets 2 million page views, I'll risk having to pay $40,000? Golly, I wonder why anyone would have a problem with that.

    They don't give a damn about the geek's freely distributed Star Trek fan-flick.

    Unless the website hosting it has ads of any sort; then it's commercial.

    The Enterprise Cap for H.264 in 2011 is $6.5 million a year. H.264 is deeply entrenched in theatrical production. Broadcast, cable and satellite distribution. Industrial and military applications. Home video.

    Which begs the question, why isn't licensing such that Google, Firefox, etc don't have to pay? It's certainly not like MPEG LA is getting insufficient money. The simple point is, MPEG LA wants the chance to spread into the online world to make even more money. I can appreciate this. But, when you start counting the possibly millions or even billions of units to be sold in the future, that "dirt cheap" is no longer dirt cheap--why else would the per unit rate be so low, anyways?

    The simple truth is, allowing H.264 to effectively tax all internet-video devices is one of those anti-free market things that will only slow down innovation and growth. It's no different than any other pervasive fee in a system.

    --
    Eurohacker European paranoia, gun rights, and h
  10. Re:Great! Less choice! by lennier · · Score: 5, Insightful

    Except H.264 is the best codec. Google didn't choose WebM because it's better, they chose it because they own it and (purportedly) because it's open. They did not choose it for being a high-quality codec, they chose it for entirely meta and political/ideological reasons.

    Yes. The chief of those meta issues being that distributing any Free Software implementation of H.264 in the United States of America is illegal due to software patent law.

    I don't know about you, but where I come from, not getting arrested is a pretty good driver of technology choices, and yes, does tend to trump 'quality' issues. A slightly higher-quality video codec, distribution of which breaks the law, is not even a starter. It simply cannot compete with WebM in the GPL-derived software market at all.

    It's certainly very sad that the makers of H.264 have deliierately put their product outside the realm of rational economic choice by using the big patent gun to make its distribution in GPL-compliant form flatly illegal, but, well. Destroying a whole class of potential users of their own product was their choice, even if it wasn't a sane one.

    Google, however, have only one economically rational law-abiding choice left open to them if they want to distribute a GPL-derived media player, and that's to use anything but H.264.

    I admit I find it rather strange that you consider legality to be a mere 'meta' issue. Do you regularly break the law in your daily business life, and expect others to?

    --
    You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
  11. Re:Pretty soon... by commodore64_love · · Score: 5, Insightful

    >>>a decent browser will have a full screen option.

    Way to completely-and-totally miss his point. Yes the browser has a FS option, but it requires users to take a two-step option (first blow video to fill the browser; then make the browser full screen). The Grandparent poster said that's a pain in the ass, and he would be correct. Especially since many of us users don't know how to do full screen in our browsers. The old way was better (a single click via javascript).

    --
    "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
  12. Re:Great! Less choice! by boxwood · · Score: 5, Insightful

    It's short term vs. long term thinking. We can have a slightly better codec thats got a thousand patents on it or we can have one that isn't patented. We are talking about a very slight difference in quality here.

    Yes the patented codec may be slightly better now, but if an open codec becomes the standard then in the long term we're better off as it will be easier for people to make improvements to it.

    With a patented codec we have to pay. Sure it may be cheap now, but further improvements to it will also be patented which means it will never be free. And over time the price will rise and it will become less likely anyone will be able to come up with a codec to compete with it, not because no one else has the skill to do so, but simply because it will be illegal because of the patents.

    We have an opportunity to get free of all of this. Yes we have to sacrifice a small amount of quality today. And it is a very small difference in quality we're talking about. But if WebM becomes the standard then you'll have a lot of companies working to improve it. if H.264 becomes the standard a lot of companies will work to improve it. The difference is that one will be patented and the other won't.