vaapopostproc: deinterlacing don't set the correct PTS for mpeg2
Submitted by Simon Farnsworth
Link to original bug (#734135)
Description
When using:
gst-launch-1.0 filesrc location=interlace-test.mpg ! tsdemux name=mux ! queue ! mpegvideoparse ! vaapidecode ! queue ! vaapipostproc deinterlace-method=4 ! queue ! vaapisink
or deinterlace-method=3, Haswell graphics from an i3-4350T doesn't deinterlace cleanly - I get flicker and jerkiness, and even green frames.
This also happens if I use interlaced streams over UDP.
I'm using gstreamer-vaapi as of:
commit 7ac501d0
Author: Gwenole Beauchesne gwenole.beauchesne@intel.com
Date: Fri Aug 1 06:32:32 2014 +0200
build: fix with --no-undefined linker flags.
https://bugzilla.gnome.org/show_bug.cgi?id=729352 libva-intel-driver as of:
commit 82d2ed8d7da3619c0ea467c06604f5626fc0b901
Author: Zhao Yakui yakui.zhao@intel.com
Date: Wed Jul 23 13:46:17 2014 +0800
Add more check of H264 slice param to avoid GPU hang caused by the incorrect parameter
This is to fix the GPU hang in https://bugs.freedesktop.org/show_bug.cgi?id=76363
V1->V2: Use the new check based on Haihao's comment. Discard the current frame with the error
slice_param instead of smart fix. In such case it can prompt that the error slice_param
can be fixed by the upper-middle.
Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
Tested-by: ValdikSS <iam@valdikss.org.ru>
Reviewed-by: Xiang Haihao <haihao.xiang@intel.com>
(cherry picked from commit 04202281135149a13a32dfb8a902debfac1331fe) and the released libva-1.3.0.
I would expect smooth deinterlacing, at least as good as I get using the same code on IVB.