New issue
Advanced search Search tips

Issue 645494 link

Starred by 2 users
Status: Fixed
Owner:
chfremer@chromium.org
Closed: Mar 2017
Cc:
emir...@chromium.org
mcasas@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocking:
issue 584797



Sign in to add a comment

Add support for MJPEG to FakeVideoCaptureDevice

Project Member Reported by chfremer@chromium.org, Sep 9 2016 
FakeVideoCaptureDevice is used for testing video capture code without depending on an actual device. It generates frames and currently outputs them in the I420 format.

Many actual capture devices deliver their video in MJPEG format. To enable testing the code paths for those scenarios it would be useful to have FakeVideoCaptureDevice be configurable to output MJPEG instead of I420.

Comment 1 by mcasas@chromium.org, Sep 9 2016 

Sounds like a good idea. Since Motion JPEG is actually not
specified ([1] : "Unlike the video formats specified [...], 
there is no document that defines a single exact format that 
is universally recognized as a complete specification of 
'Motion JPEG' for use in all contexts"), I'd recommend
just producing independent encoded JPEG images using 
gfx::JPEGCodec [2].


[1] https://en.wikipedia.org/wiki/Motion_JPEG#Disadvantages
[2] https://cs.chromium.org/chromium/src/ui/gfx/codec/jpeg_codec.h?q=jpegcodec&sq=package:chromium&l=23&dr=CSs

Comment 2 by mcasas@chromium.org, Sep 9 2016

Labels: Hotlist-GoodFirstBug

Comment 3 by yini...@chromium.org, Sep 9 2016

Status: Assigned (was: Untriaged)

Comment 4 by chfremer@chromium.org, Mar 15 2017

Status: Fixed (was: Assigned)
This work has been completed, see https://codereview.chromium.org/2721633006/
►

Sign in to add a comment