commit | 3f2634eadc8c1109f73fb24eec7635ca9fc74e48 | [log] [tgz] |
---|---|---|
author | Sergey Silkin <ssilkin@webrtc.org> | Mon Nov 06 10:49:19 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Nov 07 16:34:20 2017 |
tree | eb1d1b2a7cfaf02ff453ebad5dd5c589be691b83 | |
parent | 2732bf5f20878885ef90b7a7a04cbfd1b9314cca [diff] |
Reland "Keep spatial_idx=kNoSpatialIdx(255) if there is no layer indices." This is a reland of 47836b4ebb8a5c71695b5ec07bffd5ee4e3bc2ff Internal tests are synced with the fix. Original change's description: > Keep spatial_idx=kNoSpatialIdx(255) if there is no layer indices. > > spatial_idx is not present in RTP header if there is no temporal or > spatial layering. But the parser sets spatial_idx to 0 in this case. > When reflector repacketizes such packets it writes layering indices > into outgoing packets. When packets arrive to receiver it thinks that > it deals with multi layer stream and passes it through special path > in Vp9 reference frame finder which never outputs inter frames. > > I modified the parser such that it keeps spatial_idx=kNoSpatialIdx(255) > when there is no layer indices in RTP header. Related unit tests have > been modified as well. > > Bug: none > Change-Id: I14498cafb4e57797577dc873298c35b243479f88 > Reviewed-on: https://webrtc-review.googlesource.com/17980 > Commit-Queue: Sergey Silkin <ssilkin@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Reviewed-by: Åsa Persson <asapersson@webrtc.org> > Reviewed-by: Rasmus Brandt <brandtr@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#20560} TBR=brandtr@webrtc.org,asapersson@webrtc.org,sprang@webrtc.org Bug: none Change-Id: I6087a8b20a926296b30432d69251670120b2a20c Reviewed-on: https://webrtc-review.googlesource.com/20940 Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> Commit-Queue: Sergey Silkin <ssilkin@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20591}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.