# HG changeset patch # User gpoirier # Date 1124058302 0 # Node ID f7373277b26907ad22cbf22ebefe1904704c5dea # Parent f18e92e72216062d7112b825c4f4ba983b84b10c NTSC sources are hard to encode. How to identify telecine content reliably. diff -r f18e92e72216 -r f7373277b269 DOCS/xml/en/encoding-guide.xml --- a/DOCS/xml/en/encoding-guide.xml Sun Aug 14 19:40:33 2005 +0000 +++ b/DOCS/xml/en/encoding-guide.xml Sun Aug 14 22:25:02 2005 +0000 @@ -63,10 +63,12 @@ presentation on a television, and often does not correspond to the original format of the movie. + Experience shows that NTSC contents are a lot more difficult to encode + given that there more elements to identify in the source. In order to produce a suitable encode, you need to know the original format. Failure to take this into account will result in ugly combing - (interlacing) artifacts in your encode. + (interlacing) artifacts, duplicated or lost frames in your encode. Besides being ugly, the artifacts also harm coding efficiency: You will get worse quality per bitrate. @@ -209,8 +211,8 @@ encoded MPEG-2. - The procedures for dealing with these cases will be covered later - in this guide. + The procedures for dealing with these cases will be covered + later in this guide. For now, we leave you with some guides to identifying which type of material you are dealing with: @@ -1686,6 +1688,20 @@ "hard-telecine". Since hard-telecine is already 60000/1001 fields per second, the DVD player plays the video without any manipulation. + + + Another way to tell if your source is telecined or not is to watch the + the source appending to your command line + to see how matches frames. + If the source is telecined, you should see on the console a 3:2 pattern + with 0+.1.+2 and 0++1 + alternating. + This technique has the advantage that you do not need to watch the + source to identify it, which could be useful if you wish to automate + the encoding procedure, or to carry out said procedure remotely via + a slow connection. + +