webrtc-extensions
webrtc-extensions copied to clipboard
w3c
A repository for experimental additions to the WebRTC API
Fixes: #196. Enumerate examples of situations in which `icecandidatepairremove` is fired, including ICE restart. This makes it clear that the event is fired and `[[CandidatePairs]]` is cleared in the event...
Addresses: w3c/webrtc-pc#2930. This change is built on top of w3c/webrtc-pc#2961, which converts RTCIceCandidatePair from a dictionary to an interface. - Change RTCIceCandidatePairEvent to contain a single RTCIceCandidatePair attribute. - Modify...
Filed as a follow-up to [this comment](https://github.com/w3c/webrtc-extensions/pull/194#discussion_r1457986273). The reason why I filed it is I'm not sure whether or not this is already covered by existing ICE pair removal steps....
### Background There is missing possibility to force jitter buffer to operate with specific delay. Existing attribute jitterBufferTarget enables setting of minimum delay, but upper bound is not controllable from...
Add an explainer for the upcoming RTCRtpSenderEncodedSource extension proposal *** Preview | Diff
the spec links to [RTP Header Extension for Absolute Capture Time](https://webrtc.org/experiments/rtp-hdrext/abs-capture-time) as a reference; that document is not a standards, but claims that "once experience has shown that it is...
Moved from https://github.com/w3c/webrtc-pc/issues/2346 Current browsers do not add pages that have a live (or connected) peer connection to the b/f cache. It would be interesting to enable this. One possibility...
We all know and love `scaleResolutionDownBy`... it let's you do this: Capture 720p and apply expensive video effects on the track. Send {active, scaleResolutionDownBy:1 (720p)} + {active, scaleResolutionDownBy:2 (360p)} simulcast....
Looking at https://w3c.github.io/webrtc-extensions/#rtcrtpencodingparameters, a new parameter "codec" is added. However, it is not used in any of the algorithms in section 7 (parameters.codec**s** is used in 7.2.1, presumably that refers...
## Background Encode complexity settings are hardcoded for WebRTC's built-in encoders (libvpx VP8/VP9, libaom AV1 and OpenH264). The settings depend on platform, number of CPU cores and video resolution and...
