Upgrade the hardware is not an acceptable answer. Video acceleration is meant to offload work from CPU (especially on constrained devices, e.g. mobile). You want to be able to do compositing on video card, so that you don't have to read the video out of the video card's memory, transfer it over the bus, to the CPU, do some transforms/overlays/..., and then send it back to the video card for display. Doing that absolutely kills framerate.<div>
<br></div><div>As we (browsers) implement <video> I think a lot of us are starting with software rendering. Certainly we want to be able to do hardware acceleration at some point. Perhaps some things we will still be able to do in hardware, e.g. overlays of HTML or certain transforms (if the video device supports saying "take this, translate it, and composite" and the rendering engine only needs geometry data.) Other things we might not be able to do in hardware (e.g. if you have "transparent" flash video on top, and Flash wants to know what pixels are underneath it, then we would have to read that data off of the video card, send it to CPU, ...)</div>
<div><br></div><div>I think what would be helpful is for browsers who are implementing <video> with hardware acceleration to publish information on what would make them fall back to software rendering. If it turns out that list is roughly similar across implementations, perhaps it could be added as a note in the spec that doing the following certain things may cause performance implications. We're probably not ready to do that yet given that we don't have enough implementation experience, but that would be my suggestion for how to move forward.</div>
<div><br></div><div>-Ian<br><br><div class="gmail_quote">On Tue, Apr 28, 2009 at 5:59 PM, Ian Hickson <span dir="ltr"><ian@hixie.ch></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Sat, 28 Mar 2009, Benjamin M. Schwartz wrote:<br>
><br>
> The <video> tag has great potential to be useful on low-powered<br>
> computers and computing devices, where current internet video streaming<br>
> solutions (such as Adobe's Flash) are too computationally expensive.<br>
> My personal experience is with OLPC XO-1, on which Flash (and Gnash) are<br>
> terribly slow for any purpose, but Theora+Vorbis playback is quite<br>
> smooth at reasonable resolutions and bitrates.<br>
><br>
> The <video> standard allows arbitrary manipulations of the video stream<br>
> within the HTML renderer. To permit this, the initial implementations<br>
> (such as the one in Firefox 3.5) will perform all video decoding<br>
> operations on the CPU, including the tremendously expensive YUV->RGB<br>
> conversion and scaling. This is viable only for moderate resolutions<br>
> and extremely fast processors.<br>
><br>
> Recognizing this, the Firefox developers expect that the decoding<br>
> process will eventually be accelerated. However, an accelerated<br>
> implementation of the <video> spec inevitably requires a 3D GPU, in<br>
> order to permit transparent video, blended overlays, and arbitrary<br>
> rotations.<br>
><br>
> Pure software playback of video looks like a slideshow on the XO, or any<br>
> device with similar CPU power, achieving 1 or 2 fps. However, these<br>
> devices typically have a 2D graphics chip that provides "video overlay"<br>
> acceleration: 1-bit alpha, YUV->RGB, and simple scaling, all in<br>
> special-purpose hardware. Using the overlay (via XVideo on Linux) allows<br>
> smooth, full-speed playback.<br>
><br>
> THE QUESTION:<br>
> What is the recommended way to handle the <video> tag on such hardware?<br>
<br>
</div></div>Upgrade the hardware.<br>
<div class="im"><br>
<br>
> There are two obvious solutions:<br>
> 0. Implement the spec, and just let it be really slow.<br>
> 1. Attempt to approximate the correct behavior, given the limitations of<br>
> the hardware. Make the video appear where it's supposed to appear, and<br>
> use the 1-bit alpha (dithered?) to blend static items over it. Ignore<br>
> transparency of the video. Ignore rotations, etc.<br>
> 2. Ignore the HTML context. Show the video "in manners more suitable to<br>
> the user (e.g. full-screen or in an independent resizable window)".<br>
><br>
> Which is preferable? Is it worth specifying a preferred behavior?<br>
<br>
</div>>From HTML's point of view, all are acceptable. From the user's point of<br>
view, 1 and 2 are preferable, probably at the user's option.<br>
<br>
I don't know what else to tell you. :-)<br>
<font color="#888888"><br>
--<br>
Ian Hickson U+1047E )\._.,--....,'``. fL<br>
<a href="http://ln.hixie.ch/" target="_blank">http://ln.hixie.ch/</a> U+263A /, _.. \ _\ ;`._ ,.<br>
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'<br>
</font></blockquote></div><br></div>