[gstreamer-bugs] [Bug 637754] New: Requesting augmentation of multipartdemux time stamping functionality

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=637754
  GStreamer | gst-plugins-good | 0.10.x

           Summary: Requesting augmentation of multipartdemux time
                    stamping functionality
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.x
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: GStreamer-Bugs at tycosp.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Hello,
We have developed an application in which we use the multipartdemux to assemble
large video frames (which means many packets) “pushed” to this element via an
http source.  And the current implementation of multipartdemux will use the
reception time stamp of the most recent “packet” recvd as the timestamp when it
finally pulls/sends assembled frames downstream.  On a congested network with
retransmits, these packets-per-frame can be milliseconds apart.  For this
reason we consider the time stamp of the first buffer in the frame more
accurate than the timestamp of the last buffer in the frame.

Would it be possible for the multipartdemux element to be augmented to support
the ability to use the reception time of the first packet when sending the
assembled frame downstream instead of the timestamp of the most recently
received packets’ timestamp?  And to create another property which would
represent using the current implementation or using this new proposed
implementation, defaulted to use the current implementation?  If this is deemed
a good idea we can develop and submit a patch.

Thank you very much.

-- 
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.