-
Notifications
You must be signed in to change notification settings - Fork 385
fix(meetings): checking audio level from RTP header before emitting DECODE_RESULTS_IN_ZERO_AUDIO_LEVEL #4550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
481fa74 to
15164b1
Compare
| RemoteStreamEventNames, | ||
| type VideoContentHint, | ||
| type StreamState, | ||
| type InboundAudioIssueEvent, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these exports is something I missed in some previous PRs, web app needs them (for now it's importing them directly from internal-media-core, but really it should do it via SDK)
c50f7b0 to
ac9fce5
Compare
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just change fix
|
|
||
| testEnableInboundAudioLevelMonitoring( | ||
| 'enables enableInboundAudioLevelMonitoring for multistream when browser is Chrome', | ||
| {isChrome: true, isEdge: false}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you need to pass isEdge: false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it's redundant, it's something left over from a previous version of the code where these were required, I've removed it now
COMPLETES #SPARK-728621
This pull request addresses
We incorrectly detect issues with remote audio level being zero when remote participants are unmuted but silent.
by making the following changes
Updating to latest internal-media-core (which includes new WCME) that only emits the INBOUND_AUDIO_ISSUE event with sub type DECODE_RESULTS_IN_ZERO_AUDIO_LEVEL when decoded audio level is zero while audio level in rtp header extension is not zero - this should minimize the false positives for these audio issue events we're seeing from our metrics.
This PR depends on:
Change Type
The following scenarios where tested
unit tests, manual testing with WCME and web app
The GAI Coding Policy And Copyright Annotation Best Practices
I certified that
I have read and followed contributing guidelines
I discussed changes with code owners prior to submitting this pull request
I have not skipped any automated checks
All existing and new tests passed
I have updated the documentation accordingly
Make sure to have followed the contributing guidelines before submitting.