diff options
| author | Sebastian Dröge <sebastian.droege@collabora.co.uk> | 2011-09-08 14:23:50 +0200 |
|---|---|---|
| committer | Sebastian Dröge <sebastian.droege@collabora.co.uk> | 2011-09-08 14:28:23 +0200 |
| commit | 43538e2e75b4bdc5fc71a62b472a4b223472c059 (patch) | |
| tree | 8fc77f478b9d15166c85c083e24d0ee0e6b890ad /docs/design/part-element-transform.txt | |
| parent | a952de69dd7aa216dc7aaf5572ae17229574477a (diff) | |
| parent | d3cad28da936b037d877dc70c02286b81b680284 (diff) | |
Merge branch 'master' into 0.11
Conflicts:
docs/design/draft-buffer2.txt
docs/design/part-TODO.txt
docs/design/part-block.txt
docs/design/part-bufferlist.txt
docs/design/part-caps.txt
docs/design/part-element-transform.txt
docs/design/part-events.txt
docs/design/part-negotiation.txt
gst/gstcaps.c
gst/gstevent.h
gst/gstghostpad.c
gst/gstinterface.c
gst/gstpad.c
gst/gstpad.h
gst/gstutils.c
libs/gst/base/gstbasesink.c
libs/gst/base/gstbasesrc.c
libs/gst/base/gstbasetransform.c
libs/gst/base/gsttypefindhelper.c
plugins/elements/gstcapsfilter.c
plugins/elements/gsttee.c
tests/check/generic/sinks.c
tools/gst-launch.1.in
Diffstat (limited to 'docs/design/part-element-transform.txt')
| -rw-r--r-- | docs/design/part-element-transform.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/design/part-element-transform.txt b/docs/design/part-element-transform.txt index 73f18bf560..e3c11b86f2 100644 --- a/docs/design/part-element-transform.txt +++ b/docs/design/part-element-transform.txt @@ -25,7 +25,7 @@ the following things: Some transform elements can operate in different modes: - passthrough (no changes are done on the input buffers) - - in-place (changes made directly to the incomming buffers without requiring a + - in-place (changes made directly to the incoming buffers without requiring a copy or new buffer allocation) - metadata changes only @@ -253,7 +253,7 @@ state. We can identify these steady states: input buffer is transformed into the output buffer. The flow is exactly the same as the case with the same-caps negotiation. (DCC) -We can immeditatly observe that the copy transform states will need to +We can immediately observe that the copy transform states will need to allocate a new buffer from the bufferpool. When the transform element is receiving a non-writable buffer in the in-place state, it will also need to perform an allocation. There is no reason why the passthrough state would @@ -295,7 +295,7 @@ retrieve the size. There are two functions: Given a caps and a size on one pad, and a caps on the other pad, calculate the size of the other buffer. This function is able to perform all size - transforms and is the prefered method of transforming a size. + transforms and is the preferred method of transforming a size. - get_unit_size() |