mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-01-11 18:05:37 +00:00
design/part-latency: Minor logic fix
The maximum latency will be the element's minimum latency or bigger, not bigger than the element's minimum latency or bigger.
This commit is contained in:
parent
4a5ce862a2
commit
fd3a064c97
1 changed files with 5 additions and 5 deletions
|
@ -256,9 +256,9 @@ The pipeline latency is queried with the LATENCY query.
|
||||||
Elements answering the latency query should set this to the maximum
|
Elements answering the latency query should set this to the maximum
|
||||||
time for which they can buffer upstream data without blocking or
|
time for which they can buffer upstream data without blocking or
|
||||||
dropping further data. For an element this value will generally be
|
dropping further data. For an element this value will generally be
|
||||||
bigger than its own minimum latency, but might be bigger than that
|
its own minimum latency, but might be bigger than that if it can
|
||||||
if it can buffer more data. As such, queue elements can be used to
|
buffer more data. As such, queue elements can be used to increase
|
||||||
increase the maximum latency.
|
the maximum latency.
|
||||||
|
|
||||||
The value set in the query should again consider upstream's maximum
|
The value set in the query should again consider upstream's maximum
|
||||||
latency:
|
latency:
|
||||||
|
|
Loading…
Reference in a new issue