mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-01-11 09:55:36 +00:00
Code Issues 1 Projects Releases Wiki Activity

design/part-latency: Minor logic fix

Browse source 
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:
Sebastian Dröge 2015-02-12 11:26:26 +02:00
parent 4a5ce862a2
commit fd3a064c97
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/design/part-latency.txt
View file

@ -256,9 +256,9 @@ The pipeline latency is queried with the LATENCY query.
Elements answering the latency query should set this to the maximum
time for which they can buffer upstream data without blocking or
dropping further data. For an element this value will generally be
bigger than its own minimum latency, but might be bigger than that
if it can buffer more data. As such, queue elements can be used to
increase the maximum latency.
its own minimum latency, but might be bigger than that if it can
buffer more data. As such, queue elements can be used to increase
the maximum latency.
The value set in the query should again consider upstream's maximum
latency:
@ -292,8 +292,8 @@ The pipeline latency is queried with the LATENCY query.
maximum latency. The base class' default query handler needs to be
overridden to correctly handle leaky buffering.
If the element has multiple sinkpads, the maximum upstream latency is
the minimum of all live upstream maximum latencies.
If the element has multiple sinkpads, the maximum upstream latency is
the minimum of all live upstream maximum latencies.
Event
~~~~~