- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Mar 2021 12:59:48 +0000
- To: public-webrtc-logs@w3.org
The main use case of the transform API so far is end-to-end encryption. I could see other use cases like appending additional data to a frame. In both cases, we are talking of media being transformed by a sender, sent to a receiver that does the inverse transform to render the (potentially augmented) media. It would be good to better understand the use cases you have in mind so that we break them down in requirements. For instance, the use cases I mentioned above do not need 'the input or output to a transform go somewhere other than the normal path'. It would also help understanding what signals we are talking about and the best way to handle them. Can you share more of the use cases? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/90#issuecomment-802815812 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 March 2021 12:59:50 UTC