On Sat, Mar 10, 2018 at 02:38:17PM +0000, Mark Burton wrote: > On 9 Mar 2018, at 01:26, Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > > This breaks fate, our regression testing suite (my mistake). > > To download the test-suite: > > $ make SAMPLES=fate-suite fate-rsync > > $ make SAMPLES=fate-suite GEN=1 fate > > This changes the values for fate, then commit again with: > > $ git commit tests libavformat > > > Thanks Carl, I hope the below is now correct. > > From 0c73563d06c05245ecf8bcaf64bc1c2809f375e4 Mon Sep 17 00:00:00 2001 > From: mwjburton <mwjbur...@gmail.com> > Date: Sat, 10 Mar 2018 14:33:02 +0000 > Subject: [PATCH] libavformat/movenc : Change MOV_TIMESCALE from 1000 to 600 > > Changing the MOV_TIMESCALE value from 1000 to 600 results in > files that seek accurately in professional Quicktime software. This is > due to the fact 600 is cleanly divisible by more frame rates than 1000, for > example 24fps and 30fps. The Quicktime specification default is set to 600 > for this reason. When set to 1000 seeking can be inaccurate for these fame > rates.
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 is there something that iam missing or can this simply be computed from the input timebases instead of being a fixed value ? so its accurate for the inpiut when that is possible and only some fixed value when that is not possible [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
