-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[MM-52657] AV1 support #8037
[MM-52657] AV1 support #8037
Conversation
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.
Tried an old version of mobile with new server, new version of mobile with new server, and just in case: new version of mobile with old server. Everything works. Thank you!
// Registering WebRTC globals (e.g. RTCPeerConnection) | ||
registerGlobals(); |
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.
Oh, nice! Didn't notice they had that. Kind of embarrassed I missed it, tbh...
Hi @streamer45, |
@DHaussermann The idea is to run this mobile build against both the latest plugin release and the AV1 PR so we can make sure no regressions related to screen sharing exist. |
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.
Tested and passed
- Tested current release of Calls with prod mobile release
- Tested current release of Calls with mobile builds from this PR
- Tested Calls AV1 PR with AV1 enable in combination with these builds and production mobile builds
- Tested Calls AV1 PR with AV1 disable in combination with these builds and production mobile builds
In all cases the Android and iOS clients had no issues receiving the video stream.
LGTM!
@streamer45 - Is there product or developer documentation impact expected for this Engineering PR? |
@cwarnermm There's a new system console config setting to control this functionality that we should likely document. |
@streamer45 - Can you direct me to those details please? I'm not seeing code in this PR that looks like a new config setting. |
@cwarnermm Yeah, it's the linked calls PR -> mattermost/mattermost-plugin-calls#795 |
Thanks, @streamer45!! |
Summary
PR adds experimental support for receiving AV1-encoded screen-sharing tracks. The change on this side is minimal as we only need to detect whether we support receiving AV1 or not. This is done through the new
RTCPeer.getVideoCodec
static method.To simplify further, I also modified some code in
calls-common
to make use of WebRTC globals that can be conveniently registered using the providedregisterGlobals
function.Related PRs
mattermost/mattermost-plugin-calls#795
mattermost/calls-common#34
Ticket Link
https://mattermost.atlassian.net/browse/MM-52657
Release Note