Re: [mediacapture-transform] We shouldn't require track transferability (#113)

> If the app wants to do VideoFrame handling out of main thread in an optimal way, the standardized API is the way
> forward.

This argument is specious. The API currently in the spec (with a lot of "no consensus" remarks that make it impossible to move that API to PR) is a proposal. The points made by @guidou and @mehagar indicate that the API currently in the spec may not be the best for developers.

Applications that need to move frame processing to a worker, but have no need to move the control surfaces represented by MediaStreamTrack to the worker, should be able to do so.
(the argument that they should be able to do frame processing on the main thread if they choose to do so is one that we already know that we don't have consensus on, but it's orthogonal to the issue discussed here.)

-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2589305856 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 14 January 2025 08:32:01 UTC