\index{appimage}
The main way to install \CGG{} is to use the AppImage. This is updated regularly and works for every distro, since it already contains the necessary dependencies.
-A big advantage of using the AppImage format is that it is only 1/3 the size of the normal install, and since each release is named differently, you can keep a number of versions in a directory, and when testing from a terminal you just have to type CinGG, then hit tab, and complete it to the desired date release. A small disadvantage of using the AppImage format is that some of the options to make minor text type changes are not available and any graphics board speedups most likely will not work.
+A big advantage of using the AppImage format is that it is only 1/3 the size of the normal install, and since each release is named differently, you can keep a number of versions in a directory, and when testing from a terminal you just have to type CinGG, then hit tab, and complete it to the desired date release. A small disadvantage of using the AppImage format is that some of the options to make minor text type changes are not available and any graphics board speedups most likely will not work. In many cases, rendering has been found to take a small percentage longer than if you do your own build or use a package RPM as documented at \nameref{sec:distro_with_cinelerra_included}. It is assumed that general processing will be slightly slower also.
For 64-bit systems you can choose between an image with up-to-date libraries or one that supports older libraries (named \textit{older-distro}), which you should use only if the first image gives you problems with unsupported libs.
LV2\protect\footnote{Optional Feature - OS dependent} is an open standard for audio plugins using a simple interface with extensions which add functionality to support audio software. These plugins were written by external developers and provide additional audio effects to \CGG{} audio without having to change \CGG{} every time. Because the LV2 plugins are separate from \CGG{} Infinity, if one fails or does not perform as expected, \CGG{} should stay running and you will have to contact the programmers responsible for that plugin for a fix.
-Typically, a user OS has specialized package groups installed. It is difficult to create one build of \CGG{} to accommodate all potential LV2 plugins. Specifically for the \textit{Calf-Studio LV2 plugins}, you should install the \textit{Calf Plugins} package. Note that because the Calf Plugins have a graphics UI interface which is dependent on specific hardware, they will not work with AppImage. The user’s computer must have \textit{gtk-2-runtime} installed, which seems to be automatically done already for most distros. For users doing their own builds, you can build \CGG{} without LV2 support by including \texttt{-{}-without-lv2} in the configure step. The default build is \texttt{-{}-with-lv2=yes} and requires that \textit{GTK-2-devel} must be installed or the build will fail and notify you. In addition for some newer distros, you will need to install
+Typically, a user OS has specialized package groups installed. It is difficult to create one build of \CGG{} to accommodate all potential LV2 plugins. Specifically for the \textit{Calf-Studio LV2 plugins}, you should install the \textit{Calf Plugins} package.
+The user’s computer must have \textit{gtk-2-runtime} installed, which seems to be automatically done already for most distros. For users doing their own builds, you can build \CGG{} without LV2 support by including \texttt{-{}-without-lv2} in the configure step. The default build is \texttt{-{}-with-lv2=yes} and requires that \textit{GTK-2-devel} must be installed or the build will fail and notify you. In addition for some newer distros, you will need to install
\textit{lv2-calf-plugins-gui}; for example Fedora version 32.
LV2 plugins have their own category in the \textit{Audio Plugins Visibility} as lv2. There is a simple text interface which is available via the usual \textit{Show controls} button when the plugin is attached to the audio track. This window has a Reset button to get back to the default settings. To change a value of one of the parameters, highlight that parameter and type in the new value in the topmost text box and then hit Apply to take effect -- the reason for requiring hitting apply is so that the audio is not moving all over the place while you are still typing a value. More easily, you can just move the \textit{pot dial} or the \textit{slider} bar which take effect automatically.
/tmp/cinelerra-5.1/bin/lv2ui http://calf.sourceforge.net/plugins/Flanger
\end{lstlisting}
+If using the AppImage version and the Calf/LV2 plugins are not working for you, try doing the
+following which has been shown to work on Ubuntu 16.
+
+\begin{enumerate}
+ \item Copy the "calf" and "lv2" folders from /usr/lib/ to /home/user/plugins\_lv2-calf\_for\_Cin/.
+ \item After starting up \CGG{}, change Settings-> Preferences...-> Interface tab, Default LV2\_PATH to
+ \$HOME/plugins\_lv2-calf\_for\_Cin/lv2 .
+ \item In the /home/user/plugins\_lv2-calf\_for\_Cin/lv2/ directory remove any of the plugins that do not seem to work.
+\end{enumerate}
\section[Video Effects --- Native]{Video Effects -- Native}%
\label{sec:video_effects_native}
job into that specified number of tasks. Each background job is
assigned a timeline segment to process. The render farm software
tries to process all of the rendering in parallel so that several
- computers can be used to render the results.
+ computers can be used to render the results. You should adjust
+ this for each different video if your work varies considerably in
+ time so that each task time is not too small.
To start, if you have computers of similar speed, a good number
for \textit{Total jobs to create} is the number of computers
\textit{reset rates} to start over for new framerates.
\item If jobs are split in a key section on the timeline, you may
wish to \textit{use labels} to prevent this.
+\item Adjust the \textit{Total jobs to create} for different videos that
+ are considerably different in size. You should not create so
+ many jobs that each one is very small.
\item For testing purposes, you may want to start a client in the
foreground using \texttt{-f} instead of \texttt{-d}.
\item If one of the client computers is unavailable, check to see if
projects / goodguy / cin-manual-latex.git / commitdiff