7cd94f66eb
if not on Android/iOS. This means proprietary_codecs=1 && ffmpeg_branding=Chrome can be used to enable this H.264 enc/dec implementation instead of rtc_use_h264=1 && ffmpeg_branding=Chrome. This is used by both Chromium trybots (but not default Chromium build) and offical Chrome build, meaning we will be able to test and enable H.264 in chromium. This change would otherwise be enough to launch this feature in Chrome, but because we do not want to do that before we have chromium browser tests and are ready to flip the switch, this CL prevents chromium from using H.264 just yet: https://codereview.chromium.org/1641163002/ (landing this after that CL). BUG=chromium:500605, chromium:468365 Review URL: https://codereview.webrtc.org/1660403004 Cr-Commit-Position: refs/heads/master@{#11506}
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. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- 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