Unexpected buffer timestamps after x264enc

David Jaggard davywj at gmail.com
Mon Dec 7 02:15:25 PST 2015


Yes I'm using the GST_BUFFER_TIMESTAMP macro to get the timestamp.

The pipeline is:
udpsrc -> queue -> rtpmp2tdepay -> identity -> tsdemux -> (video/x-h264) ->
queue -> identity -> decodebin -> deinterlace -> identity -> x264enc ->
identity -> video/x-h264,profile=baseline ->rtph264pay -> rtpbin ->
identity -> multiudpsink

The identity elements are there so I can look at the buffer times using the
handoff signal

I can't see how to get the segment information from here?

On 7 December 2015 at 09:17, Sebastian Dröge <sebastian at centricular.com>
wrote:

> On So, 2015-12-06 at 11:17 +0000, David Jaggard wrote:
> > I've placed identity elements either side of an x264enc element to
> > have a look at the timestamps.
> >
> > (I've rounded all timestamps up to milliseconds)
> >
> > The timestamp of the first buffer to enter the x264enc is 5182ms. The
> > timestamp of the first buffer to leave is 3600000000ms. Subsequent
> > buffers increase monotonically from there. Given the clock time at
> > this point was around 6400ms how does the sink (multiudpsink in this
> > case) know when to 'display' this?
> >
> > Incidentally the latency at the sink was 1220ms and post buffer
> > timestamp - 3600000000ms + 5182ms + 1220ms = ~6400ms (the clock
> > time).
>
> What's your complete pipeline and with buffer timestamps you mean
> GST_BUFFER_PTS()? Take a look at the running time as calculated from
> that with gst_segment_to_running_time() and the segment that is output
> by x264enc.
>
> --
> Sebastian Dröge, Centricular Ltd · http://www.centricular.com
>
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20151207/24ae35d9/attachment.html>


More information about the gstreamer-devel mailing list