henbos

Add replaceStream to MediaRecorder

13

Fixes #167 *** Preview | Diff

Is "same PT, different FMTP lines" allowed in BUNDLE?

6

While working on https://github.com/w3c/webrtc-stats/issues/662#issuecomment-1232989049, we discovered that Chrome is able to handle a BUNDLEd transport where different m= sections use the same codec and payload type but where the FMTP...

Update WPTs to not be kind-agnostic

3

The current tests are happy with either video or audio metrics, but some are only defined for one of the kinds. Having WPTs have separate tests for different kinds would...

Codec stats reveal hardware information which could be used for fingerprinting

1

This was previously discussed in #550. The reason for creating a separate issue specifically for `codec` is that this information is already exposed in `RTCRtpSender/RTCRtpReceiver.getCapabilities(kind).codecs`. Therefore it is likely that...

Width/height as setting should be configured, not native.

2

Add similar clarifications as we did in https://github.com/w3c/mediacapture-main/pull/908/files but for width and height. For example the native camera resolution may be bigger than what we see due to scaling or...

setCodecPreferences, sendonly codecs and dummy codecs

21

As of recent changes, we force you to have at least one codec capable of receiving, regardless of direction, or else `setCodecPreferences` throws. But we also allow codecs of any...

If a preferred codec is filtered out, does it still get assigned a PT?

16

Use case: I want to signal in the SDP that I support sending X, but my transceiver is `sendrecv`. X is filtered out from the preference list at createOffer, so...

Proposing setCodecPreferences to deal with both send and recv codecs

6

Based on prior discussions such as https://github.com/w3c/webrtc-pc/issues/2937#issuecomment-1942031155, here's a concrete proposal which I think fixes unidirectionality, requires no changes to JSEP (consistent with https://github.com/w3c/webrtc-pc/issues/2938#issuecomment-1942116384) and avoids backwards compat issues introduced...

Existing setCodecPreferences NOTE is wrong and should be deleted

4

The second NOTE under [setCodecPreferences](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-setcodecpreferences) says: > NOTE > Due to a recommendation in [[SDP](https://w3c.github.io/webrtc-pc/#bib-sdp)], calls to [createAnswer](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-createanswer) SHOULD use only the common subset of the codec preferences and the...

Transceivers stopped prior to being negotiated are never removed from the set of transcievers

7

The spec has this to say about removing stopped transcievers and it happens in response to negotiating: > - If description is of type "[answer](https://w3c.github.io/webrtc-pc/#dom-rtcsdptype-answer)", then run the following steps:...