There have probably been other discussions around the topic. A proposal from 2016 to add a rational time value for seek() to solve rounding issues (still open as of June 2018):.A question from 2013 on whether there was interest to expose "versions of currentTime, fastSeek(), duration, and the TimeRanges accessors, in frames, for video data":.Not sure if these use cases remain relevant today: A list of use cases from 2012 for seeking to specific frames.An long thread from 2011 on Frame accuracy / SMPTE, which led to improvements in the precision of seeks in browser implementations:.
ACCURATE 4 PLUS
Plus that framerate may actually vary over time.Īlso, internal rounding of time values may mean that one seeks to the end of the previous frame instead of the beginning of a specific video frame.ĭigging around, I've found a number of discussions and issues around the topic, most notably: Conversion from/to times to/from frame numbers is doable but supposes one knows the framerate of the video, which is not exposed to Web applications (a generic NLE would thus not know about it).
The currentTime property takes a time, not a frame number or an SMPTE timecode. I've heard a couple of companies point out that one of the problems that makes it hard (at least harder than it could be) to do post-production of videos in Web browsers is that there is no easy way to process media elements on a frame by frame basis, whereas that is the usual default in Non-Linear Editors (NLE).
0 kommentar(er)
