Conversation
|
(It seems pr-preview did not run even if the PR passes the checks, any idea why @dontcallmedom?) |
|
I don't know re pr-preview, and don't think I have an easy way to debug it either unfortunately |
| ### Integration with real-time video processing ### {#usecase-real-time-video-processing} | ||
|
|
||
| The user experience of WebRTC-based video conferencing is enhanced using real-time video processing. For example, background blur implemented using a [[#usecase-segmentation]] model blurs the background in the user's live camera feed. To satisfy the performance requirements of this use case, the WebNN API integrates with primitives from other Web APIs that make up the media pipeline to allow WebNN API-based transformation of real-time video streams. | ||
|
|
There was a problem hiding this comment.
Should the full-GPU video processing pipeline be a requirement? For other Web APIs, should we mention WebGPU and WebGL? Because it should require the pre/post-processing are also on the GPU.
There was a problem hiding this comment.
Thanks for the proposal, that was the key question on my mind also. Let's discuss this on our call to capture the whole group's perspective.
|
Reviewed on WebML WG Teleconference – 27 January 2022: https://www.w3.org/2022/01/27-webmachinelearning-minutes.html#t15 |
In https://www.w3.org/2022/01/13-webmachinelearning-minutes.html#t06 it was suggested we add a real-time video processing use case. Here's a proposal for that.
A few questions: