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

This is a major problem for existing applications, and IMO it is also a problem for new applications.
The issue is that by hard-coupling the control surface (i.e., the track) and the processing surface we are removing a lot of flexibility from applications and forcing them to introduce designs that are more complex than they need to be.
Treating a control surface separately from a processing surface is a common (and recommended) pattern in a lot of contexts and this one is not an exception.
There might be cases where coupling the control and processing surface is useful, but making it mandatory is a bad idea and we should fix that.


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


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

Received on Friday, 10 January 2025 11:28:32 UTC