mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-01-29 18:48:44 +00:00
Code Issues 1 Projects Releases Wiki Activity

pwd: discontinous event -> newsegment event

Browse source 
Fix a 0.8 leftover as mentioned on bug #621121.
This commit is contained in:
Stefan Kost 2011-07-24 11:24:44 +02:00
parent 6a1e2cc6e5
commit 3ebec93515
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/pwg/advanced-clock.xml
View file

@ -59,7 +59,7 @@
element will be regarded as the source element for this discussion.
</para>
</footnote>
First, the source element sends a discontinuous event. This event carries information
First, the source element sends a newsegment event. This event carries information
about the current relative time of the next sample. This relative time is
arbitrary, but it must be consistent with the timestamp that will be
placed in buffers. It is expected to be the relative time to the start
@ -81,7 +81,7 @@
<para>
If the stream is seeked, the next samples sent will have a timestamp that
is not adjusted with the element time. Therefore, the source element must
send a discontinuous event.
send a newsegment event.
</para>
</sect1>
<sect1 id="section-clock-obligations-of-each-element" xreflabel="Obligations
@ -101,14 +101,14 @@
Source elements (or parsers of formats that provide notion of time, such
as MPEG, as explained above) must place a timestamp in each buffer that
they deliver. The origin of the time used is arbitrary, but it must
match the time delivered in the discontinuous event (see below).
match the time delivered in the newsegment event (see below).
However, it is expected that the origin is the origin of the media
stream.
</para>
<para>
In order to initialize the element time of the rest of the pipeline, a
source element must send a discontinuous event before starting to play.
In addition, after seeking, a discontinuous event must be sent, because
source element must send a newsegment event before starting to play.
In addition, after seeking, a newsegment event must be sent, because
the timestamp of the next element does not match the element time of the
rest of the pipeline.
</para>

2
docs/pwg/building-chainfn.xml
View file

@ -47,7 +47,7 @@ gst_my_filter_change_state (GstElement * element, GstStateChange transition)
that buffers are not always writeable. In more advanced elements (the ones
that do event processing), you may want to additionally specify an event
handling function, which will be called when stream-events are sent (such
as end-of-stream, discontinuities, tags, etc.).
as end-of-stream, newsegment, tags, etc.).
</para>
<programlisting>
static void