Thanks for the request.

This is definitely something we've been thinking about, but the problem is especially 
hairy for us because of Chrome's multi-process architecture.  FFmpeg actually doesn't 
have direct access to the drawing surface currently, and is infact running in the 
renderer process which isn't allowed to have direct access to hardware.  This means 
that none of the hardware accel solutions will work without some significant surgery 
on the rendering pipeline.  This issue also makes fullscreen harder.

Once we have the rendering pipeline patched up, we'll look at how to integrate 
specific hardware APIs, do nicer scaling, etc. etc.

As ajwong mentioned, we're doing a bunch of work to get *some* form of hardware 
acceleration possible.  After that's done we might be should be able to have a better 
idea on what's needed for VAAPI and other accelerated video APIs.

Also note that decoding is not our bottleneck - rendering is.
Current code was achieves 720p on Pentium4 3 Ghz.
Before looking at decoding, we'll retune for Atom and offload rendering to GPU.

If you're looking to buy a netbook, Chrome will take full advantage of multicore, so a 
dual core N330 or D510 cpu will help.

Well, for reference, I'm currently trying to run Chrome on my 6 year old P4 2.4ghz
machine with a GeForce 6600. VLC will just barely play a 720p vid smoothly, but with
Flash and HTML5 (aka Chrome & Firefox) it's unwatchable...so in my particular use
case (which I'm sure I'm not alone in) it would be a very nice benefit.

Also, I don't know why you even brought up multicore...there are currently zero
decoders for any operating system nor codec that are multithreaded. They're all still
single threaded, so that makes no difference.

@derick.eisenhardt: the particular decoder we use actually decodes full frames in 
parallel.  We see quite a performance improvement compared to running a traditional 
single threaded decoder.

http://gitorious.org/ffmpeg/ffmpeg-mt

Ok, that's nice to know. Glad to see ffmpeg's made some progress on this. Hope they
push this into their stable branch soon ;)

 Issue 43025  has been merged into this issue.

We're trying to deprecate HelpWanted, so I'm bulk-removing it from some bugs.

Did you seriously just mark my 2 year old feature request a duplicate of one just made today?

@derick.eisenhardt: yep.  It's nice to start with a clean slate sometimes.  History is preserved through bi-directional linking.
The pain from the injustice might be somewhat alleviated for you by noting the status of the other bug is "Started" :)

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.