- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jan 2025 23:05:06 +0000
- To: public-webrtc-logs@w3.org
I think we need to distinguish theoretical differences from ones that matter. My bar for the shim was to minimize refactoring, not design a zero-work drop-in. All examples presented so far (here and in #116) stop both the original track and the processed track on main thread at the same time, so shimming `stop()` hardly seems necessary. I agree with @youennf people are going to stop the processed track (which stops the worker clone per https://github.com/w3c/mediacapture-transform/issues/117#issuecomment-2502034790). Same with enabled. If they don't then yeah the processed track can outlive the original just fine. It's a feature. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2584708519 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 23:05:07 UTC