New issue
Advanced search Search tips

Issue 921931 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Blocked on:
issue 907767



Sign in to add a comment

V4L2VideoDecodeAccelerator: use ImageProcessor::Process(input_frame, output_frame, cb) when ImageProcessor runs OutputMode::IMPORT mode

Project Member Reported by deanliao@chromium.org, Jan 15

Issue description

Right now in V4L2VideoDecodeAccelerator, when it needs ImageProcessor, it calls the original Process() interface. We plan to deprecate the original interface (see crbug.com/907767). For the case ImageProcessor runs OutputMode::IMPORT mode, i.e. V4L2VideoDecodeAccelerator's output buffers are imported from its client, it should be as simple as wrapping output buffer's DMAbuf FDs into a new VideoFrame. And then use it as output_frame to call ImageProcessor::Process(input_frame, output_frame, cb).
 

Sign in to add a comment