On 18 Mar 2018, at 07:52, Mark Burton <mwjbur...@gmail.com> wrote: > On 14 Mar 2018, at 23:20, Michael Niedermayer <mich...@niedermayer.cc > <mailto:mich...@niedermayer.cc>> wrote: >> for other cases 600 is less accurate >> for example input that uses timestamps in ms precission >> like flv >> but also 30000/1001 will be less precisse > > In the case of a Quicktime encoder, a 30000/1001 frame rate encode would > still have a Movie Header timescale of 600, but a video track timescale of > 2997. Since ffmpeg allows us to specify the video_track_timescale, this > output could still be achieved. > > As for flv and formats that use ms precision, I’ll freely admit thats not > something I work with so am not in a position to comment. However, would > these formats not also have the benefit of the current flag to set > video_track_timescale?
Or go with 1200, which is more accurate for ms precision formats and also works for all major frame rates. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
