level-asymmetry-allowed and profile-level-id capabilities and settings #382
In looking at the H.264 SDP used by Mozilla Firefox (see below), I noticed the level-asymmetry-allowed SDP parameter (set to 1, to indicate that FF supports level asymmetry).
In the ORTC API, we provide a profileLevelId capability within an RTCRtpReceiver (to indicate the maximum profile-level-id that a receiver can handle), as well as a profileLevelId setting within an RTCRtpSender (to configure the profile-level-id for the sender). Currently there is no levelAsymmetryAllowed capability.
Is there an assumption within the ORTC API that all implementations support level asymmetry? Also, since there is no profileLevelId capability within an RTCRtpSender, how does a developer determine the maximum profile-level-id that a sender can support?
Mozilla FF SDP returned by createOffer():
The text was updated successfully, but these errors were encountered: