gstreamer/subprojects/gst-plugins-base/tests/validate/videorate/reverse.30fps.validatetest

set-globals, in_framerate="(GstFraction)30/1", out_framerate="(GstFraction)30/1"

include, location="videorate-test.meta"

play
seek, start=0.0, stop=1.0, flags=accurate+flush, rate=-1.0

# First buffer is display as fast as possible
crank-clock, expected-elapsed-time=(guint64)0
crank-clock, repeat=29

# Waiting on EOS
crank-clock, expected-elapsed-time=(guint64)33333334
stop, on-message=eos
videorate: Fix buffer selection logic in reverse playback Stop comparing all timestamps from buffers that are before the segment with the segment.stop and compare with the actual end times. Comparing to segment.stop for all the buffers that where before the segment.stop was incorrect and leading to consuming wrong buffers and not respecting segment.stop, this is now properly tested. Expectations for `reverse.10_to_1fps.validatetest` have been fixed to take that into account and comparing the checksums of the sinkpad and srcpad expectations makes pretty clear how wrong that was. (we can see in the expectations that videotestsrc outputs an extra buffer with pts == segment.stop and this one is now properly dropped by videorate as bec7f4ad5ed4bb1abfb92db946e654338766562b aimed at doing) Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/-/merge_requests/668> 2020-05-25 20:59:53 +00:00			`set-globals, in_framerate="(GstFraction)30/1", out_framerate="(GstFraction)30/1"`

			`include, location="videorate-test.meta"`

			`play`
			`seek, start=0.0, stop=1.0, flags=accurate+flush, rate=-1.0`

			`# First buffer is display as fast as possible`
			`crank-clock, expected-elapsed-time=(guint64)0`
			`crank-clock, repeat=29`

			`# Waiting on EOS`
			`crank-clock, expected-elapsed-time=(guint64)33333334`
			`stop, on-message=eos`