commit | 825e4f19ce38e839d74d865b01dbe86abbec3df3 | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Tue Sep 17 13:13:36 2024 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 17 14:33:26 2024 |
tree | 4ee3707c2610f4265096dc59bd75eac5e66427d7 | |
parent | 52ea2c3d2a9c35f5744d0d3eadbae75d8506eb0f [diff] |
VideoAdapter: Interpret requested resolution as max restriction. The `requested_resolution` API must not change aspect ratio, example: - Frame is 60x30 - Requested is 30x30 - We expect 30x15 (not 30x30!) as to maintain aspect ratio. This bug was previously fixed by making VideoAdapter unaware of the requested resolution behind a flag: this seemed OK since the VideoStreamEncoder ultimately decides the resolution, whether or not the incoming frame is adapted. But this is not desired for some non-Chrome use cases. This CL attempts to make both Chrome and non-Chrome use cases happy by implementing the aspect ratio preserving restriction inside VideoAdapter too. This allows us to get rid of the "use_standard_requested_resolution" flag and change the "VideoStreamEncoderResolutionTest" TEST_P to TEST_F. Bug: webrtc:366067962, webrtc:366284861 Change-Id: I1dfd10963274c5fdfd18d0f4443b2f209d2e9a4b Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/362720 Reviewed-by: Jonas Oreland <jonaso@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Henrik Andreassson <henrika@webrtc.org> Cr-Commit-Position: refs/heads/main@{#43037}
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.