RepoMirrors
/
mpv
mirror of https://github.com/mpv-player/mpv
1
0
Fork 0
Code Issues Releases Wiki Activity

tweak x264 option descriptions 

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@15715 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
lorenm 2005-06-13 01:06:33 +00:00
parent fd84e21c3b
commit 1453b069b2
2 changed files with 12 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
DOCS/man/en/mplayer.1
View File

@ -8167,13 +8167,13 @@ hexagon search, radius 2 (default)
.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>

24
DOCS/xml/en/mencoder.xml
View File

@ -2302,24 +2302,20 @@ Note the <option>ilmv</option> and <option>ildct</option> options.
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 @@ Note the <option>ilmv</option> and <option>ildct</option> options.
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.