- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Dec 2017 10:41:18 +0000
- To: public-webrtc-logs@w3.org
I think it would make sense if replaceTrack() could trigger a renegotiation. If not needed, great, just replace the track, otherwise treat it like an addTrack()-sender in that it doesn't start sending until the O/A cycle has occurred. If we want it to be able to fail in case renegotation is needed because we don't want black frames until the O/A cycle has completed (in the case of already sending another track), then another operation is needed to say "I want to be able to send this track" such that when that operation completes, including the O/A, you can do replaceTrack() again. Now if you want to say "I want to send this track" you have to addTrack(), since replaceTrack() will prematurely fail before O/A and doesn't allow you to send tracks requiring different codec settings than the default O/A set of codec settings. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-354429524 using your GitHub account
Received on Friday, 29 December 2017 10:41:20 UTC