[FFmpeg-trac] #9710(undetermined:new): 59.94 fps timecode mis-read
FFmpeg
trac at avcodec.org
Sun Apr 3 19:17:30 EEST 2022
#9710: 59.94 fps timecode mis-read
-------------------------------------+-------------------------------------
Reporter: jdachik01 | Owner: (none)
Type: defect | Status: new
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: timecode | Blocked By:
59.94 |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by jdachik01):
Replying to [comment:3 Balling]:
> Please provide the "S1H 119.88" file. You do understand it is just
120/1.001, right?
Yes, I'm aware of the fractional values (29.97 = 30000/1001, etc.). And
clearly there is some relation to the frame rate in comparison to 29.97
that is at play. It turns out I was wrong, in part, about the S1H file. I
have a version of ffmpeg from 2020 that cannot read its timecode at all,
but the one I just grabbed in the last few days can read it (though
incorrectly). ffmpeg (from 2022) seems to be running some calculation
against the starting timecodes for 59.94 and 119.88 fps content from these
cameras. 59.94 timecodes are being chopped in half (01:00:00;00 might
become 00:30:00;00), and 119.88 fps timecodes are being chopped to one
quarter (01:00:00;00 might become 00:15:00;00).
Here's the S1H file. Thanks for the help!
Panasonic XML metadata: <StartTimecode>16:25:24:25</StartTimecode>
ffmpeg2018: timecode : 16:25:24;25
ffmpeg2022: timecode : 04:06:21;27
https://drive.google.com/file/d/1cg5iM3HWQZdGP5KR_gxxxWoqSU2mpKDy/view?usp=sharing
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9710#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list