Andrea and Andrew corrections and changed placements

[goodguy/cin-manual-latex.git] / parts / Rendering.tex

diff --git a/parts/Rendering.tex b/parts/Rendering.tex
index 1f1646fc31545ed1273b57e8345e29e39f11c415..8ce318afed6ffa96ae8022c43a16b0d03e8b6dc9 100644 (file)
--- a/parts/Rendering.tex
+++ b/parts/Rendering.tex
@@ -17,7 +17,7 @@ But you also have the choice to render \textit{one frame}.
 \section{Single File Rendering}%
 \label{sec:single_file_rendering}
 
-Use the File pulldown and select Render to start the render dialog
+Use the \textit{File} pulldown and select Render to start the render dialog
 (figure~\ref{fig:render}).  Then choose the desired parameters.
 
 \begin{figure}[htpb] \centering
@@ -469,16 +469,14 @@ communication, shared filesystem, permissions and usernames synched.
   \item set the Total number of jobs to create;
   \item click OK on the bottom of the Preferences window.
   \end{itemize}
-\item On the client computers ($192.168.1.12$), start 5 background
-  \CGG{} tasks via:
+\item Now we must join the nodes created to instances of \CGG{}. On the client computers ($192.168.1.12$), on the terminal, start 5 background  \CGG{} tasks via:
 \begin{lstlisting}[style=sh]
 cd {path_to_cinelerra}
 cin -d 401 cin -d 402
 ...
 cin -d 405
 \end{lstlisting}
-\item On the master node (localhost), start the 2 background \CGG{}
-  tasks via:
+\item Similarly, on the terminal, we must join the local nodes created to instances of \CGG{}. On the master node (localhost), start the 2 background \CGG{}  tasks via:
 \begin{lstlisting}[style=sh]
 cd {path_to_cinelerra}
 cin -d 406
@@ -698,7 +696,7 @@ umount <path>
     node, start \CGG{} by clicking on the icon or by typing the
     following command on the terminal screen:
     \texttt{/{cinelerra\_path}/cin}.
-  \item Use the file pulldown \texttt{Settings $\rightarrow$
+  \item Use the \textit{File} pulldown \texttt{Settings $\rightarrow$
       Preferences}, the Performance tab, to set up your Render Farm
     options in the Render Farm pane.
   \item Check the \textit{Use render farm} option.  By default, once
@@ -850,10 +848,10 @@ count, setting up a render farm can really take advantage of using
 all of the cpus. This is much faster than the default automatic
 threading capability. Since you don’t need to communicate with other
 computers, you will not have to be concerned about TCP communication
-or shared disks/files. When you are going to be doing other work
+or shared disks/files; only localhost nodes. On the terminal, we will open many instances of \CGG{} by connecting them to the jobs created. The number of such jobs can be the total number of CPU threads or not. When you are going to be doing other work
 simultaneously while rendering a large job, you will want to leave
-some of the cpus available for that.  Be sure to set “Project SMP
-cpus” in the Settings→Preferences, Performance tab to your CPU
+some of the cpus available for that.  Be sure to set \textit{Project SMP
+cpus} in the \texttt{Settings $\rightarrow$ Preferences, Performance} tab to your CPU
 count.
 
 \subsection{Troubleshooting Tips and Warnings}%