From 3cf0c959cd76f59709dbbb71e9576121cc1d2c58 Mon Sep 17 00:00:00 2001 From: Carl Eugen Hoyos Date: Thu, 3 Sep 2015 14:36:34 +0200 Subject: [PATCH] doc: Explain how to use the fps and the fieldmatch filter together. Fixes ticket #3968. --- doc/filters.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/filters.texi b/doc/filters.texi index 162958fab0..57e8b50e05 100644 --- a/doc/filters.texi +++ b/doc/filters.texi @@ -5483,8 +5483,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 (30fps) and progressive content with a lower +framerate like 24fps use the following filterchain to produce the necessary cfr +stream: @code{dejudder,fps=30000/1001,fieldmatch,decimate}. The filter accepts the following options: