X-Git-Url: https://git.cinelerra-gg.org/git/?p=goodguy%2Fcin-manual-latex.git;a=blobdiff_plain;f=parts%2FTips.tex;h=bec6c6647f8d381bd2bc3f9778a9a843b20e4c0a;hp=a0051095d2e61689315a6b1e0816e3f383e56e8a;hb=00b3f32aaead93dbd05238a92b5027839a2e77e0;hpb=1495136705fccb30d9d238fc35da0f22b5f610d0

diff --git a/parts/Tips.tex b/parts/Tips.tex
index a005109..bec6c66 100644
--- a/parts/Tips.tex
+++ b/parts/Tips.tex
@@ -307,7 +307,8 @@ profile=high
 According to an online wiki, hardware encoders usually create output of lower quality than some software encoders like x264, but are much faster and use less CPU. Keep this in mind as you might want to set a higher bitrate to get output of similar visual quality.
 
 Results of a particular test case performed on a Intel, 4-core computer, with Broadwell Graphics using an mp4 input video/audio file with dimensions of
-$1440x1080 / 29.97fps$ is shown next (note, filename is \texttt{tutorial.mp4}).  This may very well be a \textit{best case} scenario!  But clearly, at least on this computer with only 4 cores, the hardware acceleration seems to be quite advantageous.  A comparison of the 2 output files using \texttt{ydiff} shows no obvious defects.
+$1440x1080 / 29.97fps$ is shown next (note, filename is \texttt{tutorial.mp4}).  This may very well be a \textit{best case} scenario!  But clearly, at least on this computer with only 4 cores, the hardware acceleration seems to be quite advantageous.  A comparison of the 2 output files 
+using \texttt{ydiff} as described in the Appendix (\ref{sec:Ydiff to check results}) shows no obvious defects.
 
 \begin{center}
 	\begin{tabular}{l|cccc}