[Bug 789739] New: Dark image, vaapijpegdec

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=789739

            Bug ID: 789739
           Summary: Dark image, vaapijpegdec
    Classification: Platform
           Product: GStreamer
           Version: 1.13.x
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer-vaapi
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: lubagov at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
                CC: bsreerenj at gmail.com, vjaquez at igalia.com
     GNOME version: ---

Hello! I am check it on Gstreamer 1.12.3 and 1.13.0 and have same situatuin.
I have two camera, one HP HD 4310, and second camera ELP with IMX Sony 179
sensor. MJPEG images from HP HD 4310, decoded and look fine. Fom ELP cam, it
look dark. I am add to this post sample images.
https://drive.google.com/open?id=0B3_jMty60ScdRHAwZ3R2VDdXUkU
Here i use two pipeline:

1. to create images from camera as is
gst-launch-1.0 -v v4l2src num-buffers=100 device=/dev/video1 !
image/jpeg,width=3264,height=2448,framerate=15/1 ! jpegparse ! multifilesink
location="frame%d.jpg"

2. to transcode jpeg images in vaapijpegdec:
 gst-launch-1.0 -v multifilesrc location="frame%d.jpg" !
image/jpeg,width=3264,height=2448,framerate=15/1 ! jpegparse ! vaapijpegdec !
vaapipostproc ! pngenc ! multifilesink location="frame%d.png"

3. to transcode jpeg images in jpegdec:
gst-launch-1.0 -v multifilesrc location="frame%d.jpg" !
image/jpeg,width=3264,height=2448,framerate=15/1 ! jpegparse ! jpegdec !
videoconvert ! pngenc ! multifilesink location="frame%d.png"

Decoded images from vaapijpegdec look dark. I also test this cam with Intel
Media SDK and gst-mfx plugin, and it look fine.

Why? How to solve it?

Another problem i have, it is not working contrast/brighness in vaapipostproc.
If i set here not default value, i get black screen... Why?

Thank you!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.