Timestamp issue with compositor and live sources

Mathieu Duponchelle mathieu at centricular.com
Thu Aug 18 20:48:20 UTC 2022


No, that's not an issue you can fix with the "latency" property, you need to find out why those
timestamps are decreasing in the first place (which probably means eg GstVideoDecoder will set
them to CLOCK_TIME_NONE). I would also recommend testing with latest GStreamer in case
you're encountering an issue that was fixed since then, 1.16 is old.

On 8/18/22 14:36, Florian Echtler via gstreamer-devel wrote:
> Hello everyone,
>
> I came across an issue when using my custom WebRTC server (currently running on GStreamer 1.16.3) with Safari. After an unpredictable amount of time (let's say usually somewhere between 2 and 60 seconds), I get the following warning/error, and the server crashes:
>
> ------------------------------------------------------------------------------
>
> 0:01:04.731633057 13722 0x7f30b800daa0 WARN videodecoder gstvideodecoder.c:2761:gst_video_decoder_prepare_finish_frame:<avdec_h264-2> decreasing timestamp (0:01:04.771572861 < 0:01:04.789710261)
>
> [some very likely unrelated warnings from nicesink]
>
> 0:01:09.159572691 13722      0x12fc5e0 ERROR videoaggregator gstvideoaggregator.c:1428:gst_video_aggregator_fill_queues:<frontmixer:sink_2> Need timestamped buffers!
>
> ------------------------------------------------------------------------------
>
> Is this something I could fix through the "latency" property of compositor? If so, what should I set it to? Or would I need to upgrade to 1.18/1.20 for this so I can set "ignore-inactive-pads"?
>
> Thanks and best, Florian


More information about the gstreamer-devel mailing list