a9329dbae2
When Chromium hooks up with the stereo codec, then it has difficulty communicating with a google chrome without stereo codec. By design, we do allow codec choice for the standalone codecs, but the problem is that we do not handle the payload correctly, and thus the existence of stereo codec will remove the payload registry of the standalone version of its associated codec. (For example, stereo codec on top of VP9 will remove the payload registry of standalone VP9 codec.) This CL fixes the issue. When generating payload data, we should use "stereo" as payload name, instead of its associated codecs. Bug: webrtc:8657 Change-Id: I9e0b54de6bd41d370b9353f9553c998e4049789f Reviewed-on: https://webrtc-review.googlesource.com/33122 Reviewed-by: Emircan Uysaler <emircan@webrtc.org> Reviewed-by: Stefan Holmer <stefan@webrtc.org> Commit-Queue: Qiang Chen <qiangchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#21523}
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.
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