The flush start event can be sent upstream and downstream and travels out-of-bounds with the dataflow.
It marks pads as being flushing and will make them return {@link org.gstreamer.FlowReturn#WRONG_STATE} when used for data flow with {@link Pad#pushEvent}, {@link Pad#chain}, Pad#allocBuffer, {@link Pad#getRange} and{@link Pad#pullRange}. Any event (except a {@link FlushStopEvent}) received on a flushing pad will return {@code false} immediately.
Elements should unlock any blocking functions and exit their streaming functions as fast as possible when this event is received.
This event is typically generated after a seek to flush out all queued data in the pipeline so that the new media is played as soon as possible.
|
|