Re: Sense of the WG on mediacapture-transform API

These are my personal responses. I welcome other Mozillians and members to
share their views.

At the WebRTC WG Virtual Interim meeting on Thursday, October 14, 2021 we
> discussed the path forward on mediacapture-transform API.  The slides from
> the meeting are available here:
>
> https://docs.google.com/presentation/d/1rdaRvl3h3viqvndyJVzwIAPtOpMjx_2u7q7MBHUwbyY/
>
> We would now like to get a "sense of the WG" on the following questions:
>
> Question 1:  Should mediacapture-transform be based on streams?
>

Yes.

Question 2: Should mediacapture-transform support audio?
>

Undecided.

Question 3: Should mediacapture-transform be exposed on the main thread?
>

No. Contention on the main thread is common and unpredictable, leading to
intermittently missed realtime deadlines and media stutter. Workers provide
a dedicated environment practically free of contention. [1]

We need a worker-first API, to encourage good practice. People who need
this on the main thread can still transfer streams to the main thread if
they wish (opposite direction of Chrome's MSTP/MSTG today). I haven't heard
any compelling main thread use cases that aren't transitionary, and cannot
suffer this workaround.

[1] https://www.youtube.com/watch?v=7Rrv9qFMWNM&t=494s

Potential answers to the questions are "Yes", "No" or "Undecided".
>
> Please respond to this "Sense of the WG" poll by Monday, October 25, 2021
> at midnight Pacific Time.
>
>
>
>
>
>
>

-- 
.: Jan-Ivar :.