[FFmpeg-trac] #9390(undetermined:new): Wrong FPS used for timecode computation mangles timecodes
FFmpeg
trac at avcodec.org
Sat Aug 28 18:28:16 EEST 2021
#9390: Wrong FPS used for timecode computation mangles timecodes
-------------------------------------+-------------------------------------
Reporter: Marcelo | Owner: (none)
Magnasco |
Type: defect | Status: new
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: timecode | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Marcelo Magnasco):
Replying to [comment:3 Balling]:
> Yes please paste on dropbox:
> {{{
> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7ffb6b80ac00] Using non-standard frame rate
29/1
>
> }}}
> file. "480p/60fps preview of 008" file you attached is useless.
No, Balling, it is NOT useless. The clip is 59.94fps and read as such by
every other software, but ffprobe sees both 59/1 and 59.94:
{{{
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f911e00c400] Using non-standard frame rate
59/1 [...]
Stream #0:0(eng): Video: h264 [...] 59.94 fps, 59.94 tbr, 60k tbn,
119.88 tbc (default)
}}}
I have nevertheless uploaded all clips to our server:
[http://sur.rockefeller.edu/Plone/ffmpeg-timecode-issues]
Let me again reiterate: the only place in the ff suite where the FPS is
incorrectly truncated to an integer is upon reading the timecode, whereby
the truncated FPS is used to convert frames-since-midnight to hh:mm:ss:ff.
Even if I transcode the clip using, say, ffmpeg concat, the new clip is
created as 59.94 and the hh:mm:ss:ff is translated to frames-since-
midnight using the correct frame rate.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9390#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list