[FFmpeg-devel] [PATCH] ffmpeg: drop format specific stream copy heuristics

James Almer jamrial at gmail.com
Tue Sep 6 17:32:24 EEST 2016

On 9/6/2016 9:57 AM, Clément Bœsch wrote:
>> We don't have time_base in codecpar, so why do we need ticks per frame in it?
>> > 
>> > Which time_base does it modify the interpretation of? The field should
>> > be bundled with that, then.
> When do we have a mismatch of st->time_base and that "codec time base"?

st->time_base can be anything. Matroska for example is always 1/1000,
and mpegps 1/90000.
"Codec time_base" seems to be codec frame_rate * ticks_per_frame, so
usually the same as frame_rate, except for codecs like h264 and mpeg2
where it's twice that.

More information about the ffmpeg-devel mailing list