- From: Aaron Boushley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Jun 2018 18:34:35 +0000
- To: public-web-and-tv@w3.org
@tidoust our current experience is that the user has a skip ahead / skip back X seconds control. When they pause that changes to a frame forward / frame back control. So we're definitely looking at usecase #1. And if you're going for playback at something like 1/10 of normal speed (or 3-6 fps) you can pretty easily pull that off in JS if you have a way of progressing to the next frame or previous frame. This use case feel like it should be easily doable, although I think it'll be interesting if we can do it in a way that enables other use cases as well. @dholroyd we've definitely seen some of these off by a single frame issues in our redaction setup. Would be great if there was a better way of identifying and linking between a web client and a backend process manipulating the video. I believe one of the keys for the editing style use case is that while we want playback to be as accurate as possible, the key is that when paused it needs to be exactly accurate. -- GitHub Notification of comment by boushley Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-399201762 using your GitHub account
Received on Thursday, 21 June 2018 18:34:39 UTC