- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Jun 2018 08:24:58 +0000
- To: public-web-and-tv@w3.org
@boushley Thanks, that is useful! From a user experience perspective, how would the frame-by-frame stepping work in your case, ideally? 1. The user activates frame-by-frame stepping. Video playback is paused. The user controls which frame to render and when a new frame needs to be rendered (e.g. with a button or arrow keys). Under the hoods, the page seeks to the right frame, and video playback is effectively paused during the whole time. 2. The user activates frame-by-frame stepping. The video moves from one frame to the other in slow motion without user interaction. Under the hoods, the page does that by setting `playbackRate` to some low value such as `0.1`, and the user agent is responsible for playing back the video at that speed. In both cases, it seems indeed hard to do frame by frame stepping without exposing the current frame/presentation time, and allowing the app to set it to some value to account for cases where the video uses variable framerate. It seems harder to guarantee precision in 2. as seen in this thread [1], but perhaps that's doable when video is played back at low speed? [1] https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-396701652 -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-399018879 using your GitHub account
Received on Thursday, 21 June 2018 08:25:09 UTC