To configure the render according to your needs and to obtain the desired output, you will need to check on what your settings are for these three items:
\begin{enumerate}
- \item \textbf{Timeline:} is the main starting point because, in addition to determining the range of frames that will be rendered, it is on the timeline that plugins and other editing/compositing features are applied, which will then be included in the rendered file. While the rendering is in progress some frames from the timeline are displayed in the Compositor window, but it has no bearing on the
-actual rendering process.
+ \item \textbf{Timeline:} is the main starting point because, in addition to determining the range of frames that will be rendered, it is on the timeline that plugins and other editing features are applied, which will then be included in the rendered file.
\item \textbf{Set Format:} is used to configure the fps, aspect ratio and frame size of the project (= output). This can be found in the pulldown: \texttt{Settings $\rightarrow$ Format... (Shift + F)}.
See: \nameref{cha:project_and_media_attributes}.
\item \textbf{Render dialog:} this is under: \texttt{File $\rightarrow$ Render... (Shift + R)}. It contains all the rendering options that are documented in this chapter.
\begin{itemize}
\item check the \textit{Use render farm} box;
\item in the \textit{Hostname} box, keyin your hostname or ip
- address such as 192.168.1.12 or \textit{localhost};
+ address such as 192.168.1.12 or \textit{localhost} when using a single computer with a multicore CPU;
\item enter in a port number such as 401--405 (only a root user
can use privileged ports) or $10650...$ for non-root and click on \textit{Add Nodes}. To find a range of free ports to use you can look at the file \texttt{/etc/services};
\item you will see something like the following in the Nodes
\item For external network nodes, 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 10650 cin -d 10651
+cin -d 10650
+cin -d 10651
...
cin -d 10654
\end{lstlisting}
{path_to_cinelerra}/cin -h # displays some of the options.
\end{lstlisting}
+\subsection{Multi-core CPU Setup (Localhost)}%
+\label{sub:multi_core_render_farm_setup}
+\index{render farm!multi core CPU}
+
+If you are lucky enough to have a computer with a large cpu core
+count, setting up a render farm can really take advantage of using
+all of the cores at 100\%. 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; only localhost nodes. On the terminal you will need to 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 (-1) 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 \textit{Project SMP cpus} in the \texttt{Settings $\rightarrow$ Preferences, Performance} tab to your CPU
+count. Follow the steps outlined in ~\ref{sub:basic_steps_start_render_farm}
+but skip the step "For external network nodes".
+
\subsection{Detailed Setup Description}%
\label{sub:detailed_setup_description}
\index{render farm!setup}
the location of your project on the master computer can be done with
NFS as described next. Alternatively, you can look up on the
internet how to use Samba to share a directory.
-\item[Create a shared filesystem and mount using NFS] All nodes in
+\item[Create a shared filesystem and mount using NFS] (only for Network) All nodes in
the render farm should use the same filesystem with the same paths
to the project files on all of the master and client nodes. This is
easiest to do by setting up an NFS shared disk system.
node or use RenderMux shell script.
\end{enumerate}
-\subsection{Multi-core Computers Render Farm Setup}%
-\label{sub:multi_core_render_farm_setup}
-\index{render farm!multi core CPU}
-
-If you are lucky enough to have a computer with a large cpu core
-count, setting up a render farm can really take advantage of using
-all of the cores at 100\%. 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; 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 (-1) 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 \textit{Project SMP
-cpus} in the \texttt{Settings $\rightarrow$ Preferences, Performance} tab to your CPU
-count.
\subsection{Troubleshooting Tips and Warnings}%
\label{sub:troubleshhoting_tips_warnings}
projects / goodguy / cin-manual-latex.git / blobdiff