Add low-latency renderer algorithm for WebRTC streams
The current low-latency rendering runs without any renderer algorithm. This gives a very low latency at the cost of dropping frames in an uncontrolled way. The goal of the low-latency renderer algorithm is to add a small amount of latency to reduce number of dropped frames. We're especially interested in reducing the number of consecutively dropped frames since these are more noticeable than a single dropped frame. The low-latency renderer algorithm is enabled from WebRTC by setting the metadata field maximum_composition_delay_in_frames. This is an experimental feature that is active if and only if the RTP header extension playout-delay is set to min=0ms and max>0ms. The feature can be completely disabled by specifying the field trial WebRTC-LowLatencyRenderer/enabled:false/ Bug: 1138888 Change-Id: Ia59db56b115f2cb6e8348e115781f8ad0c33eedb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2502343Reviewed-by:Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Johannes Kron <kron@chromium.org> Cr-Commit-Position: refs/heads/master@{#824646}
Showing
Please register or sign in to comment