W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2018

Re: [webrtc-pc] addTransceiver woes

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Wed, 03 Jan 2018 18:24:02 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-355087109-1515003840-sysbot+gh@w3.org>
@jan-ivar
> @fippo It would not, because it fails the following test for re-use:
> 
> "The sender has never been used to send. More precisely, the [[CurrentDirection]] slot of the 
> RTCRtpTransceiver associated with the sender has never had a value of sendrecv or sendonly."

That is surprising. 

Ignoring CurrentDirection, what audio data is the sender sending after addTransceiver('audio')?
Or taking CurrentDirection into account, does addTransceiver('audio') create a sendrecv offer? With what track in the msid? If there is a track, is RTCRtpSender.track still optional?

> We decided long ago replaceTrack should never negotiate. I've heard no reason here to reopen that.

+1

-- 
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-355087109 using your GitHub account
Received on Wednesday, 3 January 2018 18:24:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:58 UTC