- From: Michael Hagar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Jan 2025 17:58:26 +0000
- To: public-webrtc-logs@w3.org
Thanks @jan-ivar for the suggestion on feature detection. In addition to setting the constraints themselves, there's other state our application maintains that are related to tracks. For example, if `applyConstraints` fails, we set state that indicates how to proceed in the future when the resolution should be upgraded. If the track is transferred, we would have to maintain duplicate versions of this state on the worker, or else introduce message posting mechanisms to sync related state back and forth between the worker and main thread every time we interact with the track. I'm not necessarily suggesting we add a new API, but would it be OK to support `MediaStreamTrackProcessor` and `VideoTrackGenerator` on the main thread, like Chrome does now? That would make it a lot easier for existing applications like our own to adopt. -- GitHub Notification of comment by mehagar Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2587803264 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 January 2025 17:58:27 UTC