- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jan 2018 21:27:17 +0000
- To: public-webrtc-logs@w3.org
> That is surprising.
Sure, though this is easily remedied by avoiding `addTrack`.
> does addTransceiver('audio') create a sendrecv offer?
Yes, the [webidl](https://w3c.github.io/webrtc-pc/#idl-def-rtcrtptransceiverinit) `direction = "sendrecv";` makes it indistinguishable from
```js
addTransceiver('audio', {direction: 'sendrecv'})
```
> With what track in the msid?
Random uuid. [Try it](http://jsfiddle.net/jib1/8wjb2n7f/).
> what audio data is the sender sending after addTransceiver('audio')?
Nothing is sent, but the remote end gets a receiver with a silent muted track. Support:
*"If track is `null` then the RTCRtpSender does not send."*
*"Initialize track.muted to true."*
*"A muted or disabled MediaStreamTrack renders either silence (audio), black frames (video), or a zero-information-content equivalent."*
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-355132102 using your GitHub account
Received on Wednesday, 3 January 2018 21:27:24 UTC