aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar gpoirier <gpoirier@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-04-02 18:25:05 +0000
committerGravatar gpoirier <gpoirier@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-04-02 18:25:05 +0000
commita1a54710e707fab85d81134ffe6ef5c68bd12b76 (patch)
tree11cd1b3d7bbca0b9cb68aa677f17bcd89de586da
parentc35708cbf1f4cfa2ed4b56c7fb2f6d2fd1e6a00b (diff)
Add a note explaining that it's okay to use a different target bitrate on the various passes of a video encode
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@18023 b3059339-0415-0410-9bf9-f77b7e298cf2
-rw-r--r--DOCS/xml/en/mencoder.xml13
1 files changed, 13 insertions, 0 deletions
diff --git a/DOCS/xml/en/mencoder.xml b/DOCS/xml/en/mencoder.xml
index 1f6aacae25..cc7142e4ae 100644
--- a/DOCS/xml/en/mencoder.xml
+++ b/DOCS/xml/en/mencoder.xml
@@ -373,6 +373,19 @@ mencoder <replaceable>input.avi</replaceable> -of mpeg -mpegopts format=mpeg1:ts
</para>
</informalexample>
+<note><title>Hint:</title>
+<para>
+ If for some reason the video quality of the second pass did not
+ satisfy you, you may re-run your video encode with a different target
+ bitrate, provided that you saved the statistics file of the previous
+ pass.
+ This is possible because the statistics file primary goal is to record
+ the complexity of each frames, which doesn't depend on bitrate.
+ You should note though that you'll get best results if all passes are
+ run with a target bitrate that does not differ too much.
+</para>
+</note>
+
</sect1>
<sect1 id="menc-feat-rescale">