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

I have a growing feeling that an important part of the issue discussed here is a strong disconnect between track cloning being initially designed to allow and facilitate disconnected track states (being able to apply different constraints to the various clones) and track cloning as the underlying mechanism for transferring tracks making it *hard* to keep synchronized states across transferred clones.

Since track state is fundamentally an off-js state, I wonder if having an explicit API to keep clone states synchronized would alleviate sufficiently many of these particular concerns.

-- 
GitHub Notification of comment by dontcallmedom
Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2589805994 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 12:37:36 UTC