On Tue, Oct 21, 2014 at 09:32:39AM +0200, Carl Eugen Hoyos wrote:
> Hi!
> 
> It appears to me that we all know that fieldmatch needs cfr input, 
> but it isn't mentioned in the documentation.
> Related to ticket #3968.
> 
> Please comment, Carl Eugen

> diff --git a/doc/filters.texi b/doc/filters.texi
> index c70ddf3..bc77623 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi
> @@ -4447,6 +4447,9 @@ and VIVTC/VFM (VapourSynth project). The later is a 
> light clone of TFM from
>  which @code{fieldmatch} is based on. While the semantic and usage are very
>  close, some behaviour and options names can differ.
>  
> +The filter only works for strictly constant frame rate input. If your input
> +has variable frame rate, try the @ref{pullup} filter.
> +

Well... isn't telecined content supposed to be CFR anyway? I would say
it's supposed to be undefined behaviour in any ivtc filter but well. No
opinion really.

[...]

-- 
Clément B.

Attachment: pgpbUXeagfMr5.pgp
Description: PGP signature

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to