From 99a3a0a6c0462afa1d4fb7809b81b93c20360337 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Tue, 19 Jul 2005 09:19:06 +0000 Subject: Small docs updates. Original commit message from CVS: * docs/design/part-clocks.txt: * docs/design/part-events.txt: * gst/base/gstbasesrc.c: (gst_base_src_do_seek): Small docs updates. Only update the seeking values when we are not busy streaming. --- docs/design/part-events.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'docs/design/part-events.txt') diff --git a/docs/design/part-events.txt b/docs/design/part-events.txt index 03f83b3f95..e471ede854 100644 --- a/docs/design/part-events.txt +++ b/docs/design/part-events.txt @@ -98,6 +98,9 @@ Since the stream time is always set to 0 at start and after a seek, a 0 point for all next buffer's timestamps has to be propagated through the pipeline using the DISCONT event. +Before sending buffers, an element must send a DISCONT event. An element is +free to refuse buffers if they were not preceeded by a DISCONT event. + Elements that sync to the clock should store the DISCONT start and end values and substract the start value from the buffer timestamp before comparing it against the stream time (see part-clocks.txt). @@ -107,14 +110,13 @@ substracted from the timestamp. If it does so, it needs to send a corrected DISCONT downstream, ie, one with start time 0. A DISCONT event should be generated as soon as possible in the pipeline and -is usually generated by a demuxer. The event is generated before pushing the -first buffer and after a seek, right before pushing the new buffer. +is usually generated by a demuxer or source. The event is generated before +pushing the first buffer and after a seek, right before pushing the new buffer. The DISCONT event can be send from both the application and the streaming thread and should be serialized with the buffers. - SEEK ---- -- cgit v1.2.3