gstreamer/validate/data/scenarios/seek_forward.scenario

description, seek=true, duration=20, need-clock-sync=true
include,location=includes/default-seek-flags.scenario
set-vars, test=(string)5.0
seek, name=First-forward-seek, playback-time="min($test, ($duration/8))", start="min(10, 2*($duration/8))", flags="$(default-flags)"
seek, name=Second-forward-seek, playback-time="min(15.0, 3*($duration/8))", start="min(20, 4*($duration/8))", flags="$(default-flags)"
seek, name=Third-forward-seek, playback-time="min(25, 5*($duration/8))", start="min(30.0, 6*($duration/8))", flags="$(default-flags)"
stop, playback-time=35.0
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=20, 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			`set-vars, test=(string)5.0`
			`seek, name=First-forward-seek, playback-time="min($test, ($duration/8))", start="min(10, 2*($duration/8))", flags="$(default-flags)"`
			`seek, name=Second-forward-seek, playback-time="min(15.0, 3($duration/8))", start="min(20, 4($duration/8))", flags="$(default-flags)"`
			`seek, name=Third-forward-seek, playback-time="min(25, 5($duration/8))", start="min(30.0, 6($duration/8))", flags="$(default-flags)"`
validate: Rename action type playback_time to playback-time Keeping backward compatiblity with the old naming 2014-10-12 18:19:42 +00:00			`stop, playback-time=35.0`