- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Apr 2017 22:30:30 +0000
- To: public-webrtc-logs@w3.org
> so setRemoteDescription with an a=msid:streamid trackid fires ontrack with a track whose id is 'trackid' only with an offer but not with an answer?! This doesn't make sense... > > Not that track ids are useful but this seems to make the msid concept rather useless. I agree it doesn't make sense. But signaling track IDs is redundant in the first place, now that we have MIDs. So, from my perspective, this is just legacy baggage we have to deal with, and it doesn't really matter what we do as long as the behavior is predictable. > Why? I expected that RtpReceivers (and their internal tracks) would just be created upon receipt of the remote SDP... But then the early media example wouldn't work. The RtpReceiver and track should be available right after `addTransceiver`, so it can immediately be hooked up to a `<video>` tag, before the remote SDP is received. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-294614331 using your GitHub account
Received on Monday, 17 April 2017 22:30:37 UTC