| |||||||||||||
There's an app for thatThere's an app for thatPosted Jan 17, 2011 13:00 UTC (Mon) by cesarb (subscriber, #6266)In reply to: More about the Chrome HTML Video Codec Change (The Chromium Blog) by jmorris42 Parent article: More about the Chrome HTML Video Codec Change (The Chromium Blog)
iOS does not have to be left out. If its browser does not support WebM, Google could simply create a "YouTube Viewer" application which includes optimized software decoding for WebM (possibly using an ARM-optimized version of the ffmpeg VP8 decoder, which is already faster than Google's own reference decoder).
Yes, it will use more battery, but it is a small price to pay (and most users will not notice unless they play a lot of videos).
(Log in to post comments)
There's an app for that Posted Jan 17, 2011 13:17 UTC (Mon) by bawjaws (guest, #56952) [Link]
Was the ffmpeg decoder actually faster on ARM? I was under the impression that it was "faster" because they tweaked it for desktop chips whereas the original code was designed and coded to be fast on mobile ARM chips, specifically those with NEON SIMD (like every iPhone since the 3GS). I think I saw something claiming that ffmpeg code was faster than Google's code on ARM as long as you disabled the ARM specific assembly but that's a somewhat limited victory.
I'd be interested to know how fast a 3rd party WebM decode could go on an iPhone. From the example of Theora it sounds like it can depend on some very arcane details of how the hardware is set up. I guess we'll get some kind of numbers on that when Android 2.3 starts rolling out wider.
|
|||||||||||||