[Bug 642669] interlace: Improve and extend field patterns

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Mon Feb 21 00:54:55 PST 2011

  GStreamer | gst-plugins-bad | git

--- Comment #6 from Robert Swain <robert.swain at gmail.com> 2011-02-21 08:54:50 UTC ---
Explicit specification of the patterns in both interlace and deinterlace, when
known would be good, I agree. That way third party apps can define and use
their own patterns.

I was talking about deinterlace in my last comment as I'm considering that
whatever one does, the other should be able to undo effectively somehow. Maybe
in any real GStreamer usage sense that's irrelevant as no one should produce
something and then undo it. But it's certainly useful for testing.

My point was that if we allow interlace to create a pattern on-the-fly
according to the input and output frame rates, deinterlace needs some way to
detect and output something sane. Such patterns could well differ from those in
the pattern list so we should implement something extra on top of the pattern
locking stuff I've done. I'll elaborate on the relevant ticket what is
implemented already to handle this.

Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- 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