On 6/2/2015 8:57 AM, [email protected] wrote:
Hi all,
My device doesn't work again with FF39 webrtc. After tracing FF39 source, I
find my sdp is denied because my profile-level-id=4d0028. This profile-level-id
indicates main profile, but FF39 requires constrained baseline profile? (In
JsepCodecDescription.h, function ParametersMatch)
Why did FF39 make this change? Does anyone can help me? Thanks.
Please read RFC 6184, the spec for H264 packetization and SDP.
Main Profile is never a match for constrained baseline (or for anything
other than Main Profile). If you want to support more than one profile,
you must offer multiple profiles on different payload types. If you
receive an offer for profile X, you must agree to profile X - you cannot
answer with profile Y. (note: profile-level-id includes both profile
and level info, and there are some "equivalent" combinations of
constrainsts and profiles - but this discussing nits; Main Profile never
will equal baseline constrained.
Baseline Constrained is what has been mandated as the MTI for webrtc.
One can support higher, but you must support that.
There are more details (and we may relax the spec requirements for exact
matches to allow "Baseline" to match "Constrained Baseline", for
interoperability), but those are the basics. Anything that allowed a
Main Profile through before was a bug.
--
Randell Jesup, Mozilla (and author of RFC 6184)
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
