Re: RtpReceiver: controlling the id attribute of the received track?

You mean that you want the RtpReceiver.track created by the RtpReceiver to
have a particular track.id instead of being some random thing?

I hadn't thought of that, but now that you mention it, it does sound
reasonable.  We can't add track.setId(...).  That's outside the scope of
ORTC.  But maybe we could have a RtpReceiver.setTrackId(...) that can only
be called before you call RtpReceiver.receive() (calling it after would
either blow up or be a no-op).


On the other hand, I think that apps shouldn't use track IDs for anything
anyway.  They should use MIDs instead.  So I'd prefer that this weren't
needed in the first place.



On Sun, Jul 26, 2015 at 2:45 PM, Philipp Hancke <fippo@andyet.net> wrote:

> i am thinking about mapping
> https://tools.ietf.org/html/draft-ietf-mmusic-msid-10
>
> At the javascript level, the gist of this is (as I understand it) to allow
> a correlation between SDP operations and onaddstream. For multiparty
> applications (using plan B) I add a new msid in the SDP and sometime later
> get an onaddstream and need some way to correlate that, in particular when
> adding multiple new streams at the same time.
>
> Now ignoring that with ORTC i'm in charge and don't get streams/tracks
> popping up at random...
> is there a way I can control the id of the Receiver's track? The track's
> id is readonly so I can't change it.
>