GNOME Bugzilla – Bug 617778
deinterlace: Many methods are broken in fields=all mode or in one of the fields={top,bottom} modes
Last modified: 2018-11-03 14:42:00 UTC
This is true for most color formats it seems... examples of misbehaviour are jumping frames, pixelized frames, etc.
It seems that this was due to scanline pointer calculation in some cases for the methods making use of the simple method code. See https://bugzilla.gnome.org/show_bug.cgi?id=639321 for the approach used to fix that and possibly code something similar for greedy* and tomsmocomp.
There have been other fixes that would affect behavior such as is reported here. This may be obsolete.
Marking as obsolete.
(In reply to comment #3) > Marking as obsolete. Did you test to prove that this is obsolete? I haven't ported all the methods across to use your pointer calculation code nor edited the others to mirror its behaviour as much as possible so there may still be broken methods.
Oh indeed. I had the threshold set too low on the quality test.
Created attachment 191608 [details] script to do SSIM on deinterlace output A little script to interlace/deinterlace the ball pattern from videotestsrc and SSIM the result with the original. Initial investigation indicates that most methods are not grossly inaccurate, however, it clearly shows that 2 fields are skipped at the beginning in tomsmocomp, greedyh, and greedyl, making all the pictures out of sync. I'm hijacking this bug to include that problem.
Are you going to work on this David? It's assigned to you for some reason
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/29.