Add support for generic display rates to WebRTC/low-latency renderer
The initial implementation of the low-latency renderer assumed that the display rate was fixed at 60Hz. This CL adds support for generic frame rates as well as missed render intervals. 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: Ic64b26331d31aaf8fb8ed4fb8f1056b227cb6eaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527424Reviewed-by:Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Johannes Kron <kron@chromium.org> Cr-Commit-Position: refs/heads/master@{#830225}
Showing
This diff is collapsed.
This diff is collapsed.
Please register or sign in to comment