mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-14 06:10:40 +01:00
![]() This can happen when the encoder uses real presentation timestamps that originate with the input frames. By using those, the encoder can bypass webrtc frame dropping logic and may severely over/under-shoot if the timestamps are very precise. In practice, this seems rather common on Chrome on Windows. Bug: aomedia:3391 Change-Id: I2be5eed4fabc86dac8a6c7bfdd068c2dcb5a3743 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/294740 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39382} |
||
---|---|---|
.. | ||
av1_svc_config.cc | ||
av1_svc_config.h | ||
av1_svc_config_unittest.cc | ||
BUILD.gn | ||
dav1d_decoder.cc | ||
dav1d_decoder.h | ||
DEPS | ||
libaom_av1_encoder.cc | ||
libaom_av1_encoder.h | ||
libaom_av1_encoder_unittest.cc | ||
libaom_av1_unittest.cc |