47836b4ebb
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}
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 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://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