Jump to content

Google To Remove H.264 Support From Chrome


Lancer
 Share

Recommended Posts

In a move to encourage support for royalty-free codecs on the Web, Google announced this morning that it will remove the patent-encumbered H.264 codec from future versions of its Chrome Web browser. This new twist in the video codec debate could help accelerate adoption of Google's own WebM format, but it will also compound the technical challenges faced by content producers who want to use standards-based video to reach a broad audience on the Web.

More...

Used on Blu-ray discs and supported across a wide range of mainstream consumer electronics devices, the H.264 codec is the current de facto industry standard for encoding digital video. Although H.264 has many technical advantages, Web standards advocates oppose using it as the standard format for the HTML5 video tag. The underlying compression mechanisms in H.264 are patented and adopters have to pay royalties to a licensing consortium called MPEG-LA. Standards advocates view this patent encumbrance as undesirable for the Web. In an effort to provide a viable open alternative to H.264, Google acquired video technology company On2 and opened up the company's competitive VP8 codec, creating a new royalty-free media format called WebM. Support for WebM has since been added to Firefox, Opera, and Chrome. Microsoft and Apple have declined to adopt the new royalty-free format, however, and have remained committed to supporting H.264 in their browsers. Apple favors H.264 because its quality is still considered technically superior and because it already has robust hardware-accelerated decoding support on Apple's popular devices.

Google appeared to favor the pragmatic approach and had opted to support both formats in its own browser, but is now moving towards a fully open approach. In a post on the official Chromium blog, Google says that the benefits of an open format outweigh the pragmatic advantages of supporting H.264. The company believes that innovation, in the long term, will be best served by an open technology ecosystem.

The move will resonate strongly with standards enthusiasts, but it won't help reduce the complexity of the HTML5 video landscape. The split between H.264 and WebM poses some challenges for content producers. Companies that want to use HTML5 to display video on the Internet will likely have to support both codecs in order to reach the broadest possible audience. Microsoft's substantial browser market share and the popularity of Apple's devices simply can't be ignored by content producers. It's likely that many content producers will continue using H.264 and will simply use Flash instead of the HTML5 video tag to display video content to browsers that don't natively support the H.264 codec.

Although Google is taking a forceful position in favor of open codecs in its browser, it's not clear yet if this principled attitude will carry over to other aspects of Google's Web strategy. It seemingly contradicts the company's pragmatic complacency on the issue of proprietary browser plug-ins. It's also unclear if Google's newfound commitment to pushing open video formats will cause the company to rethink its support for H.264 on its popular YouTube website.

@Ars Technica

Link to comment
Share on other sites

Num topico sobre o google tinha dito que não tinha uma confiança cega na google, que neste mundo nada é de borla e que tudo se paga duma maneira ou doutra, e que a google já chegou a criar umas certas polemicas, resultado, fui gozado, insultado e por fim banido do topico.

Ken Thompson, cientista de renome que é efectivo na google disse :

"You can't trust code that you did not totally create yourself. Especially code from companies that employ people like me."

Se eles querem tanto defender o open source, porque não usam o x264 que já está mais que estabelecido?

Aqui há gato...

Link to comment
Share on other sites

Num topico sobre o google tinha dito que não tinha uma confiança cega na google, que neste mundo nada é de borla e que tudo se paga duma maneira ou doutra, e que a google já chegou a criar umas certas polemicas, resultado, fui gozado, insultado e por fim banido do topico.

Ken Thompson, cientista de renome que é efectivo na google disse :

"You can't trust code that you did not totally create yourself. Especially code from companies that employ people like me."

Se eles querem tanto defender o open source, porque não usam o x264 que já está mais que estabelecido?

Aqui há gato...

x264 não é opensource, tem patentes por trás, e só podes usar porque disseram que os users finais podem usar à borla até ao ano não sei quantos. Basta lembrarem-se e de repente puffs, toda a gente tem de pagar pa usar. E só é free pa users finais, quem cria conteudo tem de pagar.

É uma assunto mais que discutido na net, ja vejo se arranjo o raio dos links da fsf e outros onde o assunto ta bem explicado para quem não anda muito dentro do assunto.

EDIT: http://www.fsf.org/news/supporting-webm

Edited by AnDr3w_RvNgR
Link to comment
Share on other sites

x264 não é opensource, tem patentes por trás, e só podes usar porque disseram que os users finais podem usar à borla até ao ano não sei quantos. Basta lembrarem-se e de repente puffs, toda a gente tem de pagar pa usar. E só é free pa users finais, quem cria conteudo tem de pagar.

Auraite, já aprendi uma coisa hoje. Como quando faço compressão em x264 nunca me apareceu nada a pedir cenas como com o divx e que os rips HD são todos em x264 não pensei que fosse patenteado, mas prontos eu sou um particular e os grupos de releases operam em submarino, mas imagino que uma empresa estabelecida podia ser cobrada pelos patenteares.

Copyright kills culture, it´s a fucked up world ruled by money... :no:

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.