Re: [webrtc-pc] There are redundant steps in setCodecPreferences (#2183)

Revisiting this I don't think it is redundant.
The first part ensures there is at least one codec that works for both sending AND receiving. A must for the negotiation of a sendrecv transceiver to work.
The second part ensures that none of the codecs are one we do not support.
The first part already ensures that we do not succeed if your only codec preference is "FEC" because the first bit requires a "real" codec.

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

Received on Thursday, 25 April 2019 09:47:27 UTC