- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jan 2025 15:15:24 +0000
- To: public-webrtc-logs@w3.org
Thanks for the feedback! > * It is indeed annoying to have to feature detect by first creating a Worker. I'm not aware of any other API that is Worker only To echo what Jan-Ivar said, this can be detected synchronously by checking whether a `MediaStreamTrack` is transferable or not on a window's `MessagePort`. This is similar in spirit to feature detection of `RTCDataChannel` in workers: - In theory, a web page would need to spin a worker to feature detect that it exists in a worker and can be transferred to a worker. - In practice, this can be done by trying to transfer a `RTCDataChannel` on a window's `MessagePort`. > * the correct way to solve this would be to postMessage constraints to the worker Right, this is the current way of doing things. We could try to think of ways to improve things but we should be careful and do this based on use cases. For instance, a camera track can be cloned to apply frame rate/resolution decimation. This is not the case for VideoTrackGenerator and might be something we could try to improve. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2575548923 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 January 2025 15:15:25 UTC