summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArun Raghavan <git@arunraghavan.net>2015-11-04 13:10:26 +0530
committerArun Raghavan <git@arunraghavan.net>2015-11-04 13:15:21 +0530
commitf7c9b269a0813434a32d1f3a0cf22da29dd69721 (patch)
tree679e8118d052ab2477a9f74840cb7a92b1abe391
parent34abadd258f2bcb2950a0f4d59c499105f84c965 (diff)
downloadwebrtc-audio-processing-f7c9b269a0813434a32d1f3a0cf22da29dd69721.tar.gz
doc: Add release notes about changes and API breakage
-rw-r--r--NEWS44
1 files changed, 44 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 3d5c03a..485f0a8 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,47 @@
+Release 0.2
+-----------
+
+Updated AudioProcessing code to be more current.
+
+Contains API breaking changes.
+
+Upstream changes include:
+
+ * Rewritten AGC and voice activity detection
+ * Intelligibility enhancer
+ * Extended AEC filter
+ * Beamformer
+ * Transient suppressor
+ * ARM, NEON and MIPS optimisations (MIPS optimisations are not hooked up)
+
+API changes:
+
+ * We no longer include a top-level audio_processing.h. The webrtc tree format
+ is used, so use webrtc/modules/audio_processing/include/audio_processing.h
+ * The top-level module_common_types.h has also been moved to
+ webrtc/modules/interface/module_common_types.h
+ * C++11 support is now required while compiling client code
+ * AudioProcessing::Create() does not take any arguments any more
+ * AudioProcessing::Destroy() is gone, use standard C++ "delete" instead
+ * Stream parameters are now configured via StreamConfig and ProcessingConfig
+ rather than set_sample_rate(), set_num_channels(), etc.
+ * AudioFrame field names have changed
+ * Use config API for newer audio processing options
+ * Use ProcessReverseStream() instead of AnalyzeReverseStream(), particularly
+ when using the intelligibility enhancer
+ * GainControl::set_analog_level_limits() is broken. The AGC implementation
+ hard codes 0-255 as the volume range
+
+Other notes:
+
+ * The new audio processing parameters are not all tested, and a few are not
+ enabled upstream (in Chromium) either
+ * The rewritten AGC appears to be less sensitive, and it might make sense to
+ initialise the capture volume to something reasonable (33% or 50%, for
+ example) to make sure there is sufficient energy in the stream to trigger
+ the AGC mechanism
+
+
Release 0.1
-----------