X-Git-Url: https://git.cinelerra-gg.org/git/?a=blobdiff_plain;ds=sidebyside;f=parts%2FRendering.tex;h=8ce318afed6ffa96ae8022c43a16b0d03e8b6dc9;hb=ac79c08dfb1261861b2154b797ecb9e4530deaa3;hp=1be6e02aa84a7cda10306946afa1d9ecc19b6e46;hpb=880f5be6425028cf9a0c07143f62cce0a82ea6bd;p=goodguy%2Fcin-manual-latex.git diff --git a/parts/Rendering.tex b/parts/Rendering.tex index 1be6e02..8ce318a 100644 --- 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 @@ -149,7 +149,7 @@ rendering an output file, are called a batch. This allows a large amount of media to be processed without user intervention. \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{batch01.png} + \includegraphics[width=1.0\linewidth]{batch01.png} \caption{Example of the Batch Render menu} \label{fig:batch01} \end{figure} @@ -346,7 +346,7 @@ to illustrate how to take advantage of their capabilities. \end{description} \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{batch02.png} + \includegraphics[width=1.0\linewidth]{batch02.png} \caption{Batch render with the 4 ghosted buttons on the right side + the Warning message below} \label{fig:batch02} @@ -372,7 +372,7 @@ the time ruler showing what has been background rendered (figure~\ref{fig:back-ren02}). \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{back-ren02.png} + \includegraphics[width=1.0\linewidth]{back-ren02.png} \caption{Settings Background Rendering} \label{fig:back-ren02} \end{figure} @@ -383,7 +383,7 @@ right before the effect to preview it in real time and full frame rates (figure~\ref{fig:back-ren}). \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{back-ren.png} + \includegraphics[width=1.0\linewidth]{back-ren.png} \caption{Timeline with the top red bar} \label{fig:back-ren} \end{figure} @@ -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 @@ -507,8 +505,8 @@ Below we describe the Performance tab for configuring a render farm (figure~\ref{fig:farm}). \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{farm.png} - \caption{Settings $\rightarrow$ Preferences, Performance tab, menu + \includegraphics[width=1.0\linewidth]{farm.png} + \caption{Settings: Preferences: Performance tab, menu to set up your Render Farm} \label{fig:farm} \end{figure} @@ -698,7 +696,7 @@ umount 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}% @@ -933,7 +931,7 @@ for your setup. may want to share these files with the clients on a shared filesystem. More information on index files configuration is outlined in~\ref{sub:index_file_section}. -\item Or, one of the convenient features of Cinelerra is the +\item Or, one of the convenient features of \CGG{} is the redirection of the path via \texttt{CIN\_CONFIG} as in: \begin{lstlisting}[style=sh] CIN_CONFIG="//" cin @@ -1024,7 +1022,7 @@ always complete, and it may include options that are not legal with all parameter configurations. \begin{figure}[htpb] \centering - \includegraphics[width=0.6\linewidth]{yuv420.png} + \includegraphics[width=1.0\linewidth]{yuv420.png} \caption{Render \& Video Preset menus displaying Pixel choices} \label{fig:yuv420} \end{figure} @@ -1074,7 +1072,7 @@ can be set with the \textit{cin\_sample\_fmt} parameter used.\\ Example: \textit{cin\_sample\_fmt=s16} \begin{figure}[htpb] \centering - \includegraphics[width=0.55\linewidth]{audio.png} + \includegraphics[width=0.7\linewidth]{audio.png} \caption{Render menu showing where Samples is} \label{fig:audio} \end{figure}