Given the subject, are you looking for a bandwidth setting/constraint on
RTCPeerConnection or just a working b=?
I believe Chrome has something like the former but it is not in the spec
AFAIK, so I don't know what the plan is for that. Maybe others here can
comment on that.
The width/height/framerate gUM constraints are my next item after this
work week.
..: Jan-Ivar :.
On 2/8/14 12:10 PM, Philipp wrote:
Is there any progress in bandwidth control in firefox lately?
On Friday, July 5, 2013 6:40:13 PM UTC+2, Adam Roach wrote:
On 7/5/13 01:36, Randell Jesup wrote:
In this case, I think Bryan is probably correct: b=AS:XXX or
b=TIAS:XXXX at the media level specifies you'd like that to be the
limit for *receiving* data on that m-line from one source
You are correct -- I had identified that b= was defined for declarative
SDP, and didn't find the string "b=" in RFC 3264, so I assumed it meant
the same thing (i.e., the bandwidth to be sent). By searching for
"bandwidth" in 3264, I see that it reverses the sense of "b=" for
negotiated SDP.
That being the case, we probably ought to open another bug for plumbing
this into the media engine, similar to what we're doing in Bug 881935
right now.
--
Adam Roach
Principal Platform Engineer
[email protected]
+1 650 903 0800 x863
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
