ebe5acb27a
Adds ability to specify desired frame size separate from actual clip resolution, as well as clip and desired fps. This allows e.g. reading an HD clip but running benchmarks in VGA, and to specify e.g. 60fps for the clip but 30for encoding where frame dropping kicks in so that motion is actually correct rather than just plaing the clip slowly. Bug: webrtc:12229 Change-Id: I4ad4fcc335611a449dc2723ffafbec6731e89f55 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/195324 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32839}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct
- Reporting bugs