mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-03-31 05:09:41 +00:00
On the first buffer, it's possible that sink_segment is set but src_segment has not been set yet. If this is the case, we should not calculate cur_level.time since sink_segment.position may be large and src_segment.position default is 0, with the resulting diff being larger than max-size-time, causing the queue to start leaking (if leaky=downstream). One potential consequence of this is that the segment event may be stored on the srcpad before the caps event is pushed downstream, causing a g_warning ("Sticky event misordering, got 'segment' before 'caps'"). https://bugzilla.gnome.org/show_bug.cgi?id=773096 |
||
---|---|---|
.. | ||
elements | ||
tracers | ||
Makefile.am | ||
meson.build |