[Bug 643847] New: deinterlace: Add support for deinterlacing using buffer caps/flags
bugzilla at gnome.org
Thu Mar 3 23:01:27 PST 2011
GStreamer | gst-plugins-good | git
Summary: deinterlace: Add support for deinterlacing using
AssignedTo: gstreamer-bugs at lists.freedesktop.org
ReportedBy: robert.swain at gmail.com
QAContact: gstreamer-bugs at lists.freedesktop.org
GNOME target: ---
GNOME version: ---
When not using the fieldanalysis element immediately upstream of deinterlace,
behaviour should remain unchanged. fieldanalysis will set the caps and
the buffers such that they can be interpreted and acted upon to produce
There are two main modes of operation:
- Passive pattern locking
Passive pattern locking is a non-blocking, low-latency mode of operation
is suitable for close-to-live usage. Initially a telecine stream will be
output as variable framerate with naïve timestamp adjustment. With each
incoming buffer, an attempt is made to lock onto a pattern. When a lock
obtained, the src pad and output buffer caps will reflect the pattern and
timestamps will be accurately interpolated between pattern repeats. This
means that initially and at pattern transitions there will be short
of inaccurate timestamping.
- Active pattern locking
Active pattern locking is a blocking, high-latency mode of operation that
targeted at use-cases where timestamp accuracy is paramount. Buffers will
queued until enough are present to make a lock. When locked, timestamps
be accurately interpolated between pattern repeats. Orphan fields can be
dropped or deinterlaced. If no lock can be obtained, a single field might
pushed through to be deinterlaced.
Locking can also be disabled or 'auto' chooses between passive and active
locking modes depending on whether upstream is live.
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