[FFmpeg-devel] [PATCH] lavf: inspect more frames for fps when container time base is coarse

[Michael Niedermayer]

On Mon, Feb 28, 2011 at 02:20:56AM +0200, Anssi Hannula wrote:
> As per issue2629, most 23.976fps matroska H.264 files are incorrectly
> detected as 24fps, as the matroska timestamps usually have only
> millisecond precision.
> 
> Fix that by doubling the amount of timestamps inspected for frame rate
> for streams that have coarse time base. This also fixes 29.970 detection
> in matroska.
> 
> ---
> 
> A preferable solution to issue2629 would be to somehow use header values
> either from the H.264 stream or from the Matroska stream.
> 
> However, AFAICS the framerate inspecting has to be fixed as well anyway
> (with e.g. this patch), for cases when we have no reliable header values.
> 
> Comments welcome.

applied locally, will push in a moment
sorry, ive somehow missed reimars ping it seems

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20110403/2da51d8e/attachment.asc>