From dc2080fb783e1265150283e4a4f4fef71d61096d Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Mon, 8 Oct 2012 09:11:53 +0200 Subject: [PATCH] docs: small updates --- docs/design/part-preroll.txt | 3 ++- docs/design/part-sparsestreams.txt | 3 +++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/design/part-preroll.txt b/docs/design/part-preroll.txt index 5b2630f..597c661 100644 --- a/docs/design/part-preroll.txt +++ b/docs/design/part-preroll.txt @@ -28,7 +28,8 @@ state could unqueue the buffer again. The state is commited in the following conditions: - a buffer is received on a sinkpad - - an EOS is received on a sinkpad. + - an GAP event is received on a sinkpad. + - an EOS event is received on a sinkpad. We require the state change to be commited in EOS as well since an EOS means by definition that no buffer is going to arrive anymore. diff --git a/docs/design/part-sparsestreams.txt b/docs/design/part-sparsestreams.txt index 269faa5..66b3d2f 100644 --- a/docs/design/part-sparsestreams.txt +++ b/docs/design/part-sparsestreams.txt @@ -11,6 +11,9 @@ elements could know not to expect any more data for that gap. In 0.10, segment information conveyed through SEGMENT events can be used for the same purpose. +In 1.0, there is a GAP event that works in a similar fashion as the FILLER +event in 0.8. + Use cases ~~~~~~~~~ -- 2.7.4