- From: Mark Foltz (Google) via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Sep 2022 21:36:52 +0000
- To: public-secondscreen@w3.org
Sorry for the late reply. It sounds like you want to configure a `<video>` element with metadata about audio, video, and text tracks, so the browser will render media controls as if the media was playing locally. However, you have some other solution for fetching and rendering the media on another device with WebRTC so you want the browser's media controls to control remote playback. I think there are a few solutions here. One idea is to pre-process your media tracks into a container that has the metadata you want, but does not have encoded audio and video data. It would still need to be valid media that the browser can render for the `<video>` element to respond to controls as expected. Then you would render something else locally in place of the video frames? If you don't need to use the browser's default media controls, then rendering your own media player controls avoids the need for these workarounds. I am not sure that this exact situation falls in the scope of the Remote Playback API as it is focused on cases where the browser implements remote playback (versus app-to-app media sharing through WebRTC or other means). -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/143#issuecomment-1262842938 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 September 2022 21:36:54 UTC