diff options
| author | Wim Taymans <wim.taymans@gmail.com> | 2007-02-15 11:32:02 +0000 |
|---|---|---|
| committer | Wim Taymans <wim.taymans@gmail.com> | 2007-02-15 11:32:02 +0000 |
| commit | 46d2c100f8aa9cf7948c2b2dd6aa1eb5c8d1ad81 (patch) | |
| tree | ae977055a100b13186036062cef4197f765f38c0 /docs/design/part-activation.txt | |
| parent | 2d4c842ab7b06d178e695adaa87d671bdcb9beb4 (diff) | |
docs/design/: Some doc updates. Start renaming from stream_time to running_time where it was used wrongly.
Original commit message from CVS:
* docs/design/part-TODO.txt:
* docs/design/part-activation.txt:
* docs/design/part-block.txt:
* docs/design/part-buffering.txt:
* docs/design/part-clocks.txt:
* docs/design/part-element-source.txt:
* docs/design/part-events.txt:
* docs/design/part-gstbin.txt:
* docs/design/part-gstbus.txt:
* docs/design/part-gstpipeline.txt:
* docs/design/part-live-source.txt:
* docs/design/part-messages.txt:
* docs/design/part-overview.txt:
* docs/design/part-qos.txt:
* docs/design/part-query.txt:
* docs/design/part-states.txt:
* docs/design/part-trickmodes.txt:
Some doc updates. Start renaming from stream_time to running_time where
it was used wrongly.
Diffstat (limited to 'docs/design/part-activation.txt')
| -rw-r--r-- | docs/design/part-activation.txt | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/docs/design/part-activation.txt b/docs/design/part-activation.txt index f2aa75c55c..425505536e 100644 --- a/docs/design/part-activation.txt +++ b/docs/design/part-activation.txt @@ -6,6 +6,10 @@ sink-to-source order. As elements undergo the READY->PAUSED transition, their pads are activated so as to prepare for data flow. Some pads will start tasks to drive the data flow. +An element activates its pads from sourcepads to sinkpads. This to make +sure that when the sinkpads are activated an ready to accept data, the +sourcepads are already active to pass the data downstream. + Pads can be activated in one of two modes, PUSH and PULL. PUSH pads are the normal case, where the source pad in a link sends data to the sink pad via gst_pad_push(). PULL pads instead have sink pads request data @@ -71,12 +75,14 @@ pushing data. Deactivation ------------ -Pad deactivation occurs when a pad is unlinked, or when its parent goes -into the READY state. gst_pad_set_active() is called with a FALSE -argument, which then calls activate_push() or activate_pull() with a -FALSE argument, depending on the activation mode of the pad. +Pad deactivation occurs when its parent goes into the READY state or when the +pad is deactivated explicitly by the application or element. +gst_pad_set_active() is called with a FALSE argument, which then calls +activate_push() or activate_pull() with a FALSE argument, depending on the +activation mode of the pad. Mode switching -------------- -Changing from push to pull modes needs a bit of thought. +Changing from push to pull modes needs a bit of thought. This is actually +possible and implemented but not yet documented here. |