Open Bug 1688342 Opened 3 years ago Updated 3 years ago

maxBitrate is not working correctly for both audio and video

Categories

(Core :: WebRTC, defect, P3)

Firefox 84
defect

Tracking

()

People

(Reporter: csantos, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36

Steps to reproduce:

  1. Run this fiddle https://jsfiddle.net/charlietwilio/kLfrb7zu/3
  2. Click Start button
  3. Click the radio button to set maxBitrate

Actual results:

Audio bitrate remains the same. Video bitrate is changed but is not limited to the set maxBitrate. The actual bitrate is significantly higher than the set maxBitrate. On chrome and safari, this works find.

I found the two similar bug below, but they don't mention anything about video bitrate.
https://bugzilla.mozilla.org/show_bug.cgi?id=1278001
https://bugzilla.mozilla.org/show_bug.cgi?id=1573726

Hi,

On my end the "actual audio and video bitrate" stays at "0" no matter which radio button is selected so I wasn't able to reproduce the issue.
However, I'm going to set a component to get this issue looked at by the development team, although, this might be a duplicate of Bug 1573726

Thank you for reporting!

Status: UNCONFIRMED → NEW
Component: Untriaged → WebRTC
Ever confirmed: true
Product: Firefox → Core
Severity: -- → S3
Depends on: 1401592
Priority: -- → P3

Two issues here AIUI:

  • Audio senders don't follow maxBitrate at all
  • Actual video bitrate is higher than maxBitrate

Audio will be fixed by bug 1401592.

Video is a stats issue I believe, because we report the total number of rtp bytes sent, whereas the spec (indirectly) says to exclude header bytes. This will be fixed by bug 1654112.

Or did you measure "The actual bitrate is significantly higher than the set maxBitrate" in some way other than through stats?

Depends on: 1654112

Your understanding is correct. I measured the bitrate through stats. Thanks for looking into this.

You need to log in before you can comment on or make changes to this bug.