Open
Bug 1408462
Opened 7 years ago
Updated 2 years ago
The max-fr parameter does not work properly when low values of max-fs are used.
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
People
(Reporter: dminor, Unassigned)
Details
(Keywords: regression)
There appears to be a negative interaction between max-fr and max-fs when max-fs is set to a low value.
I did a bit of experimentation and with max-fr set to 15 and max-fs set to below 1300, the framerate is limited to around 16 - 18 frames per second rather than the 15 requested. If I don't set max-fr, the camera runs at 30. For higher values of max-fs, the framerate seems to stabilize at 15 frames per second
Comment 1•7 years ago
|
||
This is a followup from bug 1403714.
status-firefox56:
--- → ?
status-firefox57:
--- → affected
status-firefox58:
--- → affected
Keywords: regression
Comment 2•7 years ago
|
||
From https://bugzilla.mozilla.org/show_bug.cgi?id=1403714#c45, sounds like this is not a severe issue. Fix-optional for 57, we could still take a patch in 58.
Updated•7 years ago
|
status-firefox59:
--- → fix-optional
status-firefox60:
--- → affected
Updated•7 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•