[FFmpeg-devel] [PATCH]Slightly improve pullup documentation

Carl Eugen Hoyos cehoyos at ag.or.at
Fri Sep 20 02:52:57 CEST 2013

On Friday 20 September 2013 01:39:54 am compn wrote:
> On Fri, 20 Sep 2013 01:26:21 +0200, Carl Eugen Hoyos wrote:
> >Hi!
> >
> >Automatically dropping superfluous frames within the pullup filter would
> >require to copy the whole fps logic into the filter afaict so I propose
> >attached documentation patch instead.
> >
> >Please comment, Carl Eugen
> maybe add one example line with both filters chained ?


Please comment, Carl Eugen
-------------- next part --------------
diff --git a/doc/filters.texi b/doc/filters.texi
index eb3a493..ce40814 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -6193,6 +6193,10 @@ its decisions. This filter is stateless in the sense that it does not lock
 onto a pattern to follow, but it instead looks forward to the following
 fields in order to identify matches and rebuild progressive frames.
+To produce content with an even framerate, insert the fps filter after
+pullup, use @code{fps=24000/1001} if the input frame rate is 29.97fps,
+ at code{fps=24} for 30fps and the (rare) telecined 25fps input.
 The filter accepts the following options:
 @table @option
@@ -6235,6 +6239,11 @@ The main purpose of setting @option{mp} to a chroma plane is to reduce CPU
 load and make pullup usable in realtime on slow machines.
 @end table
+For example to inverse telecine NTSC input:
+ at example
+-vf pullup,fps=24000/1001 
+ at end example
 @section removelogo
 Suppress a TV station logo, using an image file to determine which

More information about the ffmpeg-devel mailing list