-Because index files speed up displaying the video you may want to share these files with the clients on a shared filesystem. There is a configuration option available in \texttt{Settings $\rightarrow$ Preferences}, the Interface tab, that sets up in your preferences the location of the index files which you can put on a shared disk.
-Screencast below shows part of the Preferences menu where you can change the index files setup (figure~\ref{fig:index}).
-\begin{figure}[htpb]
- \centering
- \includegraphics[width=0.8\linewidth]{images/index.png}
- \caption{Index file setup for your preferred configuration for Render Farm sharing or anything}
- \label{fig:index}
-\end{figure}
- Or, one of the convenient features of cin5 is the redirection of the path via \texttt{CIN\_CONFIG} as in:
-\begin{lstlisting}[language=bash,numbers=none]
-CIN_CONFIG=/<shared_file_pathname>/<filename_such_as_.bcast5> /<cinelerra_pathname>/cin
-\end{lstlisting}
-This means that you can make project related configurations that do not impact the default \texttt{\$HOME} config. You can either export your default \texttt{\$HOME} config or the \texttt{CIN\_CONFIG} config to use on the render farm.
+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 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 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 count.