Opened 3 years ago

Last modified 19 months ago

#9402 new defect

FFmpeg 4.4 - Incorrect processing of media with timecode

Reported by: Andrew Owned by:
Priority: normal Component: avformat
Version: unspecified Keywords: timecode
Cc: Andrew Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description (last modified by Andrew)

Summary of the bug: Media with timecode metadata is processed incorrectly. For the sample media, which is ~6.5 seconds with basic timecode metadata output incorrectly has a duration of 10x/fps of 1/10th the original. This results in a file that plays "normally" for the expected duration and then persists the final frame for about 6 minutes.

I have replicated this on multiple original files with timecode information. It does not happen on original files without timecode information. Unclear on the impact of other non A/V metadata/tracks.

How to reproduce: Use of "-map" is required to recreate this issue. Example command:
ffmpeg -i Earth_6s_59-94.mp4 -loglevel error -preset medium -map 0:v:0 -c:v libx264 -profile:v main -x264opts qpmin=0 -bf 0 -pix_fmt yuv420p -g 50 -vsync 0 -tune film -map 0:a:0? -c:a libfdk_aac -b:a 128k -ac 2 -movflags +faststart EarthOut.mp4

Example Source File: Unable to upload this to the form, so here's a link to a file that includes a timecode. Works great in 4.3.1, but 4.4 has bad output -

Attachments (1)

ffmpeg-20210902-150734.log (258.0 KB ) - added by Andrew 3 years ago.

Download all attachments as: .zip

Change History (4)

by Andrew, 3 years ago

Attachment: ffmpeg-20210902-150734.log added

comment:1 by Andrew, 3 years ago

Description: modified (diff)

comment:2 by Andrew, 3 years ago

Note: 4.4 is not available in the version selection drop-down

Last edited 3 years ago by Andrew (previous) (diff)

comment:3 by Carl Eugen Hoyos, 19 months ago

Priority: importantnormal

I think that vsync 0 is not supported for the mov muxer.
Is the issue reproducible with current FFmpeg git head, the only version supported on this bug tracker?

Note: See TracTickets for help on using tickets.