Merge pull request #274701 from enricohuang/patch-26

Update audio issues troubleshooting guide

Author: Stacyrch140

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/poor-quality.md

@@ -54,3 +54,9 @@ If the sender is using Desktop Edge or Chrome, they can follow the instructions
 
 The audio recordings include the audio before and after it's processed by the audio processing module.
 By comparing the recordings, you may be able to determine where the issue is coming from.
+
+We found in some scenarios that when the browser is playing sound, especially if the sound is loud,
+and the user starts speaking, the user's audio input in the first few seconds may be overly processed,
+leading to distortion in the sound. This can be observed by comparing the ref\_out.wav and input.wav files in aecdump files.
+In this case, reducing the volume of audio playing sound may help.
+

articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-diagnostic-audio-recordings.md

@@ -30,3 +30,49 @@ After you finish an ACS call, you should be able to see files saved in the folde
 `*.input.M.wav` is the audio input captured from the microphone.
 
 `*.aecdump` contains the necessary wav files for debugging audio after processed by the audio processing module in browsers.
+
+## How to build tools for inspecting aecdump files
+To inspect `*.aecdump` files, you must use the `unpack_aecdump` utility program, the source code can be found at [unpack\_aecdump](https://chromium.googlesource.com/external/webrtc/+/HEAD/rtc_tools/unpack_aecdump?autodive=0)
+
+You need to prepare the build environment (Here we use Windows as an example)
+
+Prerequisites:
+
+* Visual Studio 2022
+* Python 3
+* depot\_tools: See Install depot\_tools in [Checking out and Building Chromium for Windows](https://chromium.googlesource.com/chromium/src/+/HEAD/docs/windows_build_instructions.md#Install) 
+
+Make sure you add depot\_tools to the start of your PATH and it must be ahead of any installs of Python.
+
+Run the following commands
+```sh
+mkdir webrtc
+cd webrtc
+gclient
+fetch --nohooks webrtc
+gclient sync
+cd src
+gn gen out/Default
+ninja -C out/Default unpack_aecdump
+```
+The file is available at webrtc/src/out/Default/unpack\_aecdump.exe
+
+## How to inspect aecdump files
+
+Run the command:
+
+```
+unpack_aecdump.exe audio_debug.5.aecdump
+```
+
+:::image type="content" source="./media/extract-aecdump.png" alt-text="Screenshot of the extracted aecdump file.":::
+
+There are three different types of audio files extracted from the aecdump file
+
+* reverseN.wav: the rendered audio originated from the same process
+* inputN.wav: the captured audio, before audio processing.
+* ref\_outN.wav: the captured audio, after audio processing and will be sent to the network.
+
+If you think that audio quality issues are on the sending end, you can first check ref\_outN.wav, find the possible problem time points, and compare them with the same time points in inputN.wav to see if the audio quality issues are caused by the audio processing module, or if the audio quality was already poor in the source.
+
+