Hi!
As Clément always pointed out correctly, the issues users see with
fieldmatch and mixed telecined and progressive content have nothing
to do with decimate (and of course not fieldmatch) but with the
specifics of our fps filter (see my ignored mail for details).
Attached patch should help, please comment.
Carl Eugen
diff --git a/doc/filters.texi b/doc/filters.texi
index 3e7d2a2..6ba4bed 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -5476,8 +5476,9 @@ which @code{fieldmatch} is based on. While the semantic
and usage are very
close, some behaviour and options names can differ.
The @ref{decimate} filter currently only works for constant frame rate input.
-Do not use @code{fieldmatch} and @ref{decimate} if your input has mixed
-telecined and progressive content with changing framerate.
+If your input has mixed telecined and progressive content which implies
+changing framerates use the following filterchain to produce the
+necessary cfr stream: @code{dejudder,fps=30000/1001,fieldmatch,decimate}.
The filter accepts the following options:
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
