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

Re: [webrtc-pc] addTransceiver woes

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Tue, 02 Jan 2018 12:41:35 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-354758738-1514896894-sysbot+gh@w3.org>
A brief chat with @alvestrand cleared up some my confusion, that the intent is to use setParameters() to decide codec params and set direction and renegotiate as to then allow using replaceTrack() without it being rejected.

With such a conscious effort necessary to start sending, I think it makes more sense if by default it is "recvonly".

My interpretation is ontrack only fires in association with receivers being created with a track. That means at SRD() or if you addTransceiver() then no event should fire because you created it yourself.

There is no event for "now we are or are no longer receiving frames on a receiver". Receiving/not receiving frames is not associated with onmute/onunmute.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-354758738 using your GitHub account
Received on Tuesday, 2 January 2018 12:41:39 UTC

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