gstreamer/validate/data/scenarios/seek_backward.scenario

description, seek=true, duration=30, need-clock-sync=true
include,location=includes/default-seek-flags.scenario
seek, name=Backward-seek, playback-time="min(5.0, ($duration / 4))", rate=1.0, start=0.0, flags="$(default-flags)"
seek, name=Backward-seek, playback-time="min(10.0, 2*($duration / 4))", rate=1.0, start="min(5.0, $duration / 4)", flags="$(default-flags)"
seek, name=Backward-seek, playback-time="min(15.0, 3*($duration / 4))", rate=1.0, start="min(10.0, 2*($duration / 4))", flags="$(default-flags)"
stop, playback-time="min(15.0, 3*($duration / 4))"
validate: launcher: Force clock syncronization for some scenarios In some cases it is necessary that the clock is sync so that all the actions can be executed. 2014-07-23 12:43:29 +00:00			`description, seek=true, duration=30, need-clock-sync=true`
Scenarios: override seek flags for RTSP tests Our RTSP server is not accurate, it makes no sense to perform accuracy checks on the client-side segments. 2019-02-02 00:23:16 +00:00			`include,location=includes/default-seek-flags.scenario`
validate:scenario: Allow using set-vars from numeric expressions And require them to follow the `$varname` (can't be $(varname) as parenthesis have another meaning in those expressions). Still accept "duration" and "position" as varname for backward compat but update our scenarios anyway. 2019-02-02 16:43:35 +00:00			`seek, name=Backward-seek, playback-time="min(5.0, ($duration / 4))", rate=1.0, start=0.0, flags="$(default-flags)"`
			`seek, name=Backward-seek, playback-time="min(10.0, 2*($duration / 4))", rate=1.0, start="min(5.0, $duration / 4)", flags="$(default-flags)"`
			`seek, name=Backward-seek, playback-time="min(15.0, 3($duration / 4))", rate=1.0, start="min(10.0, 2($duration / 4))", flags="$(default-flags)"`
			`stop, playback-time="min(15.0, 3*($duration / 4))"`