[gstreamer-bugs] [Bug 163577] [RFC] Interlaced/progressive media support in GStreamer.

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=163577

  GStreamer | gstreamer (core) | Ver: HEAD CVS


Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wim at fluendo.com




------- Comment #8 from Wim Taymans  2006-10-26 08:09 UTC -------
Been thinking of adding 2 new custom flags to a GstBuffer, which get a
definition based on the caps of the buffer. For video buffers the meaning would
be:

GST_BUFFER_FLAG_CUSTOM1 = GST_VIDEO_BUFFER_TFF
GST_BUFFER_FLAG_CUSTOM2 = GST_VIDEO_BUFFER_BFF

The fact that a buffer is interlaced is therefore detectable because one of the
flags is set. Otherwise the buffer contains a single frame/field.

This does not need any caps changing and elements can incrementally be updated
to handle the interlacing flags.

Putting multiple video frames in one buffer could require a new caps property.
The flags can still be used though. Alternatively, the buffer size and the
field size (as calculated from the description in the caps) can indicated that
this buffer conatains multiple samples (like we do now with audio).
Alternatively yet another new buffer flag could be added to denote the fact of
2 fields in this buffer.

Sounds a lot more simple than having to deal with lots of caps that can change
for each buffer (try writing a transform_caps function for ffmpegcolorspace
with all these properties :).


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email