# HG changeset patch # User corey # Date 1208719587 0 # Node ID 83fdf3030da728f8c18ed225887ee96f90a7456d # Parent 586d7ee3c10604421920d2b2273035c0100e27cb add better information about inverse-telecining with vf_filmdint diff -r 586d7ee3c106 -r 83fdf3030da7 DOCS/xml/en/encoding-guide.xml --- a/DOCS/xml/en/encoding-guide.xml Sun Apr 20 16:06:41 2008 +0000 +++ b/DOCS/xml/en/encoding-guide.xml Sun Apr 20 19:26:27 2008 +0000 @@ -2245,6 +2245,23 @@ --> + is similar to + : both filters attempt to match a pair of + fields to form a complete frame. will + deinterlace individual fields that it cannot match, however, whereas + will simply drop them. Also, the two filters + have separate detection code, and filmdint may tend to match fields a + bit less often. Which filter works better may depend on the input + video and personal taste; feel free to experiment with fine-tuning + the filters' options if you encounter problems with either one (see + the man page for details). For most well-mastered input video, + however, both filters work quite well, so either one is a safe choice + to start with. + +mencoder dvd://1 -oac copy -vf filmdint -ovc lavc -ofps 24000/1001 + + An older method is to, rather than inverse-telecine the telecined parts, telecine the non-telecined parts and then inverse-telecine the whole @@ -2258,18 +2275,6 @@ - - I have not used myself, but here is what - D Richard Felker III has to say: - -
It is OK, but IMO it tries to deinterlace rather - than doing inverse telecine too often (much like settop DVD - players & progressive TVs) which gives ugly flickering and - other artifacts. If you are going to use it, you at least need to - spend some time tuning the options and watching the output first - to make sure it is not messing up. -
-