diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-60B9404B-5102-4FBB-A32F-55F2ACFD1481.dita
--- a/Symbian3/SDK/Source/GUID-60B9404B-5102-4FBB-A32F-55F2ACFD1481.dita Wed Mar 31 11:11:55 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-60B9404B-5102-4FBB-A32F-55F2ACFD1481.dita Fri Jun 11 12:39:03 2010 +0100
@@ -1,83 +1,83 @@
-
-
-
-
-
- GStreamer is designed to make it easier to write applications easily that
-handle audio, video, or both. Pluggable components can be mixed and matched
-into arbitrary pipelines, which consist of a chain of processing elements. GStreamer
-core provides the following features: Plug-in handling Media type negotiation Clocking and data flow
-
GStreamer also provides
Some -GStreamer concepts are as follows:
Element
An element is an object that performs some action -on a multimedia stream. Examples of such actions are reading a file, decoding -or encoding data and capturing data from a hardware device.
Bin
A bin is a subclass of element. A bin acts as a container -for other elements, so multiple elements combine into one logical unit.
Pipeline
A pipeline is a set of data processing elements -connected in series, so the output from one element is the input for the next -element.
In GStreamer the pipeline is a specialized bin subclass that -provides execution of all contained elements. Normally, applications create -one pipeline that will manage all the elements contained within it.
Note: Elements can be added to and removed from pipelines -based on the use-case being handled. For example a use-case such as playing -an MP3 file using GStreamer.
An element can provide a number -of pads, which can be either source or sink pads. A pad is a plug or port -on an element to link with other elements. The pads are responsible for data -flow between the elements. Source pads supply data, and sink pads consume -data. Basically, pads are used to negotiate compatibility and allow data flow -between elements.
An element can be in one of four different states -during the application request:
Null
Ready
Pause
Play
GStreamer also provides higher level utilities -and components to detect automatically the media type of an application, and -to create the best possible pipeline for a use-case. This process is called -auto plugging.
GStreamer -is used in many types of applications including:
Media playback and streaming
Media recording
Media transcoding
Video editing
For example the diagram below shows how a Media Player uses GStreamer:
GStreamer is designed to make it easier to write applications easily that +handle audio, video, or both. Pluggable components can be mixed and matched +into arbitrary pipelines, which consist of a chain of processing elements.
+GStreamer +core provides the following features:
Plug-in handling
Media type negotiation
Clocking and data flow
Some +GStreamer concepts are as follows:
Element
An element is an object that performs some action +on a multimedia stream. Examples of such actions are reading a file, decoding +or encoding data and capturing data from a hardware device.
Bin
A bin is a subclass of element. A bin acts as a container +for other elements, so multiple elements combine into one logical unit.
Pipeline
A pipeline is a set of data processing elements +connected in series, so the output from one element is the input for the next +element.
In GStreamer the pipeline is a specialized bin subclass that +provides execution of all contained elements. Normally, applications create +one pipeline that will manage all the elements contained within it.
Note: Elements can be added to and removed from pipelines +based on the use-case being handled. For example a use-case such as playing +an MP3 file using GStreamer.
An element can provide a number +of pads, which can be either source or sink pads. A pad is a plug or port +on an element to link with other elements. The pads are responsible for data +flow between the elements. Source pads supply data, and sink pads consume +data. Basically, pads are used to negotiate compatibility and allow data flow +between elements.
An element can be in one of four different states +during the application request:
Null
Ready
Pause
Play
GStreamer also provides higher level utilities +and components to detect automatically the media type of an application, and +to create the best possible pipeline for a use-case. This process is called +auto plugging.
GStreamer +is used in many types of applications including:
Media playback and streaming
Media recording
Media transcoding
Video editing
For example the diagram below shows how a Media Player uses GStreamer: