[Webkit-unassigned] [Bug 76720] [chromium] Refactor video drawing to be more data driven
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jan 27 06:35:34 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=76720
--- Comment #18 from Tim Dresser <tdresser at chromium.org> 2012-01-27 06:35:34 PST ---
(In reply to comment #17)
> No, these are all draw-only state and they should live on the one quad that the video layer produces.
I was under the impression that each frame, the CCVideoLayerImpl produces a brand new quad, but the ManagedTexture objects are used in multiple frames.
Currently, the ManagedTexture objects are allocated in CCVideoLayerImpl::reserveTextures. A new ManagedTexture is only created if the layer doesn't have a texture for a specific plane. If my understanding is correct, that means that ManagedTexture objects will be reused for multiple frames. If we switch to calling reserveTextures in the quad, without a backpointer to the layer, then we'll only be able to use each ManagedTexture for one frame.
Does that sound correct?
--
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