Thibault Saunier baa5aae24b baseparse: Don't set meaningless buffer dts from segment->start ... When we do not have any information about DTSs we shouldn't try to make them up, moreover after seeking `segment->start` has nothing to do with the next buffer timing (and is probably after the actual buffer timestamp) and since, since fa8312472f we do: ``` if (buffer->dts > buffer->dts) buffer->pts = buffer->dts ``` we end up setting `buffer->pts = segment->start` which is plain broken and leads to downstream decoder accept the first buffer as it will be inside the segment (its pts==segment->start) which basically means accurate seeking behaves mostly the same way as keyframe seeks. Fixes https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/492		2020-02-04 18:14:05 +00:00
..
base	baseparse: Don't set meaningless buffer dts from segment->start	2020-02-04 18:14:05 +00:00
check	gstcheck: remove bogus refcount asserts	2019-12-10 09:42:37 +01:00
controller	Remove autotools build system	2019-10-13 16:10:42 +01:00
helpers	Remove autotools build system	2019-10-13 16:10:42 +01:00
net	gstreamer: use of g_value_dup_string	2019-12-18 15:57:54 +01:00
meson.build	meson: Always use a dependency object for dependencies	2018-09-05 16:33:43 +05:30