Skip to content

Conversation

@backportbot-nextcloud
Copy link

backport of #5551

When a call started and the VideoConstrainer was created the video track
was assumed to be already in high quality, so when the VideoConstrainer
was asked to apply again the high quality constraints it just ignored
the request. However, in some cases the browser does not initialize the
camera in high quality, so the camera was kept in a lower quality for
as long as the high quality was kept being requested.

Moreover, even if the browser initialized the camera with high quality
that quality might not be exactly the same as the one set when applying
the high quality constraints, so even in those cases the constraints
should be applied anyway for consistency.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
@nickvergessen nickvergessen merged commit f5ef0d3 into stable20.1 May 3, 2021
@nickvergessen nickvergessen deleted the backport/5551/stable20.1 branch May 3, 2021 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug feature: call 📹 Voice and video calls feature: frontend 🖌️ "Web UI" client

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants