Opened 6 years ago

Last modified 6 years ago

#7016 new defect

Timecode incorrect when transcoding 59.94 to 29.97

Reported by: Michael Oliver Owned by:
Priority: normal Component: undetermined
Version: git-master Keywords: timecode
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Summary of the bug:
How to reproduce:

% ffmpeg.exe -y -r 59.94 -i SRC.mov -acodec copy -c:v libx265 -crf 28 -vf "transpose=1" -r 29.97 DST.mov
ffmpeg version: N-89955-g118e1b0b33

Timecode when transcoding from 59.94 --> 29.97 timecode is not being calculated correctly resulting in incorrect start and end timecodes. Tested on multiple input and output codecs including prores, h264, h265

Start timecode on 59.97 is 09:31:58:30.
Start timecode on 29.97 is 09:31:59:00.
It should be 09:31:58:15

Attachments (4)

plate.json​ (6.4 KB ) - added by Michael Oliver 6 years ago.
original 59.94 prores ffprobe json output
h265.json​ (4.8 KB ) - added by Michael Oliver 6 years ago.
transcoded h265 29.97 ffprobe output
h265-timecodeissue.log​ (5.2 KB ) - added by Michael Oliver 6 years ago.
encoding log file
plate.mov​ (668.7 KB ) - added by Michael Oliver 6 years ago.
Source Plate showing timecode 09:31:58:30

Download all attachments as: .zip

Change History (10)

by Michael Oliver, 6 years ago

Attachment: plate.json​ added

original 59.94 prores ffprobe json output

by Michael Oliver, 6 years ago

Attachment: h265.json​ added

transcoded h265 29.97 ffprobe output

by Michael Oliver, 6 years ago

Attachment: h265-timecodeissue.log​ added

encoding log file

comment:1 by Carl Eugen Hoyos, 6 years ago

Version: 3.4 → git-master

Please provide a small input file that allows to reproduce the issue.

comment:3 by Carl Eugen Hoyos, 6 years ago

Please attach a file of approximately 1 MB here to the ticket.

by Michael Oliver, 6 years ago

Attachment: plate.mov​ added

Source Plate showing timecode 09:31:58:30

comment:4 by Michael Oliver, 6 years ago

Last edited 6 years ago by Michael Oliver (previous) (diff)

in reply to:  3 comment:5 by Michael Oliver, 6 years ago

Uploaded and attached. Any ideas?
Replying to cehoyos:

Please attach a file of approximately 1 MB here to the ticket.

comment:6 by Michael Oliver, 6 years ago

FYI I just stumbled across this post from 2 years ago regarding the same thing. Link below. Any chance we can get this elevated in priority?

​http://www.ffmpeg-archive.org/60-FPS-timecode-problem-td4676077.html

Note: See TracTickets for help on using tickets.