- From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Mar 2019 22:24:19 +0000
- To: public-webrtc-logs@w3.org
wow... I can believe that. `msid` is just a **Web**RTC artifact to "associate" tracks within a `MediaStream`. It's just crazy that the RTP receptor depends on that to do sync stuff. What about if the source is not using `MediaStream` at all? Does this also affect the sender? I mean, if I call twice to `gUM` (one for audio and one for video) and I don't "mix" them into the same `MediaStream` and I do not pass any `MediaStream` to `addTransceiver`, will libwebrtc not care much about sending both tracks in sync? -- GitHub Notification of comment by ibc Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2114#issuecomment-470301669 using your GitHub account
Received on Wednesday, 6 March 2019 22:24:20 UTC