| commit | 709374b33385aa9fecfd994aa429254efca45f46 | [log] [tgz] |
|---|---|---|
| author | Per K <perkj@webrtc.org> | Thu Mar 21 12:56:50 2024 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 21 14:19:57 2024 |
| tree | f7b329ab30db77801c7cd4e6ee5182cd19877659 | |
| parent | f49a8262cc4b89549375cde7b962bbf5ee3c0d07 [diff] |
Reland "Propagate known Encoder SinkWants when configured instead of after first frame." This reverts commit c39712b51522bb21c18c58c593f454c5cc0e7995. Reason for revert: Fixed issue where frame rate not adapted to highest "active" requested frame rate. Patchset 1 contains original cl. Later patchsets contains modifications. Original change's description: > Propagate known Encoder SinkWants when configured instead of after first frame. > > Propagate requested resolution and max frame rate to the source when > configured rather than after the first frame. > This is so that the source can be configured immediately. There is no > reason why source should be updated until after first frame since it may lead > to unnecessary reconfigurations and thread jumps. Wants that depend on actual frame size is not moved. > > Cl also change default behaviour in VideoStreamEncoderTest to not > set restriction on max frame rate. > Bug: webrtc:14451 Change-Id: I2668db44bd17586efcf511ad3cd975065c503ec5 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/343122 Commit-Queue: Per Kjellander <perkj@webrtc.org> Reviewed-by: Åsa Persson <asapersson@webrtc.org> Cr-Commit-Position: refs/heads/main@{#41941}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.