# HG changeset patch
# User lorenm
# Date 1118624793 0
# Node ID d7c271f828d9cd5464be45f4a9bb66dc50eb78e0
# Parent  1a542b10ea87a4e9bd7126ead326f4cecea5ad37
tweak x264 option descriptions

diff -r 1a542b10ea87 -r d7c271f828d9 DOCS/man/en/mplayer.1
--- a/DOCS/man/en/mplayer.1	Sun Jun 12 21:45:11 2005 +0000
+++ b/DOCS/man/en/mplayer.1	Mon Jun 13 01:06:33 2005 +0000
@@ -8167,13 +8167,13 @@
 .IPs 3
 uneven multi-hexagon search
 .IPs 4
-exhaustive search, controlled by me_range (very slow)
+exhaustive search (very slow)
 .RE
 .PD 1
 .
 .TP
 .B me_range=<4\-64>
-radius of exhaustive motion search (default: 16)
+radius of exhaustive or multi-hexagon motion search (default: 16)
 .
 .TP
 .B subq=<1\-5>
diff -r 1a542b10ea87 -r d7c271f828d9 DOCS/xml/en/mencoder.xml
--- a/DOCS/xml/en/mencoder.xml	Sun Jun 12 21:45:11 2005 +0000
+++ b/DOCS/xml/en/mencoder.xml	Mon Jun 13 01:06:33 2005 +0000
@@ -2302,24 +2302,20 @@
   types that are possible in B-frames.
   Usually, even a naive B-frame choice algorithm can have a
   significant PSNR benefit.
-  It is also interesting to note that if you turn off the adaptive
-  B-frame decision (<option>nob_adapt</option>), encoding with
-  <option>bframes</option> usually speeds up encoding speed somewhat.
+  It is interesting to note that using B-frames usually speeds up
+  the second pass somewhat, and may also speed up a single pass
+  encode if adaptive B-frame decision is turned off.
 </para>
 <para>
   With adaptive B-frame decision turned off
   (<option>x264encopts</option>'s <option>nob_adapt</option>),
-  the optimal value for this setting will usually range from
-  <option>bframes=1</option> to <option>bframes=3</option>.
+  the optimal value for this setting is usually no more than
+  <option>bframes=1</option>, or else high-motion scenes can suffer.
   With adaptive B-frame decision on (the default behavior), it is
-  probably safe to use higher values; the encoder will try to
-  reduce the use of B-frames in scenes where they would hurt
-  compression.
-</para>
-<para>
-  If you are going to use <option>bframes</option> at all, consider
-  setting the maximum number of B-frames to 2 or higher in order to
-  take advantage of weighted prediction.
+  safe to use higher values; the encoder will reduce the use of
+  B-frames in scenes where they would hurt compression.
+  The encoder rarely chooses to use more than 3 or 4 B-frames;
+  setting this option any higher will have little effect.
 </para></listitem>
 
 <listitem><para>
@@ -2359,7 +2355,7 @@
   of expensive I-frames; using weighted prediction in B-frames
   makes it possible to turn at least some of these into much more
   reasonably-sized B-frames.
-  Encoding time cost seems to be minimal, if there is any.
+  Encoding time cost is minimal, as no extra decisions need to be made.
   Also, contrary to what some people seem to guess, the decoder
   CPU requirements are not much affected by weighted prediction,
   all else being equal.