On 5/15/15 7:21 AM, Randell Jesup wrote:
On 5/14/2015 2:23 PM, [email protected] wrote:

Once the call is established between browsers, video deteriorates until the keyframe refresh. This was not happening in Firefox 37, so it appears a change may have occurred to make Firefox more reliant upon the rtcp pli in version 38. In the same situation, Chrome only responds with 'ccm fir' and video keeps good quality throughout.

We did a major rewrite of the negotiation code in 37, and in 38 added multistream and bundle (and a lot of fixes for things); so it's certainly possible there was a regression in 38. Did 37 (or 36) answer in the same way to a "ccm fir"-only offer?
I'm pretty sure this was the behavior all along; signaling_unittests has several test-cases that require the answerer to add rtcp-fbs that weren't in the offer.

Best regards,
Byron Campen
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media

Reply via email to