WinGui:

[handbrake-jp/handbrake-jp-git.git] / win / C# / Controls / x264Panel.resx

diff --git a/win/C#/Controls/x264Panel.resx b/win/C#/Controls/x264Panel.resx
index 8dca4f1..064df4a 100644 (file)
--- a/win/C#/Controls/x264Panel.resx
+++ b/win/C#/Controls/x264Panel.resx
@@ -205,8 +205,9 @@ If you want to create a high profile H.264 video (which is less compatible with
     <value>This setting is finer-grained than the motion estimation settings above. Instead of dealing with whole pixels, it deals with 4 fractional pixels, or quarter pixels (qpel). \r
 Higher levels increase quality by further refining the motion prediction for these quarter pixels, but take longer to encode.\r
 \r
-The default, 6, turns on a feature called rate distortion optimization, including psychovisual enhancements. \r
-7 enables that rate distortion for B-frames. 8 refines those decisions for I and P frames, and 9 adds on refinement for B-frames as well.</value>\r
+Level 6, turns on a feature called rate distortion optimization, including psychovisual enhancements. \r
+7, the default, enables that rate distortion for B-frames.\r
+8 refines those decisions for I and P frames, and 9 adds on refinement for B-frames as well.</value>\r
   </data>\r
   <data name="drop_MotionEstimationRange.ToolTip" xml:space="preserve">\r
     <value>This range is the radius, in pixels, x264 should use for motion estimation searches. \r
@@ -235,7 +236,9 @@ Logically, to reference an earlier B-frame, you must tell x264 to use at least 2
   </data>\r
   <data name="check_weightedBFrames.ToolTip" xml:space="preserve">\r
     <value>Sometimes x264 will base a B-frame's motion compensation on frames both before and after. \r
-With weighted B-frames, the amount of influence each frame has is related to its distance from the frame being encoded, instead of both having equal influence.</value>\r
+With weighted B-frames, the amount of influence each frame has is related to its distance from the frame being encoded, \r
+instead of both having equal influence. \r
+The AppleTV can have issues with this.</value>\r
   </data>\r
   <data name="drop_directPrediction.ToolTip" xml:space="preserve">\r
     <value>Direct prediction tells x264 what method to use when guessing motion for certain parts of a B-frame. \r