Re: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC (#1174)

So I made the "playground approach" work, see [here](
It doesn't extract the tracks in resolution order but that was a weak assertion anyway. And we get the decoded images so can query their resolution. There are some rough edges such as relying on plan-b in Chrome in order to generate an answer that is mid- and rid-less but this  should still work with unified plan with slight modifications (which are already in the firefox code)

Ironically Chrome misinterpreted a=msid: without any a=ssrc:msid lines and got confused by the addition of a=ssrc:... msid later. I think Taylor wrote that :-)

GitHub Notification of comment by fippo
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 5 March 2019 09:25:26 UTC