Re: ReplaceTrack and track.id (Re: ReplaceTrack - need to evaluate alternatives) from Martin Thomson on 2015-04-14 (public-webrtc@w3.org from April 2015)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 14 Apr 2015 12:28:42 -0700
To: Justin Uberti <juberti@google.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <CABkgnnUZaSACA38EBu277Mo13dvdETAR17iz=hYfmnYYaTp9mg@mail.gmail.com>

On 14 April 2015 at 12:23, Justin Uberti <juberti@google.com> wrote:
> Basically, when you add a track, and thereby generate a new RtpSender, the
> "track id" associated with the sender is fixed for the lifetime of the
> RtpSender. So if A sends X, and then later does replaceTrack to send Y, this
> doesn't change anything for media or future signalling.
>
> In essence, this means that MSID really serves as the id of a RtpSender. If
> you want to change the id, removeTrack + addTrack to get a new RtpSender.


That works too.

Received on Tuesday, 14 April 2015 19:29:13 UTC