Re: [mediacapture-transform] Out-of-main-thread processing by default (#23)

The option of using  w3c/mediacapture-extensions#16  also would allow getting access on the main thread.
Also, I don't think allowing access on the main thread is such a dangerous thing that should be forbidden at all costs, especially if the result is a much more complex API. After all, today what is being used is canvas with media access on the main thread, and it works in production for many applications.
About the AudioWorklet as the only solution, I need to study the pros and cons, but some feedback I have seen from developers is that timestamping from the AudioWorklet makes AV sync more difficult, for example (i.e., the timestamps are not from the microphone, but from the worklet).  I need to confirm if this is an implementation bug or WAI, but it's something some developers are reporting. And, of course, WebCodecs integration is more difficult with WebCodecs.

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


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

Received on Thursday, 29 April 2021 15:24:25 UTC