mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-01-10 17:35:59 +00:00
docs/manual/: Some more minor docs additions and updates.
Original commit message from CVS: * docs/manual/basics-bins.xml: * docs/manual/basics-elements.xml: * docs/manual/intro-basics.xml: Some more minor docs additions and updates.
This commit is contained in:
parent
9c39605f30
commit
e5559e4e8b
4 changed files with 29 additions and 12 deletions
|
@ -1,3 +1,10 @@
|
|||
2006-01-11 Tim-Philipp Müller <tim at centricular dot net>
|
||||
|
||||
* docs/manual/basics-bins.xml:
|
||||
* docs/manual/basics-elements.xml:
|
||||
* docs/manual/intro-basics.xml:
|
||||
Some more minor docs additions and updates.
|
||||
|
||||
2006-01-11 Wim Taymans <wim@fluendo.com>
|
||||
|
||||
* docs/manual/basics-bins.xml:
|
||||
|
|
|
@ -134,7 +134,7 @@ main (int argc
|
|||
player = gst_element_factory_make ("oggvorbisplayer", "player");
|
||||
|
||||
/* set the source audio file */
|
||||
g_object_set (G_OBJECT (player), "location", "helloworld.ogg", NULL);
|
||||
g_object_set (player, "location", "helloworld.ogg", NULL);
|
||||
|
||||
/* start playback */
|
||||
gst_element_set_state (GST_ELEMENT (player), GST_STATE_PLAYING);
|
||||
|
@ -148,5 +148,11 @@ main (int argc
|
|||
url="http://gstreamer.freedesktop.org/data/doc/gstreamer/head/pwg/html/index.html">Plugin
|
||||
Writers Guide</ulink>.
|
||||
</para>
|
||||
<para>
|
||||
Examples of such custom bins are the playbin and decodebin elements from<ulink
|
||||
type="http"
|
||||
url="http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/index.html">
|
||||
gst-plugins-base</ulink>.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
|
|
@ -530,7 +530,9 @@ main (int argc,
|
|||
any form. Internally, &GStreamer; will start threads that take this
|
||||
task on to them. &GStreamer; will also take care of switching
|
||||
messages from the pipeline's thread into the application's own
|
||||
thread, by using <xref linkend="chapter-bus"/>.
|
||||
thread, by using a <ulink type="http"
|
||||
url="&URLAPI;GstBus.html"><classname>GstBus</classname></ulink>. See
|
||||
<xref linkend="chapter-bus"/> for details.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
|
|
@ -35,16 +35,14 @@
|
|||
themselves, you can mostly control a bin as if it where an element,
|
||||
thereby abstracting away a lot of complexity for your application. You
|
||||
can, for example change state on all elements in a bin by changing the
|
||||
state of that bin itself. Bins also forward some signals from their
|
||||
contained childs (such as errors and tags).
|
||||
state of that bin itself. Bins also forward bus messages from their
|
||||
contained children (such as error messages, tag messages or EOS messages).
|
||||
</para>
|
||||
<para>
|
||||
A pipeline is a bin that allows to <emphasis>run</emphasis> (technically
|
||||
referred to as <quote>iterating</quote>) its contained childs. By
|
||||
iterating a pipeline, data flow will start and media processing will
|
||||
take place. A pipeline requires iterating for anything to happen. you
|
||||
can also use threads, which automatically iterate the contained childs
|
||||
in a newly created threads. We will go into this in detail later on.
|
||||
A pipeline is a top-level bin. As you set it to PAUSED or PLAYING state,
|
||||
data flow will start and media processing will take place. Once started,
|
||||
pipelines will run in a separate thread until you stop them or the end
|
||||
of the data stream is reached.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
@ -79,8 +77,12 @@
|
|||
between elements. Data flows out of one element through one or more
|
||||
<emphasis>source pads</emphasis>, and elements accept incoming data
|
||||
through one or more <emphasis>sink pads</emphasis>. Source and sink
|
||||
elements have only source and sink pads, respectively. Data is
|
||||
embodied in a <classname>GstData</classname> structure.
|
||||
elements have only source and sink pads, respectively. Data usually
|
||||
means buffers (described by the <ulink type="http"
|
||||
url="&URLAPI;/gstreamer-GstBuffer.html"><classname>GstBuffer
|
||||
</classname></ulink> object) and events (described by the <ulink
|
||||
type="http" url="&URLAPI;/gstreamer-GstEvent.html"><classname>
|
||||
GstEvent</classname></ulink> object).
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
|
Loading…
Reference in a new issue