Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Chromium Google Media Youtube

Google Enables VP9 Video Codec In Chromium 161

An anonymous reader writes "Last month, Google revealed that it was planning to finish defining its VP9 video codec on June 17 (today), after which it will start using the next-generation compression technology in Chrome and on YouTube. The company is wasting no time: it has already enabled the free video compression standard by default in the latest Chromium build."
This discussion has been archived. No new comments can be posted.

Google Enables VP9 Video Codec In Chromium

Comments Filter:
  • It's... OK. (Score:5, Insightful)

    by Guspaz ( 556486 ) on Tuesday June 18, 2013 @12:35AM (#44036505)

    It's not the disaster that VP8 was (which looked like a codec from 10+ years ago), but it seems to be at best in the same ballpark as x264. VP9 isn't really a viable replacement for h.265, but it might do better than their last attempt merely by not being a laughable joke like VP8.

    Mind you, I'm not saying VP8 is bad in and of itself. I certainly couldn't do better. But Google promoted it as being superior to h.264, which was an absurd assertion, hence the derision.

  • Re:Firefox support (Score:4, Insightful)

    by wvmarle ( 1070040 ) on Tuesday June 18, 2013 @02:02AM (#44036803)

    This allows you as much to move away from Flash as the current built-in support for H264 and other codecs. So until the Flash-based player UI is replaced by an HTML-based player UI, nothing will change.

    And you can for many years already watch YouTube videos without using Flash plugin in your browser.

  • by Camembert ( 2891457 ) on Tuesday June 18, 2013 @02:15AM (#44036849)
    It may be a technically good codec (I have no strong opinion on that either way). But I see issues with the many devices (tablets, bluray players with usb input, set top boxes, phones...) available whose graphical processors are totally geared towards implementations of mp4 and h264. For example, I understand that an iphone would do battery-efficient hardware decoding of such files. I assume that dfor this new codec the processor will need to do all the work, with likely a much bigger impact on the battery.
  • Chromium? (Score:0, Insightful)

    by Anonymous Coward on Tuesday June 18, 2013 @02:36AM (#44036921)

    More like SpyingOnYouAllTheTimeium, amirite?

  • by Camael ( 1048726 ) on Tuesday June 18, 2013 @02:45AM (#44036943)

    I don't disagree with you on the merits of the x264 encoder (open source, etc) but are you sure that x.264 is free? Because it seems from this webpage that you need to pay for a licence to use it [x264licensing.com].

    Also, from the H.264 standard itself is not free [engadget.com]. The party who makes the encoder and the party who distributes the encoded file to the end users for commercial use has to pay for licensing.

    Although H.264 is an open standard, in that it was developed by a consortium of companies and anyone can make and sell an encoder or decoder, it's not free -- you've got to pay for a royalty fee to use it, and the rates are set by the MPEG-LA, which collects payments and distributes them to its members.

    V8 and V9 are not the same. V8 itself may have a bad history and be a crap codec, performance wise. Is V9 a bad codec as well, performance wise? Has Google done anything that justifies the wholesale boycott of V9?

  • Comment removed (Score:4, Insightful)

    by account_deleted ( 4530225 ) on Tuesday June 18, 2013 @02:52AM (#44036961)
    Comment removed based on user account deletion
  • by SuricouRaven ( 1897204 ) on Tuesday June 18, 2013 @02:53AM (#44036965)

    h264 would be ideal, if not for the patent issue. That's a real deal-breaker for many. It's why Firefox doesn't have support for h264 video - even if they applied for a license, they wouldn't then be able to sub-license to developers who want to fork the project, which is incompatible with the open-source development model.

  • Re:It's... OK. (Score:5, Insightful)

    by VirtualVirtuality ( 2895477 ) on Tuesday June 18, 2013 @03:14AM (#44037009)

    Ehh, what 'big settlement' did Google pay? Google and MPEG LA announced an agreement, there's been no disclosure of any big settlement, and I seriously doubt there was one.

    MPEG LA was actively looking (as in advertising for) any patents which could be used as a patent pool against VP8, and had they actually managed to create a strong portfolio then I don't think we'd ever seen this agreement take place. Also, given how long On2 (the company Google bought for their codec technology) have been active in video compression aswell as the patents they hold, it's not as if Google is just entering the video compression arena from scratch, and they may very well hold patents on which h264 and h265 could be found infringing.

    And as far as licencing costs, there's no indemnification from patent trolls with MPEG LA licencing either, and MPEG LA's saber rattling turned out to be just that, no 'massive liabilities' ended up facing anyone.

    This notion you try to sell that you would somehow be 'safe' with MPEG LA licencing, while opening yourself up to 'massive liabilities' if you use VP8/VP9 is just typical scare tactics as I see it.

    Now I don't think VP9 will be quite as good as h265, but that's not really important. The important thing is that MPEG LA won't be able to corner the entire online video compression market, and that there is an actual competitive alternative (and that this competition is also open source and royalty free is a huge bonus).

    Because the day there isn't, the companies who make up MPEG LA will start to collect heavily on their investments, massive-greed style. Which in turn will affect us end users as the increased cost will inevitably be shifted unto us, one way or another.

    Furthermore it will lead to stagnation, as in: 'we will bleed this technology dry before we introduce the next generation', all in an effort to maximize profit with less effort.

    So yay for VP9, may it (and it's later incarnations) live long and prosper.

  • by Telvin_3d ( 855514 ) on Tuesday June 18, 2013 @03:48AM (#44037101)

    Great, so it's the fault of the manufacturers. But seeing as VP9 takes several times more processing power to decode in software than VP8, which would you serve up to a mobile phone: h265 that has hardware decode or VP9 that provides the exact same video quality/size but will choke on playback even as the battery life drops by the second?

    The difference isn't in quality of the codec, it's the quality of support. One has a massive group that has spent a decade making sure that it is supported by everyone everywhere. The other has been tossed out into the public by a single company without any cooperation or support by other parties.

  • by MrMickS ( 568778 ) on Tuesday June 18, 2013 @04:11AM (#44037159) Homepage Journal

    Now, neither AMD or NVIDIA provide VP8 decompression - support, so obviously H/W - accelerated H.264 will be faster, but that's not the fault of the codec, it's the fault of the manufacturers.

    That's an interesting spin on the situation. It's not the fault of the manufacturers. Its that h264 was designed by an industry body that included the manufacturers with the intention of creating a single common codec to use across different applications and devices. VP8 was designed by a single entity to reduce its costs without giving a damn for end user experience as they could offload that to the bad manufacturers for not supporting it in hardware.

  • Re:It's... OK. (Score:1, Insightful)

    by mrt_2394871 ( 1174545 ) on Tuesday June 18, 2013 @04:42AM (#44037237)

    ... why bother? ...

    If VP9 wasn't there, H265 would face no competition. So then the H265 consortium would be able to pull all sorts of egregious crap. End-user licence fees, mandatory unskippable ads, you name it, they could require it.

    But VP9 does exist. So they very probably won't.

Any circuit design must contain at least one part which is obsolete, two parts which are unobtainable, and three parts which are still under development.

Working...