2011/5/9 Aℓex Converse <aconve...@google.com>: > The attached patch adds a command line option "-fpsprobesize" to > specify the number of frames used in fps estimation. > > Currently some 29.97 fps FLV files are detected as 59.92 fps. > > Feel free to play with this spreadsheet to understand the issue: > > https://spreadsheets.google.com/ccc?key=0Ah8DDuo3xisxdDZOQWRWc3ZjLV9zdzZnM0hvVkZ2enc&hl=en&authkey=CKCX3v4D > > The "Lag" parameter adjusts where the file starts. When score is > negative 59.92 fps is detected. Look how just playing with lag effects > detection when only a few frames are used. >
Ping? FWIW lag=1 seems to be our most common case as we ignore the first frame's duration. _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
