mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-06-07 07:58:51 +00:00
Code Issues 1 Projects Releases Wiki Activity

ID Labels consistent with the rest of the manual.

Browse source 
Original commit message from CVS:

ID Labels consistent with the rest of the manual.
This commit is contained in:
Ramon Garcia Fernandez 2004-08-28 14:13:42 +00:00
parent 0e52ed40ab
commit 4c38fe8bb9
1 changed files with 10 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -7,7 +7,7 @@
syncrhonization mechanism. syncrhonization mechanism.
</para> </para>
<sect1 id="clock-time-types"> <sect1 id="section-clock-time-types" xreflabel="Types of time">
<title> Types of time </title> <title> Types of time </title>
<para> <para>
@ -20,10 +20,10 @@
adding an offset to the clock time. adding an offset to the clock time.
</para> </para>
</sect1> </sect1>
<sect1 id="clocks"> <sect1 id="section-clocks" xreflabel="Clocks">
<title>Clocks</title> <title>Clocks</title>
<para> <para>
A clock is a source of time measurements. Though the system time can be used GStreamer can use different clocks. Though the system time can be used
as a clock, soundcards and other devices provides a better time source. For as a clock, soundcards and other devices provides a better time source. For
this reason some elements provide a clock. The method this reason some elements provide a clock. The method
<function>get_clock</function> is implemented in elements that provide <function>get_clock</function> is implemented in elements that provide
@ -37,13 +37,13 @@
</para> </para>
</sect1> </sect1>
<sect1> <sect1 id="section-time-data-flow" xreflabel="Flow of data between elements
and time">
<title> <title>
Flow control of data and time Flow of data between elements and time
</title> </title>
<para> <para>
Now we will see how time is used in a pipeline in its different states. We Now we will see how time information travels the pipeline in different states.
will assume that this is a real time playing.
</para> </para>
<para> <para>
@ -84,7 +84,8 @@
send a discontinous event. send a discontinous event.
</para> </para>
</sect1> </sect1>
<sect1 id="clock-obligations-of-each-element"> <sect1 id="section-clock-obligations-of-each-element" xreflabel="Obligations
of each element">
<title> <title>
Obligations of each element. Obligations of each element.
</title> </title>
@ -94,7 +95,7 @@
pipeline. pipeline.
</para> </para>
<sect2> <sect2>
<title>Source elements </title> <title>Source elements </title>
<para> <para>
Source elements (or parsers of formats that provide notion of time, such Source elements (or parsers of formats that provide notion of time, such