Skip to content

Commit 65de140

Browse files
committed
Address Acrolinx comment
1 parent 05dbbb7 commit 65de140

File tree

1 file changed

+8
-8
lines changed
  • articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues

1 file changed

+8
-8
lines changed

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/speaker-issue.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -35,25 +35,25 @@ If the user uses Windows, they should also check the volume mixer settings and a
3535

3636
:::image type="content" source="./media/apps-volume-mixer.png" alt-text="Screenshot of volume mixer.":::
3737

38-
If your are using Web Audio API in your application, you might also check if there is `AudioRenderer error with rendering audio code: 3` in the log.
38+
If you are using Web Audio API in your application, you might also check if there's `AudioRenderer error with rendering audio code: 3` in the log.
3939
This error occurs when there are too many AudioContext instances open at the same time, particularly if the application doesn't properly close the AudioContext or
40-
if there is an AudioContext creation associated with the UI component refresh logic.
40+
if there's an AudioContext creation associated with the UI component refresh logic.
4141

4242
## References
4343
### Troubleshooting process
44-
If a user cannot hear sound during a call, one possibility is that the participant has an issue with their speaker.
45-
The speaker issue is not easily detected and usually requires users to check their system settings or their audio output devices.
44+
If a user can't hear sound during a call, one possibility is that the participant has an issue with their speaker.
45+
The speaker issue isn't easily detected and usually requires users to check their system settings or their audio output devices.
4646

4747
Below is a flow diagram of the troubleshooting process for this issue.
4848

4949
:::image type="content" source="./media/speaker-issue-troubleshooting.svg" alt-text="Diagram of troubleshooting the speaker issue.":::
5050

51-
1. When a user reports that they cannot hear audio, the first thing we need to check is whether the incoming audio is silent. The application can obtain this information by checking `audioOutputLevel` in the mediastats.
51+
1. When a user reports that they can't hear audio, the first thing we need to check is whether the incoming audio is silent. The application can obtain this information by checking `audioOutputLevel` in the media stats.
5252
2. If the `audioOutputLevel` value is constantly 0, it indicates that the incoming audio is silent. In this case, ask the user to verify if the speaking participant is muted or experiencing other issues, such as permission issues, device problems, or network issues.
53-
3. If the `audioOutputLevel` value is not always 0, the user may still be unable to hear audio due to system volume settings. Ask the user to check their system volume settings.
53+
3. If the `audioOutputLevel` value isn't always 0, the user may still be unable to hear audio due to system volume settings. Ask the user to check their system volume settings.
5454
4. If the user's system volume is set to 0 or very low, the user should increase the volume in the settings.
55-
5. In some systems that support app-specific volume settings, the audio volume output from the app may be low even if system volume is not. In this case, the user should check their volume setting of the app within the system.
55+
5. In some systems that support app-specific volume settings, the audio volume output from the app may be low even if system volume isn't low. In this case, the user should check their volume setting of the app within the system.
5656
6. If the volume setting of the app in the system is 0 or very low, the user should increase it.
5757
7. In certain cases, the audio element in the browser may fail to play or decode the audio, you can find an error message `AudioRenderer error with rendering audio code: 3` in the log.
5858
8. A common case for the AudioRenderer error is that the app uses the Web Audio API but doesn't release AudioContext objects properly. Browsers have a limit on the number of AudioContext instances that can be open simultaneously.
59-
9. If you still cannot determine why the user cannot hear sound during the call, ask the user to check their speaker device or select another audio output device. Note that not all platforms support speaker enumeration in the browser. For example, you cannot select an audio output device through the JavaScript API in the Safari browser or in Chrome on Android. In these cases, you should configure the audio output device in the system settings.
59+
9. If you still can't determine why the user can't hear sound during the call, ask the user to check their speaker device or select another audio output device. Note that not all platforms support speaker enumeration in the browser. For example, you can't select an audio output device through the JavaScript API in the Safari browser or in Chrome on Android. In these cases, you should configure the audio output device in the system settings.

0 commit comments

Comments
 (0)