- From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Jan 2018 00:19:14 +0000
- To: public-webrtc-logs@w3.org
Related question: Why does the [ontrack](https://w3c.github.io/webrtc-pc/#dom-rtctrackevent) event come with a `streams` field (`FrozenArray<MediaStream>`)? > The `streams` attribute returns an array of MediaStream objects representing the MediaStreams that this event's `track` is a part of. If the sender and receive `tracks` are decoupled then there is no chance for "duplicated" receiving `tracks`, so it's impossible that the same `track` belongs to more than one `stream`. In the other side, I don't understand why we need the `msid` at all. Having a `stream` id within the transceiver is useful to group tracks into a stream. But we don't need the "more track id" at all... -- GitHub Notification of comment by ibc Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1718#issuecomment-355437732 using your GitHub account
Received on Friday, 5 January 2018 00:19:22 UTC