- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Mar 2017 02:53:40 +0000
- To: public-webrtc-logs@w3.org
I ran into something again. The simulcast example is currently: ``` pc.addTransceiver(track, { direction: "sendrecv" encodings: [ { rid: "f" }, { rid: "h", scaleDownResolutionBy: 2.0 }, { rid: "q", scaleDownResolutionBy: 4.0 } ] }); ``` So clearly, at some point the intention was that you could specify some of the encoding parameters at `addTransceiver` time. Maybe the [[send encodings]] slot was going to be used to specify this logic. Do we still want to do this? If not, the example would need to change to do a `getParameters`/`setParameters` after `setRemoteDescription`. Maybe this would be a good interim topic. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1073#issuecomment-289966672 using your GitHub account
Received on Wednesday, 29 March 2017 02:53:47 UTC