Open
Bug 1278001
Opened 9 years ago
Updated 2 years ago
RTPSender maxBitrate only works for one sender
Categories
(Core :: WebRTC, defect, P3)
Core
WebRTC
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | affected |
| backlog | webrtc/webaudio+ |
People
(Reporter: drno, Unassigned)
References
Details
RTPSender's setParameter (or b=TIAS from bug 1276368) to limit the maxBitrate works with one sender. As soon as two senders use different maxBitrate's, e.g. one uses a restriction and the second no restriction, the total bandwidth stays under the limit and does not reach the sum of restriction plus the default bandwidth w/o restriction.
I verified in the debugger that the restrictions are properly set in both encoders/senders. So my current guess is that the bandwidth limiter kicks in and wrongly restricts the second encoder/sender.
|
Reporter | |
Updated•9 years ago
|
backlog: --- → webrtc/webaudio+
Rank: 25
|
||
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•