mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-04-26 06:54:49 +00:00
Minor changes to Application Development Manual
This commit is contained in:
parent
773cfd3d87
commit
2157e4907c
2 changed files with 6 additions and 6 deletions
|
@ -25,20 +25,20 @@ great deal in the *GStreamer Plugin Writer's Guide*.
|
||||||
|
|
||||||
## Pads
|
## Pads
|
||||||
|
|
||||||
*Pads* are element's input and output, where you can connect other
|
*Pads* are an element's input and output, where you can connect other
|
||||||
elements. They are used to negotiate links and data flow between
|
elements. They are used to negotiate links and data flow between
|
||||||
elements in GStreamer. A pad can be viewed as a “plug” or “port” on an
|
elements in GStreamer. A pad can be viewed as a “plug” or “port” on an
|
||||||
element where links may be made with other elements, and through which
|
element where links may be made with other elements, and through which
|
||||||
data can flow to or from those elements. Pads have specific data
|
data can flow to or from those elements. Pads have specific data
|
||||||
handling capabilities: a pad can restrict the type of data that flows
|
handling capabilities: a pad can restrict the type of data that flows
|
||||||
through it. Links are only allowed between two pads when the allowed
|
through it. Links are only allowed between two pads when the allowed
|
||||||
data types of the two pads are compatible. Data types are negotiated
|
data types (capabilities) of the two pads are compatible. Data types are
|
||||||
between pads using a process called *caps negotiation*. Data types are
|
negotiated between pads using a process called *caps negotiation*. Data
|
||||||
described as a `GstCaps`.
|
types are described by `GstCaps`.
|
||||||
|
|
||||||
An analogy may be helpful here. A pad is similar to a plug or jack on a
|
An analogy may be helpful here. A pad is similar to a plug or jack on a
|
||||||
physical device. Consider, for example, a home theater system consisting
|
physical device. Consider, for example, a home theater system consisting
|
||||||
of an amplifier, a DVD player, and a (silent) video projector. Linking
|
of an audio amplifier, a DVD player, and a (silent) video projector. Linking
|
||||||
the DVD player to the amplifier is allowed because both devices have
|
the DVD player to the amplifier is allowed because both devices have
|
||||||
audio jacks, and linking the projector to the DVD player is allowed
|
audio jacks, and linking the projector to the DVD player is allowed
|
||||||
because both devices have compatible video jacks. Links between the
|
because both devices have compatible video jacks. Links between the
|
||||||
|
|
|
@ -80,7 +80,7 @@ High performance is obtained by:
|
||||||
|
|
||||||
The core of GStreamer is essentially media-agnostic. It only knows about
|
The core of GStreamer is essentially media-agnostic. It only knows about
|
||||||
bytes and blocks, and only contains basic elements. The core of
|
bytes and blocks, and only contains basic elements. The core of
|
||||||
GStreamer is functional enough to even implement low-level system tools,
|
GStreamer is even functional enough to implement low-level system tools,
|
||||||
like cp.
|
like cp.
|
||||||
|
|
||||||
All of the media handling functionality is provided by plugins external
|
All of the media handling functionality is provided by plugins external
|
||||||
|
|
Loading…
Reference in a new issue