[Webkit-unassigned] [Bug 111126] Enable GPU-GPU texture copy in texImage2D() for HTMLVideoElement if hardware accelerated video decode is in use

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Mar 4 17:57:22 PST 2013


--- Comment #17 from Andrew Scherkus <scherkus at chromium.org>  2013-03-04 17:59:44 PST ---
(In reply to comment #16)
> For the record, I'd like to move *all* of the compositor <-> media engine interactions to the chromium side.  My ideal world would have something like:
> namespace WebKit {
> class WebMediaPlayer {
> public:
> ...
>    WebLayer* createCompositingLayer() = 0;
> };
> and the implementation in chromium would construct a cc::VideoLayer, wrap it in a WebLayer, and return that back to WebKit so WebCore can insert it into the compositing tree in the correct place.  Then, from that point on, all interactions would be between cc::VideoLayer and the media:: pipeline stuff, using media::VideoFrame as the video frame data structure.  This would mean no WebVideoLayer, no WebVideoFrame, no WebVideoFrameProvider, no adapters for any of these, etc.  I just haven't had time to sit down and think through this fully (especially the startup/shutdown synchronization).
> So yes, adding this new functionality on the chromium side will definitely be more future proof.

jamesr: +100000 (I'd be happy to help think things through -- I have some scatterbrained ideas as well)

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list