search

jitsi / jitsi-meet

Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
https://jitsi.org/meet
Apache License 2.0
22.8k stars 6.68k forks source link

Low fps video camera upload chrome 126 vp9 #14937

Closed javierckr closed 2 weeks ago

javierckr commented 1 month ago

What happened?

When on a meeting with 3 or more participants the cameras of the participants using chrome are between 3 and 8 fps, tested on our own instance and on meet.jit.si, for testing on meet.jit.si you need to 1 participant on firefox to fall on vp9 codec instead of av1. It is not happening on chrome 115.

Platform

Browser / app / sdk version

Chromium and Google Chrome 126

Relevant log output

No response

Reproducibility

More details?

No response

pbirkants commented 1 month ago

Hi, I've also come across this weird behavior, and can contribute details on some observations.

I did some testing with various browser versions, and the issue was always present for VP9 video sources coming from Chrome/-ium 126 + Windows, and never occurred when downgrading to Chrome 124, or when using Chromium 126 on Linux, or when using AV1.

Additionally, when looking at details in chrome://webrtc-internals, I saw that the outbound-rtp stream is reported as having full, stable framerate (25 or 30fps), meanwhile receivers' inbound-rtp shows ~4x less (6-7fps or 8fps respectively) and the video is choppy. Audio is always fine. Configuring a higher target bitrate also did not change anything.

initially noticed in an older version of Jitsi, but also reproducible both on a freshly deployed docker-jitsi-meet instance with default settings (AV1 not enabled) in a LAN environment, and on meet.jit.si (by joining also with Firefox, as mentioned by OP).

cyrilfl commented 3 weeks ago

No update from anyone on this? Experiencing the same issue and do not know what to do.

saghul commented 3 weeks ago

Ping @jallamsetty1

jallamsetty1 commented 2 weeks ago

This was fixed on the bridge and the fix has been deployed to meet.jit.si already but I suspect it hasn't made to stable yet. We are planning to release new stable builds soon.