- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Nov 2023 15:24:05 +0000
- To: public-webrtc-logs@w3.org
> what streams/tracks does the event even reference? We cannot really reuse the same MediaStream, otherwise local preview might start playing audio for instance. I think it would be new MediaStream(s) / MediaStreamTrack(s). > * The decision to source-inject is finalized when calling gDM. That is the main discussion point and there are various approaches outside of callbacks/events. Is the following a fair summary? - @eladalon1983 prefers early decision (simpler to implement, no real web dev need) - @jan-ivar prefers late decision (more convenient for web devs, prevent UA from not showing switch UI) > * All handlers get references to the same new stream and track(s), rather than to clones or independent tracks. I think this is a given. Additional question related to how switching would actually work. Say we have the following case: - gdm, only one video track V1 - switch -> one video track V2 and one audio track A1. - switch -> one video track V3 - switch -> one video track V4 and one audio track A2. In that case, we are expecting V1 to get the content of V2, V3 and V4. I am unclear about A1 and A2. Are we expecting that A1 does get migrated or not? What if A1 was exposed as part of gdm call? If migrating, what happens to A1 when V3 is live? It might be best to reduce the scope to only supporting migrating the first video track generated by gdm. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1819277241 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 November 2023 15:24:07 UTC