Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers


>Why would you only expect the `track` event on the initial OA exchange (keeping in mind that in the transceiver model, the remote track often exists prior to that first event as well)?

I guess I had the mental model that you get the `track` event when there is a new incoming track to consider. But never mind that, I guess you can design your code so that getting the event several times is no problem, e.g.
* check if the track is already handled - no need to do anything
* add it to a MediaStream used for rendering (or recording or whatever) - if the track is already a member this would be a no-op (from mediacapture-main: `If track is already in stream's track set, then abort these steps.`)

But that actually brings me back to the [first post here]( if multiple track events for the same is already handled by the app, why would getting it from multiple SRD(offer) be an issue?

GitHub Notification of comment by stefhak
Please view or discuss this issue at using your GitHub account

Received on Thursday, 18 January 2018 09:51:19 UTC