- From: Nigel Megitt via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jun 2018 16:02:52 +0000
- To: public-web-and-tv@w3.org
> The key thing is indeed to be able to act essentially in sync with the frame changes, so that you can match external actions to frame changes in the video. @Daiz as I just pointed out on the M&E call, this is only known to be true at the 25-30fps sort of rate, designed to be adequately free of flicker for video. It's unknown at high frame rates, and entirely inadequate at low frame rates, where synchronisation with audio is more important. We should avoid generalising based on assumptions that the 25-30fps rate will continue to be prevalent, and gather data where we don't yet have it. We also need a model that works for other kinds of data than subtitles and captions, since they may have more or less stringent synchronisation requirements. -- GitHub Notification of comment by nigelmegitt Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-398106111 using your GitHub account
Received on Monday, 18 June 2018 16:02:59 UTC