- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Jan 2024 20:34:02 +0000
- To: public-webrtc-logs@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-encoded-transform:
== Should RTCRtpTransceiverInit have sendTransform and receiveTransform members? ==
From @alvestrand in https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1880210215:
> 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:
```js
const transceiver = pc.addTransceiver(track, {
direction,
streams,
sendEncodings,
sendTransform,
receiveTransform
});
```
...would be equivalent to:
```js
const transceiver = pc.addTransceiver(track, {sendEncodings});
transceiver.direction = direction;
transceiver.sender.setStreams(streams);
transceiver.sender.transform = sendTransform;
transceiver.receiver.transform = receiveTransform;
```
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/221 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 8 January 2024 20:34:04 UTC