validate: Fix the change_state_intensive scenario

The scenario was in no way certified that the pipeline was in PAUSED
state when starting on an stream that does not preroll
This commit is contained in:
Thibault Saunier 2017-06-22 11:53:49 -04:00
parent 6a8b0111cd
commit 5924441633

View file

@ -1,3 +1,3 @@
description, duration=0, summary="Set state to NULL->PLAYING->NULL 20 times", need-clock-sync=true, min-media-duration=1.0, live_content_compatible=True
set-state, state="null", sub-action="set-state, state=playing", repeat=40
description, duration=0, summary="Set state to NULL->PLAYING->NULL 20 times", need-clock-sync=true, min-media-duration=1.0, live_content_compatible=True, handles-states=true
set-state, state="playing", sub-action="set-state, state=null", repeat=40
stop;