News for hackers. Stuff that matters.

A comment on WebM-Enabled Browser Usage Share Exceeds H.264-Enabled ones. Parent comment

Re:WebM-Enabled Browser Usage Share Exceeds H.264-Enabled ones by cpeterso on Saturday January 21, 2012 @02:13PM (#3494293)
The battery savings can vary greatly depending on many hardware issues. The Nexus One, for instance, had some serious limitations.

I wrote some Android video software comparing performance of hardware and software decoders for H.264 and AAC. The Nexus One's H.264 hardware decoder used 2x more battery than a software decoder (for much less than 2x frame rate improvement). Further testing suggested that the power usage of moving video data to and from the hardware decoder outweighed any savings from overloading the CPU.

And the Nexus One's AAC hardware decoder was slower than a software decoder.

[ Parent | on HN ]
Re:WebM-Enabled Browser Usage Share Exceeds H.264-Enabled ones by zdw on Saturday January 21, 2012 @05:13PM (#3494816)
Hmm... on most desktop platforms, the decode happens in the GPU, and the flow is:

storage/network -> CPU -> GPU -> Screen

It sounds like on the Nexus One, there's some copy back into the CPU before it gets to the screen. In the version of the OS is Android doing graphics compositing in it's CPU?

I'd love to see references for this.

[ Parent | on HN ]