1573726 - maxBitrate not working for audio RTCRtpSender (opus)

Status: NEW

(Core :: WebRTC, defect, P2)

Description

[Manjesh Malavalli]

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

Steps to reproduce:

1. Run https://jsfiddle.net/z45w2xLm/ in a new tab.
2. Observe the iframe in which the JSFiddle is running.

Actual results:

The logged outgoing audio bitrate is constant irrespective of the value of "maxBitrate" set using RTCRtpSender.setParameters().

NOTE: This JSFiddle works on Chrome and Safari.

Expected results:

The logged outgoing audio bitrate should approximately match the value for "maxBitrate" set using RTCRtpSender.setParameters() (12000).

Comment 1

[ovidiu boca[:Ovidiu]]

I tested on Mac OS X 10.14 and Windows 10 with FF 68 release, FF Beta 69.0b14 and Nightly 70.0a1(2019-08-18) and I can reproduce the issue, in my case the value is around 72000.

Comment 2

[Alastor Wu [:alwu]]

Hi, Andreas,
Is this something you are familiar with? Or do you know who is the best fit for this issue?
Thank you.

Comment 3

[Andreas Pehrson [:pehrsons]]

Byron, do we support maxBitrate for audio?

Comment 4

[Byron Campen [:bwc]]

I don't think so? It looks like most of that stuff only works if rid is being used, which only works on video. I suspect that this stuff will need to be fixed over in bug 1401592.

Comment 5

[Andreas Pehrson [:pehrsons]]

FWIW maxBitrate and scaleResolutionDownBy definitely works without rid for video: https://jsfiddle.net/pehrsons/7L9k7zLq/

Comment 6

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

Passing over this in triage. :bwc, does the fiddle in comment 5 change what you said in comment 4? Should be mark this as related to bug 1401592 in some way -- dupe, is work we could break off from that bug, something else?

Comment 7

[Byron Campen [:bwc]]

I think this is still video-only.

Comment 8

[Michael Froman [:mjf]]

Marking P2 to match blocking bug.