[Bug 796625] vaapipostproc: Bob deinterlace doesn't work for raw file.

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Wed Jun 20 01:08:15 UTC 2018


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

--- Comment #12 from U. Artie Eoff <ullysses.a.eoff at intel.com> ---
(In reply to U. Artie Eoff from comment #11)
> (In reply to Nicolas Dufresne (ndufresne) from comment #10)
> > (In reply to U. Artie Eoff from comment #9)
> > > I may be naive, but should "rawvideoparse format=nv12 width=1920 height=1080
> > > interlaced=1" output interlaced frames for vaapipostproc?
> > 
> > It will pretend it's interlaced, but it's not, since the image you provided
> > is progressive. Then you selected a BOB deinterlacer, which I believe is the
> > only one that won't deteriorate the frame. Also, we aware that you need at
> > least 3 fields (2 interleaved frames) in order to use any other algo.
> 
> So it determines the raw image data is progressive, how?  As far as
> rawvideoparse is concerned, it's just random raw data, right?  And it should
> read the data in terms of how the user specifies.  Perhaps it's because the
> size of data is not enough for 3 fields?  Oddly, ffmpeg and yami (same vaapi
> driver) produce a different result for bob deinterlacer with same input!

That is, ffmpeg-vaapi and yami-vaapi produce very similar outputs.  That is,
PSNR is 50-60 range for both.  But gstreamer-vaapi produces noop output.

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


More information about the gstreamer-bugs mailing list