30.03.2021, 16:38
Problem seems to be the '-vsync 0' option:
When removing the option (which then uses '-vsync -1') everything seems fine.
-> Seems like the way how ffmpeg reacts to broken time codes in the input has changed.
Cu Selur
Quote:-vsync parametersource: https://www.ffmpeg.org/ffmpeg-all.html
Video sync method. For compatibility reasons old values can be specified as numbers. Newly added values will have to be specified as strings always.
0, passthrough
Each frame is passed with its timestamp from the demuxer to the muxer.
1, cfr
Frames will be duplicated and dropped to achieve exactly the requested constant frame rate.
2, vfr
Frames are passed through with their timestamp or dropped so as to prevent 2 frames from having the same timestamp.
drop
As passthrough but destroys all timestamps, making the muxer generate fresh timestamps based on frame-rate.
-1, auto
Chooses between 1 and 2 depending on muxer capabilities. This is the default method.
Note that the timestamps may be further modified by the muxer, after this. For example, in the case that the format option avoid_negative_ts is enabled.
With -map you can select from which stream the timestamps should be taken. You can leave either video or audio unchanged and sync the remaining stream(s) to the unchanged one.
When removing the option (which then uses '-vsync -1') everything seems fine.
-> Seems like the way how ffmpeg reacts to broken time codes in the input has changed.
Cu Selur
--- mainly offline 20.-26 of May ---