From d484afb3733d33d42392b915a195769aee2a0ba5 Mon Sep 17 00:00:00 2001 From: sr55 Date: Sat, 10 Jul 2010 13:33:11 +0000 Subject: WinGui: - Fix x264 tooltip for Pyramid BFrames git-svn-id: svn://svn.handbrake.fr/HandBrake/trunk@3435 b64f7644-9d1e-0410-96f1-a4d463321fa5 --- win/C#/Controls/x264Panel.resx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'win/C#/Controls/x264Panel.resx') diff --git a/win/C#/Controls/x264Panel.resx b/win/C#/Controls/x264Panel.resx index 488377436..1339f1faf 100644 --- a/win/C#/Controls/x264Panel.resx +++ b/win/C#/Controls/x264Panel.resx @@ -233,9 +233,9 @@ Note that some devices and players, even those that support Main Profile, may have problems with Weighted P-frame prediction: the Apple TV is completely incompatible with it, for example. - This is the distance x264 searches from its best guess at the motion of a block in order to try to find its actual motion. -Doesn't apply to Diamond or Hexagon search options. -The default is fine for most content, but extremely high motion video, especially at HD resolutions, -may benefit from higher ranges, albeit at a high speed cost. + B-pyramid improves compression by creating a pyramidal structure (hence the name) of B-frames, allowing B-frames to +reference each other to improve compression. + +Requires Max B-frames greater than 1; optimal adaptive B-frames is strongly recommended for full compression benefit. \ No newline at end of file -- cgit v1.2.3