You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pion used to match m lines in SDP by doing a simple comparison of the fmtp lines. This does not work in general, as some fmtp parameters are symmetric (they must have the same value on both sides for the m lines to match) and others are declarative (they only give additional information about what the announcing peer is able to send or receive). It might also be the case that some symmetric parameters can be omitted, indicating that the announcer will accept whatever value the other side finds convenient (not sure, the RFCs are unclear on this subject).
Here's the situation, as far as I can tell from a quick browse of the relevant documents:
the parameters profile-level-id and packetization-mode are symmetric, with weird matching for profile-level-id (see Improved h264 fmtp line parsing #1903);
level-asymmetry-allowed changes the matching algorithm;
all other parameters are declarative;
there are weird rules for sprop-parameter-sets.
The text was updated successfully, but these errors were encountered:
The only thing that remains is that the library does not prevent matching incompatible codecs, since there's a fallback matching algorithm that takes into consideration the mime type only:
Pion used to match m lines in SDP by doing a simple comparison of the fmtp lines. This does not work in general, as some fmtp parameters are symmetric (they must have the same value on both sides for the m lines to match) and others are declarative (they only give additional information about what the announcing peer is able to send or receive). It might also be the case that some symmetric parameters can be omitted, indicating that the announcer will accept whatever value the other side finds convenient (not sure, the RFCs are unclear on this subject).
Here's the situation, as far as I can tell from a quick browse of the relevant documents:
max-fr
andmax-fs
are declarative.profile-id
is symmetric, but may be omitted;max-fr
andmax-fs
are declarative.profile-level-id
andpacketization-mode
are symmetric, with weird matching forprofile-level-id
(see Improved h264 fmtp line parsing #1903);level-asymmetry-allowed
changes the matching algorithm;sprop-parameter-sets
.The text was updated successfully, but these errors were encountered: