From 3905c8c64fc569730798eb4bc3c2f5dd4df9d178 Mon Sep 17 00:00:00 2001 From: wanderer Date: Mon, 15 Aug 2005 22:46:27 +0000 Subject: grammar/phrasing fixes on the recent NTSC and telecine commit git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@16230 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/encoding-guide.xml | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/DOCS/xml/en/encoding-guide.xml b/DOCS/xml/en/encoding-guide.xml index 448ed867fb..ac85040b2b 100644 --- a/DOCS/xml/en/encoding-guide.xml +++ b/DOCS/xml/en/encoding-guide.xml @@ -63,14 +63,15 @@ 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. + Experience shows that NTSC material is a lot more difficult to encode, + because 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, duplicated or lost frames in your encode. + Failure to take this into account will result in various flaws in your + encode, including ugly combing (interlacing) artifacts and duplicated + or even lost frames. Besides being ugly, the artifacts also harm coding efficiency: - You will get worse quality per bitrate. + You will get worse quality per unit bitrate. @@ -1690,9 +1691,9 @@ Note the and options. - 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. + Another way to tell if your source is telecined or not is to play + the source with the and + command line options 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. -- cgit v1.2.3