# HG changeset patch
# User wanderer
# Date 1124145987 0
# Node ID 45b339e1b93b06bbbe1c0d51899311790b347171
# Parent 88ed8890152cbb366484079f3126f4019974f409
grammar/phrasing fixes on the recent NTSC and telecine commit
diff -r 88ed8890152c -r 45b339e1b93b DOCS/xml/en/encoding-guide.xml
--- a/DOCS/xml/en/encoding-guide.xml Mon Aug 15 16:30:31 2005 +0000
+++ b/DOCS/xml/en/encoding-guide.xml Mon Aug 15 22:46:27 2005 +0000
@@ -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 @@
- 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.