Comments Locked

14 Comments

Back to Article

  • DanNeely - Tuesday, September 8, 2015 - link

    The risk with VP9/10 is that if it threatens to displace HEVC in a major portion of the market, the same companies that are trying to squeeze a lot more money out of HEVC than H264 will probably come out suing claiming that VP9/10 infringe on their patents. Google can absorb the litigation risk, but when smaller entities are given the choice between paying $Lots to switch to HEVC and take a license, paying $SeveralTimesMore for the trolls license to use their patents on VP9/10 (ofc they'll demand more in this case, since shifting users to HEVC is their objective), or $MakesTheLastNumberLookSmall to litigate it; most will probably fold.
  • Mondozai - Tuesday, September 8, 2015 - link

    Not really Dan.

    The people behind HEVC are companies like Comcast, Time Warner and others. These people are notoriously against progress.

    Google, Netflix and others have always had a much more favourable stance towards Open Source. There are no guarantees in this world, but let's not fool ourselves that the risk here is the same. To see the development of these codecs being led by progressive IT companies rather than reactive placeholders is absolutely a great development.

    The faster we can bury HEVC the better. Google has already shown that they can develop new codecs that much faster on their own, imagine what they can do together with all these other companies. We need this if we are going to get 4K streaming at bandwidth rates that are doable. 20+ mbit/s for 60 fps@4K isn't sustainable if it will ever get broad adoption. We got to push down below 10 mbit/s for that and they - and only they - can do it.
  • Michael Bay - Wednesday, September 9, 2015 - link

    >muh progress

    Are you enjoying your displacement yet, whitey?
  • wicketr - Tuesday, September 8, 2015 - link

    This is huge news as Chrome (obviously) and Firefox (likely) will support it. That's about 90% of the desktop market. And with Android, they'll have at least 50% of the web market covered. Over the next few years, I would imagine most chips will support it as well.

    Apple will likely be the last holdout in all this.
  • Ken_g6 - Tuesday, September 8, 2015 - link

    "Over the past couple of years the WebM container has become something of a de facto successor to animated GIFs as it allows for clips that run for several minutes to be put into a relatively good quality file with a small size, and doesn't suffer from the 256 color limit of standard animated GIFs."

    Can I put it in an <img> tag? Or a [img]...[/img] in a forum? Until I can, it's not a successor to GIFs.
  • tuqueque - Tuesday, September 8, 2015 - link

    There seems to be a major mistake/misunderstanding with VP9, VP8, WebM and WebP here... WebM is the container for videos, usually with VP8 and now mainly VP9... OTOH, similar to WebM/VP9, WebP is the image formar proposed by Google for images on the web; it tries to replace Jpeg, Gif and Png altogether with a single format with all of the advantages of them all (plus a few other ones). WebP is based on VP8 tech, but since its appearance, has implemented several specific stuff to make it much more robust and versatile.
  • Brandon Chester - Tuesday, September 8, 2015 - link

    If you go to 4chan or imgur you'll see WebM being used in the place of GIFs. WebP has no decent browser support.
  • nandnandnand - Tuesday, September 8, 2015 - link

    There's also a similar image format using HEVC/H.265:
    https://en.wikipedia.org/wiki/High_Efficiency_Vide...
  • Sttm - Tuesday, September 8, 2015 - link

    Thats cool and all but when is it getting AdBlock and Last Pass so I would actually use it?
  • r3loaded - Tuesday, September 8, 2015 - link

    Great, now if only Apple would support it. Oh, and hardware decoding (particularly in x86 land, I'm aware the Tegra X1 supports it in fixed-function pipelines) would be nice too. I've had to install the h264ify extension on my MBP, otherwise YouTube insists on serving VP9 video to me. This video is then decoded in software on the CPU, causing the fans to spin up like mad. Meanwhile, even 4K H.264 video plays smoothly and without heating up the computer.
  • Nintendo Maniac 64 - Tuesday, September 8, 2015 - link

    I do believe that that AMD's belief that prioritizing hardware decoding for HEVC rather than VP9 in Carrizo was a mistake...

    Of course, this actually gives the benefit of being able to decode both HEVC and VP9 seeing how Windows 10 doesn't support software decoding of HEVC (it only supports hardware-accelerated decoding).
  • Morawka - Wednesday, September 9, 2015 - link

    Good luck to google.. HEVC already has wide adoption and 35 of the Fortune 100 tech companies already have licensing agreements. Nvidia already has HEVC encoder/decoder's built into maxwell GPU's.

    HEVC has definately got a leg up on vp9.. The only hope google has is the fact that it's royalty free. VP9 requires much more encoding horsepower, and it's compression is close to HEVC, but HEVC still edges it out on a wide range of content dimensions.

    http://www.tvtechnology.com/news/0086/hevc-vs-vp-w...
  • extide - Wednesday, September 9, 2015 - link

    Yeah the problem is Google cannot use some of the advanced methods HEVC does because they are patented. It would be better for everyone if HEVC and it's patents didn't exist at all, or both teams actually worked together, but sadly we all know that will never happen :(

Log in

Don't have an account? Sign up now