- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Feb 2025 19:03:32 +0000
- To: public-webrtc-logs@w3.org
[audio,video] + video clone + audio clone: https://jsfiddle.net/fippo/w7z91b8k/1/ [show link](https://jsfiddle.net/fippo/w7z91b8k/1/show) Current state: | Browser | order | |----------|-------| |"make everyone unhappy" | audio, video, video, audio | | Chrome | audio, audio, video, video| | Firefox | audio, video, video, audio| |Safari| track-id-order as we learned| I do not think this this is an improvement. We also need to be careful about remote tracks as shown by this which puts video first, then audio in the SDP: https://jsfiddle.net/fippo/ec1puh6w/ The risk of causing breakage in how this translates to SDP is too big. Multiple tracks per kind and then using that with a peer connection does not seem like a big use-case either. I'm happy to send a PR updating https://w3c.github.io/webrtc-pc/#legacy-interface-extensions but the biggest compat-win would be Safari stopping to randomize the order. (and note that adapter does not interfere with `MediaStream.getTracks()`, only with legacy `addStream` order) -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1028#issuecomment-2666670131 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 February 2025 19:03:33 UTC