[Bug 763042] New: gen75_vpp_vebox.c:1415: hsw_veb_pre_format_convert: Assertion `0' failed.

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 763042
           Summary: gen75_vpp_vebox.c:1415: hsw_veb_pre_format_convert:
                    Assertion `0' failed.
    Classification: Platform
           Product: GStreamer
           Version: 1.6.0
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer-vaapi
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: frank.huber at barco.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
                CC: bsreerenj at gmail.com, vjaquez at igalia.com
     GNOME version: ---

Decoding mjpeg together with vaapipostproc, we get this Assertion:
gen75_vpp_vebox.c:1415: hsw_veb_pre_format_convert: Assertion `0' failed.

How to reproduce:

Working:
gst-launch-1.0 souphttpsrc
location="http://88.53.197.250/axis-cgi/mjpg/video.cgi?resolution=320x240" !
multipartdemux ! jpegparse ! vaapidecode ! vaapipostproc deinterlace-mode=1
deinterlace-method=bob ! vaapisink sync=false

NOT working:
gst-launch-1.0 souphttpsrc
location="http://88.53.197.250/axis-cgi/mjpg/video.cgi?resolution=320x240" !
multipartdemux ! jpegparse ! vaapidecode ! vaapipostproc deinterlace-mode=1
deinterlace-method=bob format=nv12 ! vaapisink sync=false

The only difference is "format=nv12" for vaapipostproc.
Using "format=i420" it also works.

Our setup:
gst-inspect-1.0 --version
gst-inspect-1.0 version 1.6.3

gst-inspect-1.0 vaapipostproc |grep Version
  Version                  1.6.0

libva info: VA-API version 0.38.1
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/va/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_38
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.38 (libva 1.6.2)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 1.6.2

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