New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 601788 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner:
Last visit 21 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature

Blocked on:
issue 485859

Blocking:
issue 356871



Sign in to add a comment

Implement new zero-copy video playback

Project Member Reported by dongseon...@intel.com, Apr 8 2016

Issue description

Current zero-copy video playback implementation is actually "one-copy video playback".
The final VideoFrame is produced by following pipeline.

1. Software decoder produces a VideoFrame. e.g. VpxVideoDecoder, FFmpegVideoDecoder.
2. GpuMemoryBufferVideoFramePool copies the software VideoFrame to hardware VideoFrame backed by GpuMemoryBuffer.
3. CC composites the mailbox belonging to hardware VideoFrame.

This issue will get rid of #2 step. Software decoder (e.g. VpxVideoDecoder, FFmpegVideoDecoder) will decode video frame directly on hardware VideoFrame backed by GpuMemoryBuffer.
 
Cc: pinkerton@chromium.org dcasta...@chromium.org ccameron@chromium.org tiago.vi...@intel.com dnicoara@chromium.org renganat...@chromium.org mcasas@chromium.org jbau...@chromium.org reve...@chromium.org
Submit the initial CL; https://codereview.chromium.org/1869303004
Blockedon: 485859
Blocking: 356871
Components: -Blink>Media>Video
Cc: j.iso...@samsung.com
Status: WontFix (was: Started)
Marking this as WontFix since every attempt at this shows that we're better off using the one-copy to transform into a more hardware efficient format.

Sign in to add a comment