Google Git
Sign in
webrtc / src / 6a0aad926044c2ae4eed6c26268e3f7723ea7736
commit6a0aad926044c2ae4eed6c26268e3f7723ea7736[log] [tgz]
authorArtem Titov <titovartem@webrtc.org>Mon Apr 15 08:35:51 2019
committerCommit Bot <commit-bot@chromium.org>Mon Apr 15 09:22:28 2019
tree28f9049b1fc2f712e43085267a305e19213935d6
parent9466b66ed9ecf58fafa952baf50cc4cdb4d3c991 [diff]
Temporary switch back to generated audio to fix test flakes

Wav file capturer won't repeat file or produce silence after file end and
WebRTC pipeline will crash in such case. In future we need to make it
possible to continue audio after file was ended to behalf in the same
way as video files capturer.

Bug: webrtc:10138
Change-Id: I35f5bd33790cd430a56002a44af0abb894a96d29
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/132795
Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
Commit-Queue: Artem Titov <titovartem@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#27609}
1 file changed
tree: 28f9049b1fc2f712e43085267a305e19213935d6
  1. api/
  2. audio/
  3. build_overrides/
  4. call/
  5. common_audio/
  6. common_video/
  7. crypto/
  8. data/
  9. examples/
  10. logging/
  11. media/
  12. modules/
  13. p2p/
  14. pc/
  15. resources/
  16. rtc_base/
  17. rtc_tools/
  18. sdk/
  19. stats/
  20. style-guide/
  21. system_wrappers/
  22. test/
  23. tools_webrtc/
  24. video/
  25. .clang-format
  26. .git-blame-ignore-revs
  27. .gitignore
  28. .gn
  29. .vpython
  30. abseil-in-webrtc.md
  31. AUTHORS
  32. BUILD.gn
  33. CODE_OF_CONDUCT.md
  34. codereview.settings
  35. common_types.h
  36. DEPS
  37. ENG_REVIEW_OWNERS
  38. LICENSE
  39. license_template.txt
  40. native-api.md
  41. OWNERS
  42. PATENTS
  43. PRESUBMIT.py
  44. presubmit_test.py
  45. presubmit_test_mocks.py
  46. pylintrc
  47. README.chromium
  48. README.md
  49. style-guide.md
  50. WATCHLISTS
  51. webrtc.gni
  52. whitespace.txt
README.md

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