5 ms·
This ignores the fact that H.264 often has full hardware acceleration in the CPU or GPU of nearly all modern desktop and mobile platforms, which also covers set
by zdw 15y ago
This ignores the fact that H.264 often has full hardware acceleration in the CPU or GPU of nearly all modern desktop and mobile platforms, which also covers set top streaming devices.
WebM can often use some portions of this (colorspace conversion, etc.) but until the entire stack is natively supported, there will always be battery life advantages to using H.264.
Not to knock WebM - there are projects out there to implement encode/decode in hardware (http://www.webmproject.org/hardware/ http://www.webmproject.org/hardware/ for one example) - they're just lagging about 5 years behind H.264 in this, and getting CPU/GPU vendors to dedicate space on a chip to a less codified standard will be difficult at best.
- asomiv 15y agoI keep hearing this battery life thing but how much battery life does H264 hardware acceleration really save? I dare to wager that the majority of the power is used by the screen, not the CPU.
- dchest 15y agoAccording to this blog post http://blog.webmproject.org/2011/12/picking-right-driver.html http://blog.webmproject.org/2011/12/picking-right-driver.htm... the difference between WebM in software vs WebM in hardware is around 36%. There's also a nice graph that shows that on high brightness, the difference is smaller.
- cpeterso 15y agoThe 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.
- zdw 15y agoHmm... 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.
- dchest 15y agoThis ignores the fact that H.264 often has full hardware acceleration... Yes, the rise of WebM-enabled browser market share ignores this fact.
- joesb 15y agoActually, yes. To be more precise, the rise of WebM-enabled browser market share ignores its WebM altogether. People use Chrome or Firefox because it's faster than IE, it has automatic update, it supports more CSS3 features (i.e. it renders more beautiful web site). I never once heard people choosing Chrome/FF over IE/Safari because of WebM. Don't forget that all this browser still support flash with H.264 codec and most website still have flash video fallback. Hell, most website only use Flash video player. It might just well be the article about rising maket share of Browser with green icon or some other silly factor, and statement like "Yes, the rise of green-icon browsers market share ignore this fact" would have been equally correct. Not that it has anything to do with your parent comment missing the point of the article.
- nitrogen 15y agoRegardless of why people choose a browser that has WebM, WebGL, or any other feature, the fact that they have that feature means that developers can start targeting it, thereby giving people more of a reason to want that feature.
- Aloisius 15y agoBing puts up a looped webm background every couple weeks. Sadly in FireFox on my Macbook Air, it is pretty jittery every time it loops and sometimes during playback. They are pretty though like - http://www.bing.com/az/hprichv/?p=AntelopeCanyon_Mammoth_MHD_rKW4_r1727_EN-US.webm http://www.bing.com/az/hprichv/?p=AntelopeCanyon_Mammoth_MHD...
- zdw 15y agoDepending on how Firefox plays back H.264, it may not be using HW acceleration through the GPU. Quicktime, and recent versions of Flash have the right OS hooks in place to do this.
- unicornporn 15y agoSorry for nitpicking, but I don't think we should compare a container format (WebM) with a video compression format (H.264 or VP8). A container format isn't very likely to have hardware acceleration.
- jensnockert 15y agoWebM always contains VP8 video though, otherwise it is a Matroska file.
- asomiv 15y agoWebM isn't a container format. It's a standard which specifies MKV (container) + VP8 (video codec) + Vorbis (audio codec).
- smspence 15y ago"This ignores the fact that H.264......" What ignores this? This article is talking about the market share of different web browsers.... What are they ignoring? I don't understand how this comment has anything to do with the article.
- attractivechaos 15y agoIf comparing browsers is the purpose, then the author should not put WebM and H264 in the title.