FWIW, it seems to me that `replaceTrack` does quite a bit of things (I mean that the content of the RTP packets going over the wire change), while `addTrack` does almost nothing (it mostly returns a sender, but that sender's transports are `null`). To get anything out of an `addTrack` you need to do the createOffer, setLocal..... things. As @jan-ivar points out in https://github.com/w3c/webrtc-pc/issues/1677#issuecomment-349862300 there can be cases when an off-main-thread examination of the source would be needed for `replaceTrack`. Are there strong reasons why we would change `replaceTrack`? -- GitHub Notification of comment by stefhak Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1677#issuecomment-354733023 using your GitHub accountReceived on Tuesday, 2 January 2018 09:59:41 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC