On 12/24/2015 11:20 AM, Eric Rescorla wrote:
Hmm.. That's not what I see on calls between Nightly and Chrome on apprtc.
Right. I just tried an apprtc call to Chrome, and while we start around 300Kbps (as does Chrome), we both quickly ramp up. In my call, the ramp up was basically identical to ~1.4Mbps, when we stop and Chrome continuse up to ~3Mbps. The reason for this was that apprtc was using 1280x720 for Chrome, and 640x480 for Firefox. We adjust the bitrate limits when sending according to the input resolution and framerate; for 640x480@~30fps we max out the video at 1.3Mbps. For 1280x720 we would use a min of 600 and max of 2500Mbps.
Chrome used to use min 200, max 2000Mbps for everything, but that may have been modified, or apprtc may be playing with b=AS lines, which they allow apps to change and we don't (currently).
If video isn't adapting up, that implies that either you have poor bandwidth, very large amounts of jitter in the network (poor WiFi?), something is blocking RTCP (which will cause other problems too), or there's some form of mis-negotiation or incorrect SDP munging.
Try an apprtc call between the same two machines and watch the network stats. If that works normally, look at the negotiation, SDP munging, etc. Copies of the local and remove SDPs might help.
-- Randell Jesup, Mozilla WebRTC _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
