W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2012

[whatwg] frame accuracy breaking case for 25fps / status of 29.97fps

From: adam k <lists@inconduit.com>
Date: Mon, 9 Jul 2012 12:46:20 -0400
Message-Id: <98159848-EF97-4868-9E8A-FF35AA44E5A1@inconduit.com>
To: whatwg@lists.whatwg.org
hi whatwg, long time listener first time caller.

i have a 25fps video, h264, with a burned in timecode.  it seems to be off by 1 frame when i compare the burned in timecode to the calculated timecode.  i'm using rob coenen's test app at http://www.massive-interactive.nl/html5_video/smpte_test_universal.html to load my own video.

what's the process here to report issues?  please let me know whatever formal or informal steps are required and i'll gladly follow them.

second question:

i'm aware that crooked framerates (i.e. the notorious 29.97) were not supported when frame accuracy was implemented.  in my tests, 29.97DF timecodes were incorrect by 1 to 3 frames at any given point.  

will there ever be support for crooked framerate accuracy?  i would be more than happy to contribute whatever i can to help test it and make it possible.  can someone comment on this?  

thanks so very much for bringing frame accuracy to html5 video and bringing me out of the dark days of flash video and NetStream.  

Received on Monday, 9 July 2012 16:47:01 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:43 UTC