<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style> </head> <body dir="ltr"> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> mpegtsmux interprets the first incoming timestamp as 0 ( the start-time-selection property defaults to zero)</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> same goes for flvmux</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> so basically both muxer offset the timestamps by default</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div id="appendonsend"></div> <hr style="display:inline-block;width:98%" tabindex="-1"> <div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Von:</b> gstreamer-devel <gstreamer-devel-bounces@lists.freedesktop.org> im Auftrag von Marianna S. Buschle via gstreamer-devel <gstreamer-devel@lists.freedesktop.org><br> <b>Gesendet:</b> Montag, 31. Mai 2021 12:49<br> <b>An:</b> gstreamer-devel@lists.freedesktop.org <gstreamer-devel@lists.freedesktop.org><br> <b>Cc:</b> Marianna S. Buschle <msb@qtec.com><br> <b>Betreff:</b> Re: AW: 1000 hours offset in timestamp of h264 stream</font> <div> </div> </div> <div class="BodyFragment"><font size="2"><span style="font-size:11pt;"> <div class="PlainText">After a lot of digging I have managed to find the bug related to this 1000<br> hours offset:<br> <a href="https://github.com/GStreamer/gst-plugins-ugly/blob/master/ext/x264/gstx264enc.c#L1383">https://github.com/GStreamer/gst-plugins-ugly/blob/master/ext/x264/gstx264enc.c#L1383</a><br> <br> So I can see how x264 is adding the offset and why.<br> <br> But so far I haven't found how other elements are ignoring/removing this<br> offset.<br> <br> I can see that if I add `mpegtsmux ! tsdemux` to the pipeline after the<br> `h264parse` the offset seems to be removed by the `mux` and things then work<br> as expected.<br> <br> But I cant really see how it is doing it or how I should go about properly<br> fixing the interpipe elements.<br> <br> So far my backup plan is to, as you say, to try re-timstamp the frames by<br> subtracting the offset...<br> <br> <br> <br> --<br> Sent from: <a href="http://gstreamer-devel.966125.n4.nabble.com/">http://gstreamer-devel.966125.n4.nabble.com/</a><br> _______________________________________________<br> gstreamer-devel mailing list<br> gstreamer-devel@lists.freedesktop.org<br> <a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br> </div> </span></font></div> </body> </html>