25558ad819
The H.264 does not contain picture IDs and are not sufficient to determine that a packet may be skipped. This causes retransmission requests for FEC that are currently dropped by the sender (since they should be redundant). The receiver is then unable to continue without having the packet gap filled (unlike VP8/VP9 which moves on since it has a consecutive stream of picture IDs). Even if FEC retransmission did work it's a huge waste of bandwidth, since it just adds additional overhead that has to be unconditionally transmitted. This bandwidth is better used to send higher-quality frames. BUG=webrtc:5264 R=stefan@webrtc.org Review URL: https://codereview.webrtc.org/1687303002 . Cr-Commit-Position: refs/heads/master@{#11601}
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