Actually addTransceiver() already takes an RTCRtpTransceiverInit with 3 existing members - adding a transform here would be consistent with the existing interface.
This seems reasonable and orthogonal to other discussions, so I'm opening this issue to discuss it. E.g. this:
From @alvestrand in https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1880210215:
This seems reasonable and orthogonal to other discussions, so I'm opening this issue to discuss it. E.g. this:
...would be equivalent to: