gstreamer/validate/data/seek_forward.scenario

description, seek=true, duration=20, need-clock-sync=true
seek, name=First-forward-seek, playback_time="min(5.0, (duration/8))", start="min(10, 2*(duration/8))", flags=accurate+flush
seek, name=Second-forward-seek, playback_time="min(15.0, 3*(duration/8))", start="min(20, 4*(duration/8))", flags=accurate+flush
seek, name=Third-forward-seek, playback_time="min(25, 5*(duration/8))", start="min(30.0, 6*(duration/8))", flags=accurate+flush
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`
data: Set seeks to accurate+flush by default 2013-10-05 16:29:52 +00:00			`seek, name=First-forward-seek, playback_time="min(5.0, (duration/8))", start="min(10, 2*(duration/8))", flags=accurate+flush`
			`seek, name=Second-forward-seek, playback_time="min(15.0, 3(duration/8))", start="min(20, 4(duration/8))", flags=accurate+flush`
validate: data: Avoid using seek.stop time when not necessary Instead send an EOS. And add a seek_with_stop scenario to test that particular feature 2014-01-30 10:59:54 +00:00			`seek, name=Third-forward-seek, playback_time="min(25, 5(duration/8))", start="min(30.0, 6(duration/8))", flags=accurate+flush`
validate:scenarios: Prefer stop action instead of EOS when appropriate 2014-04-25 11:42:03 +00:00			`stop, playback_time=35.0`