// Configure the SDP semantics used by this PeerConnection. Note that the
// WebRTC 1.0 specification requires kUnifiedPlan semantics. The
// RtpTransceiver API is only available with kUnifiedPlan semantics.
//
// kPlanB will cause PeerConnection to create offers and answers with at
// most one audio and one video m= section with multiple RtpSenders and
// RtpReceivers specified as multiple a=ssrc lines within the section. This
// will also cause PeerConnection to reject offers/answers with multiple m=
// sections of the same media type.
//
// kUnifiedPlan will cause PeerConnection to create offers and answers with
// multiple m= sections where each m= section maps to one RtpSender and one
// RtpReceiver (an RtpTransceiver), either both audio or both video. Plan B
// style offers or answers will be rejected in calls to SetLocalDescription
// or SetRemoteDescription.
//
// For users who only send at most one audio and one video track, this
// choice does not matter and should be left as kDefault.
//
// For users who wish to send multiple audio/video streams and need to stay
// interoperable with legacy WebRTC implementations, specify kPlanB.
//
// For users who wish to send multiple audio/video streams and/or wish to
// use the new RtpTransceiver API, specify kUnifiedPlan.
*转载自:https://blog.youkuaiyun.com/chinabinlang/article/details/80749822*
Plan B是一个m line里多路media stream(通过msid区分).JSEP是一个m line对应一个media stream.JSEP里边多个m line的使用有点tricky需要循环利用.目前Chrome还没支持JSEP,正在支持中. Firefox已经支持JSEP.
转载自:https://www.douban.com/note/666764171/

本文深入探讨WebRTC中的SDP语义选择,包括kPlanB与kUnifiedPlan的区别。kPlanB允许在单一mline中指定多路media stream,而kUnifiedPlan为每一路media stream创建独立的mline,映射到一个RtpSender和一个RtpReceiver。文章还讨论了不同语义对多路音频/视频流的支持及与旧版WebRTC实现的互操作性。
1507

被折叠的 条评论
为什么被折叠?



