Chrome dropping h.264 support

Out of context: Reply #15

  • Started
  • Last post
  • 42 Responses
  • abettertomorrow0

    I thought Gruber is dead on in his appraisal of what will actually happen (and he didn't seem to be shitting nor fellating anyone Boz:).

    http://daringfireball.net/linked…

    A bold move, to be sure. H.264 is widely used. WebM and Theora aren’t. Perhaps this move will push more publishers toward serving video encoded with WebM. The big problem WebM has versus H.264 is that there are hardware decoders for H.264. This is key for mobile devices. It’s the hardware video decoding that allows mobile devices to get such long battery life and smooth performance for video playback. There’s no way publishers can drop H.264. To support Chrome, they’d have to add WebM-encoded versions of each video.

    My bet is that this is just going to push publishers toward forcing Chrome users to use Flash for video playback — and that the video that gets sent to Flash Player will be encoded as H.264. Google can fix this for YouTube on its own, and admittedly, that covers an awful lot of web video. But I think everywhere else, H.264 will continue to dominate, and instead of getting native playback, Chrome users will get playback through Flash. This should be great for Chrome OS laptop battery life.

View thread