mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-26 19:51:11 +00:00
docs/design/part-overview.txt: Fix some typos, add blurb about buffer flags.
Original commit message from CVS: * docs/design/part-overview.txt: Fix some typos, add blurb about buffer flags.
This commit is contained in:
parent
da6dcf9a64
commit
cd16e10793
2 changed files with 11 additions and 5 deletions
|
@ -1,3 +1,8 @@
|
||||||
|
2006-05-04 Wim Taymans <wim@fluendo.com>
|
||||||
|
|
||||||
|
* docs/design/part-overview.txt:
|
||||||
|
Fix some typos, add blurb about buffer flags.
|
||||||
|
|
||||||
2006-05-03 Thomas Vander Stichele <thomas at apestaart dot org>
|
2006-05-03 Thomas Vander Stichele <thomas at apestaart dot org>
|
||||||
|
|
||||||
* docs/libs/gstreamer-libs-sections.txt:
|
* docs/libs/gstreamer-libs-sections.txt:
|
||||||
|
|
|
@ -190,6 +190,8 @@ Dataflow and buffers
|
||||||
- the duration of the data in time.
|
- the duration of the data in time.
|
||||||
- the media type of the data described with caps, these are key/value pairs that
|
- the media type of the data described with caps, these are key/value pairs that
|
||||||
describe the media type in a unique way.
|
describe the media type in a unique way.
|
||||||
|
- additional flags describing special properties of the data such as
|
||||||
|
discontinuities or delta units.
|
||||||
|
|
||||||
When an element whishes to send a buffer to another element is does this using one
|
When an element whishes to send a buffer to another element is does this using one
|
||||||
of the pads that is linked to a pad of the other element. In the push model, a
|
of the pads that is linked to a pad of the other element. In the push model, a
|
||||||
|
@ -220,7 +222,6 @@ Dataflow and buffers
|
||||||
The process of selecting a media type and attaching it to the buffers is called
|
The process of selecting a media type and attaching it to the buffers is called
|
||||||
caps negotiation.
|
caps negotiation.
|
||||||
|
|
||||||
|
|
||||||
Caps
|
Caps
|
||||||
----
|
----
|
||||||
|
|
||||||
|
@ -284,7 +285,7 @@ Pipeline clock
|
||||||
|
|
||||||
The purpose of the clock is to provide a stricly increasing value at the rate
|
The purpose of the clock is to provide a stricly increasing value at the rate
|
||||||
of one GST_SECOND per second. Clock values are expressed in nanoseconds.
|
of one GST_SECOND per second. Clock values are expressed in nanoseconds.
|
||||||
Elements use the clock time to synchronized the playback of data.
|
Elements use the clock time to synchronize the playback of data.
|
||||||
|
|
||||||
Before the pipeline is set to PLAYING, the pipeline asks each element if they can
|
Before the pipeline is set to PLAYING, the pipeline asks each element if they can
|
||||||
provide a clock. The clock is selected in the following order:
|
provide a clock. The clock is selected in the following order:
|
||||||
|
@ -295,11 +296,11 @@ Pipeline clock
|
||||||
sinks.
|
sinks.
|
||||||
- If no element provides a clock a default system clock is used for the pipeline.
|
- If no element provides a clock a default system clock is used for the pipeline.
|
||||||
|
|
||||||
In a typical playback pipeline this will select the clock provided by a sink element
|
In a typical playback pipeline this algorithm will select the clock provided by
|
||||||
such as an audio sink.
|
a sink element such as an audio sink.
|
||||||
|
|
||||||
In capture pipelines, this will typically select the clock of the data producer, which
|
In capture pipelines, this will typically select the clock of the data producer, which
|
||||||
can in most cases not control the rate at which it delivers data.
|
can in most cases not control the rate at which it produces data.
|
||||||
|
|
||||||
|
|
||||||
Pipeline states
|
Pipeline states
|
||||||
|
|
Loading…
Reference in a new issue