Google dropping H.264 from Chrome

by Volker Weber

we are changing Chrome's HTML5 <video> support to make it consistent with the codecs already supported by the open Chromium project. Specifically, we are supporting the WebM (VP8) and Theora video codecs, and will consider adding support for other high-quality open codecs in the future. Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies.

More >

Comments

Browser war is over. We now see the Codec war ...
That's bad news for all video publishers and video consumers.

Wolfgang schmidetzki, 2011-01-12 00:32

I hope this backfires for them. I do not care about the implications for the companies, I care for the users and I would personally hope this turns out to be a mistake for Google. Can't help it, fight your stupid wars elsewhere. I want it to work, and do not care how it works - it just has to work. I would even use Flash for crying out loud.
Disclaimers apply, and YMMV.

Alexander Koch, 2011-01-12 08:37

The discrepancy between what is written and what is said is awesome on that one. Obnoxious.

Frank Quednau, 2011-01-12 09:03

Maybe you guys need some further reading on this matter.

Volker Weber, 2011-01-12 10:32

as our goal is to enable open innovation

Will they drop the bundled, proprietary, flash player as well?

Jan-Piet Mens, 2011-01-12 12:07

Simon says ...

Volker Weber, 2011-01-12 15:01

I like this. Very clever move. H.264 patent restrictions makes it too dangerous to support.

The mess with H.264 licensing

Hanno Zulla, 2011-01-12 16:01

Think built-in hardware decode support for h.264. This translates into less of a drain on mobilie device battery life, console efficiency (can a tiny device like the AppleTV , etc. Everyone is still going to need to generate h.264, so this just adds more work for the content generators. They would need to generate h.264 and WebM, or only generate h.264, serve it straight to browsers that support it, and serve it via Flash to those that don't.

Kevan Emmott, 2011-01-12 16:14

@Kevan, see this long, but German response to your argument.

Hanno Zulla, 2011-01-12 17:15

Recent comments

Ben Lampe on 365 days at 10:55
Volker Weber on 365 days at 10:41
Patric Stiffel on 365 days at 10:39
Thomas Meyer on 365 days at 10:18
Volker Weber on BlackBerry improves the PRIV camera, again at 23:47
Frank Köhler on Sonos + Dyson + Surface = zufrieden at 23:14
Volker Weber on Sonos + Dyson + Surface = zufrieden at 19:46
Frank Köhler on Sonos + Dyson + Surface = zufrieden at 19:39
Richard Schwartz on Pebble is not folding its tent at 17:53
Markus Schäfer on Sonos + Dyson + Surface = zufrieden at 14:44
John Lindsay on Sonos + Dyson + Surface = zufrieden at 14:26
Markus Schäfer on Sonos + Dyson + Surface = zufrieden at 14:11
Thomas Lang on How fast is a Tesla Mommy Mobile? at 13:58
Hubert Stettner on Sonos + Dyson + Surface = zufrieden at 13:32
Hubert Stettner on BlackBerry improves the PRIV camera, again at 10:05
Hubert Stettner on BlackBerry improves the PRIV camera, again at 10:02
Jens Nullmeyer on How fast is a Tesla Mommy Mobile? at 09:04
Ralph Hammann on BlackBerry improves the PRIV camera, again at 07:31
Ole Saalmann on How fast is a Tesla Mommy Mobile? at 21:43
Volker Weber on How fast is a Tesla Mommy Mobile? at 18:34
Felix Binsack on How fast is a Tesla Mommy Mobile? at 18:31
Ole Saalmann on How fast is a Tesla Mommy Mobile? at 18:30
Natanael Mignon on How fast is a Tesla Mommy Mobile? at 16:25
Markus Dierker on How fast is a Tesla Mommy Mobile? at 16:22
Stefan Dorscht on How fast is a Tesla Mommy Mobile? at 15:57

Ceci n'est pas un blog

I explain difficult concepts in simple ways. For free, and for money. Clue procurement and bullshit detection.

vowe

Contact
Publications
Amazon Wish List
Frequently Asked Questions

rss feed  twitter ello  instagram

snapchat

Local time is 11:48

visitors.gif