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
I think it is a headache to allow doing this for things like urn:3gpp:video-orientation which have implications for the whole pipeline.
Disabling an extension via (local) renegotiation solves the same problem, do we need this one?
The text was updated successfully, but these errors were encountered:
Assuming it can be set via setOfferedRtpHeaderExtensions (the term offer here confuses me a bit) for negotiation, right? If so 👍 for getting rid of complexity. 🙂
setOfferedRtpHeaderExtensions operates before offer (and I think answer but it seems we need another test for that), active in setParameters is dynamic "within the envelope of the negotiated sdp" (a term that I would prefer to avoid :-))
remove ability to dynamically turn off sending of header extensions
via setParameters. This can also be achieved with local renegotiation.
Fixesw3c#112
it seems that the enabled property
https://w3c.github.io/webrtc-extensions/#attributes-0
in setParameters is not implemented.
I think it is a headache to allow doing this for things like urn:3gpp:video-orientation which have implications for the whole pipeline.
Disabling an extension via (local) renegotiation solves the same problem, do we need this one?
The text was updated successfully, but these errors were encountered: