Constrain FrameRate in config.js does not work v. 2.0.5963-1

Hey guys,

im currently trying to constrain the FPS on my server but the suggensted syntax does not work.
Im always get the full FPS.
Is my syntax wrong or are there known problems regarding this option?

Version: 2.0.5963-1

Current setting:
// w3c spec-compliant video constraints to use for video capture. Currently
// used by browsers that return true from lib-jitsi-meet’s
// util#browser#usesNewGumFlow. The constraints are independent from
// this config’s resolution value. Defaults to requesting an ideal
// resolution of 720p.
constraints: {
video: {
frameRate: {
max: 16
height: {
ideal: 320,
max: 360,
min: 120


Did i do something wrong?

Best regards,

Hi, we got the same problems.
In Version 2.0.5963-1 we cannot lock the FPS to 16 or lower.
Anytime we activate the configuration we got full FPS of 29/30 Frames

Does anyone have an idea why?

Best Regards


with which Jitsi-meet version did you last see this function working ?

Im trying this function for the first time in Version: 2.0.5963-1.

from the way you were presenting this, I was thinking it was some kind of regression. Same for you @sb_cx ?

Absolut @gpatel-fr
I use the function in version 2.0.5390-3 without any probelms.
But in the newer one I can’t limit the FPS with the same synatx. I allready take a look in the jitsi documentation. I guess this was a bug in 2.0.5963-1 version
Best Regards,

I installed a 2.0.5390 especially for you and I can confirm that this version seems to limit the frame rate correctly, using Chrome 92.0.4515.159.
@saghul and/or @jallamsetty, could you have any insight about this, notably fix(RTC) drop the "old gUM" flow · jitsi/lib-jitsi-meet@ad5692d · GitHub

A little bit more insight for my case.

Version 2.0.5963-1 is our current validated Version. Everything works fine, execpt limiting the frame rate.

My best guess is, a bug in translating

video: {
frameRate: {
max: 16

into the w3c spec,

Maybe there is a workround with a different syntax?

Kind regards

Any new learnings here?
Still have the same issue.