Unexpected buffer timestamps after x264enc
Sebastian Dröge
sebastian at centricular.com
Mon Dec 7 01:17:39 PST 2015
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20151207/a230abb5/attachment-0001.sig>
More information about the gstreamer-devel
mailing list