There are realtime effects -- these are the most useful and probably all you will ever need -- and rendered effects.
The rendered effects are discussed separately in the \nameref{sec:rendered_effects} section.
-Effect plugins modify the track when played, according to how they are set, with no permanent storage of the output except when the project is rendered. There are many Plugins in Cinelerra-GG Infinity which are actually quite easy to use just by experimenting with them. The plugins are shown and selected from the \textit{Resources window} (figure~\ref{fig:video-plugins}). They are described in more detail later.
+Effect plugins modify the track when played, according to how they are set, with no permanent storage of the output except when the project is rendered. There are many Plugins in \CGG{} Infinity which are actually quite easy to use just by experimenting with them. The plugins are shown and selected from the \textit{Resources window} (figure~\ref{fig:video-plugins}). They are described in more detail later.
\begin{figure}[htpb]
\centering
- \includegraphics[width=1.0\linewidth]{images/video-plugins.png}
+ \includegraphics[width=1.0\linewidth]{video-plugins.png}
\caption{Screencast of the native Video plugins in the default Cinfinity icon set.}
\label{fig:video-plugins}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/audio-plugins.png}
+ \includegraphics[width=0.6\linewidth]{audio-plugins.png}
\caption{Cinfinity2 audio plugins}
\label{fig:audio-plugins}
\end{figure}
\begin{figure}[htpb]
\centering
\begin{tikzpicture}[scale=1, transform shape]
- \node (img1) [yshift=0cm, xshift=0cm, rotate=0] {\includegraphics[width=0.5\linewidth]{images/plugin-icons.png}};
+ \node (img1) [yshift=0cm, xshift=0cm, rotate=0] {\includegraphics[width=0.5\linewidth]{plugin-icons.png}};
\node [yshift=-8mm, xshift=-1cm,anchor=east] at (img1.north west) (Preferences) {Preferences Window};
\node [yshift=-17mm, xshift=-1cm,anchor=east] at (img1.north west) (Tab) {Tab section};
\node [yshift=-41mm, xshift=-1cm,anchor=east] at (img1.north west) (Icon) {Plugin icon choices};
\begin{wrapfigure}[2]{r}{0.3\linewidth}
\vspace{-3ex}
\centering
- \includegraphics[width=0.7\linewidth]{images/button-options.png}
+ \includegraphics[width=0.7\linewidth]{button-options.png}
\end{wrapfigure}
The rightmost knob is used to Turn Off/Turn On the effect where the default is On. This is useful to easily see that the plugin is doing what you expect. The leftmost symbol that looks like a gear is for \textit{Preset Edit} and its usage is described in the section \nameref{sec:saved_plugin_preset}.
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/editing-effects.png}
+ \includegraphics[width=0.9\linewidth]{editing-effects.png}
\caption{Screencast of the native Video plugins in the default Cinfinity icon set.}
\label{fig:editing-effects}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.7\linewidth]{images/drag-effect.png}
+ \includegraphics[width=0.7\linewidth]{drag-effect.png}
\caption{Dragging the Color 3 way effect}
\label{fig:drag-effect}
\end{figure}
When a shared effect is played back, it is processed just like a normal effect except the configuration is copied from the original effect. Some effects detect when they are being shared. These effects determine what tracks are sharing them and either mix the two tracks together or use one track to stage some value.
-When an original track has a shared track as one of its effects, the shared track itself is used as a \textit{realtime} effect. This is more commonly known as \textit{bouncing tracks} but Cinelerra achieves the same operation by attaching shared tracks. The fade and any effects in the shared track are applied to the original track. Once the shared track has processed the data, the original track performs any effects which come below the shared track and then composites it on the output.
+When an original track has a shared track as one of its effects, the shared track itself is used as a \textit{realtime} effect. This is more commonly known as \textit{bouncing tracks} but \CGG{} achieves the same operation by attaching shared tracks. The fade and any effects in the shared track are applied to the original track. Once the shared track has processed the data, the original track performs any effects which come below the shared track and then composites it on the output.
In order to prevent the shared track from mixing the same data as the original track on the output, enable the output \texttt{mute} toggle in the patchbay next to each track for which you do not want to mix on the output. If you are making a video and you do want the shared track to composite the original track's data on the output a second time, the video from the shared track would always appear under the video from the original track, regardless of whether it was on top of the original track. This is because shared tracks are composited in order of their attachment. Since it is part of the original track it has to be composited before the original track is.
\section{Saved Plugin Presets}%
\label{sec:saved_plugin_preset}
-\textit{Presets} and \textit{Factory Presets} for Plugin settings are now combined with the Preset Keyframe Parameters allowing you to choose, apply, delete, and edit your own Presets which can then be easily saved in the file \texttt{\$HOME/.bcast5/Cinelerra\_\\presets}. In addition to your own saved presets, there are automatically available Factory presets for some plugins, for example the Lens video plugin. The Factory presets are preceded by an asterisk (*) and can not be modified permanently.
+\textit{Presets} and \textit{Factory Presets} for Plugin settings are now combined with the Preset Keyframe Parameters allowing you to choose, apply, delete, and edit your own Presets which can then be easily saved in the file \texttt{\$HOME/.bcast5/Cinelerra\_presets}. In addition to your own saved presets, there are automatically available Factory presets for some plugins, for example the Lens video plugin. The Factory presets are preceded by an asterisk (*) and can not be modified permanently.
\begin{wrapfigure}[4]{r}{0.3\linewidth}
\vspace{-2ex}
\centering
- \includegraphics[width=0.7\linewidth]{images/preset.png}
+ \includegraphics[width=0.7\linewidth]{preset.png}
\end{wrapfigure}
Note that using this is directly changing a keyframe object so you will only want to modify parameters you are familiar with. Most of the data is obvious and safe to change.
\begin{figure}[htpb]
\centering
\begin{tikzpicture}[scale=1, transform shape]
- \node (img1) [yshift=0cm, xshift=0cm, rotate=0] {\includegraphics[width=0.6\linewidth]{images/preset02.png}};
+ \node (img1) [yshift=0cm, xshift=0cm, rotate=0] {\includegraphics[width=0.6\linewidth]{preset02.png}};
\node [yshift=-30mm, xshift=-1cm,anchor=east] at (img1.north west) (Green) {A user preset Green};
\node [yshift=-101mm, xshift=-1cm,anchor=south east,text width=10em, inner ysep=-3mm] at (img1.north west) (Textbox) {Textbox to type in the title for the chosen preset or name for a new preset.};
\node [yshift=-110mm, xshift=-1cm,anchor=north east,text width=10em,inner ysep=-3mm] at (img1.north west) (Save) {Use the Delete, Save or Apply button for operation.};
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.7\linewidth]{images/info-effect.png}
+ \includegraphics[width=0.7\linewidth]{info-effect.png}
\caption{Effect Info for Color 3 Way}
\label{fig:info-effect}
\end{figure}
\subsection{Delete Plugins to save Resources Space or make them Unavailable}%
\label{sub:delete_plugin_resouces_unavaible}
-Maybe you just don't ever use certain plugins or would prefer to only find the ones that are useful to you. To save space in the Resources Window so you don't have to scroll to find the plugins you want as much, a feature to delete others is available. If you have a System install, you will have to be root for this function to be usable. The plugins will be permanently deleted, but only until you rebuild or download a new set of Cinelerra binaries. To delete a plugin, highlight the plugin you no longer want in the Resources window then press Ctrl-Shift-delete. A small window will come up allowing you to change your mind and red-X out or check-OK to remove plugin. This feature may come in handy if you have personnel working on media for you and you only want them to exercise certain functions. Or maybe you can't remember which is the good \textit{deinterlace} plugin out of the available five or so and want to delete the extras so as not to be confused. The ffmpeg, \textit{ladspa}, and \textit{lv2} plugins can not be deleted in this manner but, of course, you can always turn them off from view by clicking on \textit{Visibility} and unchecking them (figure~\ref{fig:remove-effect}).
+Maybe you just don't ever use certain plugins or would prefer to only find the ones that are useful to you. To save space in the Resources Window so you don't have to scroll to find the plugins you want as much, a feature to delete others is available. If you have a System install, you will have to be root for this function to be usable. The plugins will be permanently deleted, but only until you rebuild or download a new set of \CGG{} binaries. To delete a plugin, highlight the plugin you no longer want in the Resources window then press Ctrl-Shift-delete. A small window will come up allowing you to change your mind and red-X out or check-OK to remove plugin. This feature may come in handy if you have personnel working on media for you and you only want them to exercise certain functions. Or maybe you can't remember which is the good \textit{deinterlace} plugin out of the available five or so and want to delete the extras so as not to be confused. The ffmpeg, \textit{ladspa}, and \textit{lv2} plugins can not be deleted in this manner but, of course, you can always turn them off from view by clicking on \textit{Visibility} and unchecking them (figure~\ref{fig:remove-effect}).
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/remove-effect.png}
+ \includegraphics[width=0.6\linewidth]{remove-effect.png}
\caption{Remove Deinterlace-CV plugin}
\label{fig:remove-effect}
\end{figure}
\subsection{Updatable Icon Image Support}%
\label{sub:updatable_icon_image_support}
-When running Cinelerra-GG Infinity builtin icons are loaded before the program starts. Png files in the path: \\ \texttt{<target\_directory>picon/picon\_set\_name} \\
+When running \CGG{} Infinity builtin icons are loaded before the program starts. Png files in the path: \\ \texttt{<target\_directory>picon/picon\_set\_name} \\
are searched before the images loaded into memory. Override \texttt{icon.png} files must be put into the path: \\ \texttt{<target\_directory>/picon/picon\_set\_name} \\
There are currently 4 sets of icons and their directory names are \textit{cinfinity} (the default) and \textit{cinfinity2}, \textit{original} (the long-time original set), and \textit{smoother} (generally was in use by some of the themes). An example, to replace the cinfinity icon of Blue Banana with a red apple instead, create your .png file as desired, and replace the file in: \\
\texttt{<target\_directory>/bin/plugins/picon/cinfinity/bluebanana.png}.
\texttt{<cinlib\_path>/bin/plugins/picon/cinfinity} (or cinfinity2, original or smoother)
-The Cinelerra program looks for a plugin icon in two places:
+The \CGG{} program looks for a plugin icon in two places:
\begin{enumerate}
\item First, it tries to find a png file in \texttt{<cinlib>/plugins/picon/cinfinity}(2) or original, smoother directory.
\end{enumerate}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.05\linewidth]{images/audio-default.png}
+ \includegraphics[width=0.05\linewidth]{audio-default.png}
\end{figure}
Keep in mind these points for newly created plugin icons:
\item All ffmpeg icons must begin with \texttt{ff\_<plugin\_name>.png} (Resources window title will still be F\_\dots)
\item For ladspa, check in the \texttt{<cin\_config>} directory (\texttt{\$HOME/.bcast5} normally) and look for the text file \texttt{\$HOME/.bcast5/ladspa\_plugins\dots} for the names of the ladspa libraries which correspond to plugin names where the needed name is the basename of the \texttt{.so} file.
For example \texttt{pha\-sers\_1217.so} would need to have a \texttt{phasers\_1217.png} file. There may be multiple plugins in a single “so” file which means that you can only have 1 icon to represent all of the plugins in that file; again as in phasers.
- \item Once you have placed the .png file in the correct spot, you will have to restart Cinelerra to test it.
- \item To submit your .png file for inclusion into Cinelerra-GG Infinity for all to enjoy, it is best to upload it to any datafilehost and notify the community via email with any informative documentation.
+ \item Once you have placed the .png file in the correct spot, you will have to restart \CGG{} to test it.
+ \item To submit your .png file for inclusion into \CGG{} Infinity for all to enjoy, it is best to upload it to any datafilehost and notify the community via email with any informative documentation.
\end{itemize}
\subsection{Example of new Plugin Icon Testing}%
\label{sub:example_plugin_icon_testing}
-For a simple test just copy an existing \texttt{<plugin\_name>.png} file into the cinfinity directory with the name \texttt{bluebanana.png} to write over the existing file. This icon will now show up in Cinelerra and still execute the Blue Banana function.
+For a simple test just copy an existing \texttt{<plugin\_name>.png} file into the cinfinity directory with the name \texttt{bluebanana.png} to write over the existing file. This icon will now show up in \CGG{} and still execute the Blue Banana function.
For an ffmpeg plugin, create \texttt{ff\_loop.png} and copy it to: \\
-\texttt{<cinlib\_path>/plugins/picon/original}. This icon will show up in Cinelerra if original is selected and execute the \textit{F\_loop} function.
+\texttt{<cinlib\_path>/plugins/picon/original}. This icon will show up in \CGG{} if original is selected and execute the \textit{F\_loop} function.
For a ladspa plugin, the text line in \texttt{\$HOME/.bcast5/ladspa\_plugins}$\dots$ as seen below:
2 \texttt{am\_pitchshift\_1433.so} \\
\texttt{AM pitchshifter} $1504922321\, 0\, 1\, 0\, 0\, 1\, 0\, 1\, 0\, 1\, 0\, 0$ indicates that you would create the icon: \\ \texttt{<cinlib\_path>/plugins/picon/cinfinity/am\_pitchshift\_1433.png} \\
For your own personal plugins, you can create a directory on your system and put any plugin png files you like into that directory. For example, if you want a specialized picon for \textit{F\_aeval}, create a picon named \texttt{ff\_aeval.png} in: \\ \texttt{<cinlib\_path>/plugins/picon/yournamehere.}
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
cd <cinlib>/plugins # go to the correct directory
mkdir -p picon/yournamehere # create subdirectory if does not exist
ls -l picon/* # list the picon directories
\subsection{Plugins/Effects Visibility}%
\label{sub:plugins_effects_visibility}
-Cinelerra contains many plugins, especially with the addition of ffmpeg, and it is somewhat difficult to find the one you are looking for in the Resources window. In Cinelerra-GG Infinity, the plugins have been categorized into the following subsets in the \textit{Visibility} section of the Resources window to make it easier to locate a particular one:
+\CGG{} contains many plugins, especially with the addition of ffmpeg, and it is somewhat difficult to find the one you are looking for in the Resources window. In \CGG{} Infinity, the plugins have been categorized into the following subsets in the \textit{Visibility} section of the Resources window to make it easier to locate a particular one:
\textit{Audio Effects, \quad Video Effects, \quad Audio Transitions, \quad Video Transitions}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/visibility01.png}
+ \includegraphics[width=0.8\linewidth]{visibility01.png}
\caption{Screenshot showing on the left hand side the Visibility box with Audio Effects highlighted.}
\label{fig:visibility01}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/visibility02.png}
+ \includegraphics[width=0.6\linewidth]{visibility02.png}
\caption{Screenshot showing the Visibility categories of plugins with all toggled on and audio highlighted.}
\label{fig:visibility02}
\end{figure}
\label{sub:expanders_plugin_subtrees}
To accentuate a set of common plugins, there are \textit{expander} arrows on the left side of the Resources window. You will see these expanders only when in \textit{Display text} mode, not \textit{icon} mode.
-Cinelerra’s default setup is in the file \texttt{\$CIN\_DAT/expan\-ders.txt} but if the user wants their own specific setup and if the file in \texttt{\$HOME/.\\bcast5/expanders.txt} exists, it will take precedence.
+\CGG{}’s default setup is in the file \texttt{\$CIN\_DAT/expan\-ders.txt} but if the user wants their own specific setup and if the file in \texttt{\$HOME/.\\bcast5/expanders.txt} exists, it will take precedence.
If there are recommendations for other relevant categories, they can be added. The subtree structure is applicable to any of the \textit{Video Effects/Transitions} or \textit{Audio Effects/Transitions}. You can not sort once an expansion is in effect (figure~\ref{fig:expander}).
The \texttt{expanders.txt} file has very specific requirements. The most specific is that there are no blanks -- you must use tabs only. A \# (pound sign) can be used in column 1 to indicate a comment. Here is a short example:
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
Video Effects
- Color_Correction
Blue Banana
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/expander.png}
+ \includegraphics[width=0.8\linewidth]{expander.png}
\caption{$\bigtriangledown$, $\rhd$ =expander; "-" = options}
\label{fig:expander}
\end{figure}
\subsection{Speed-up of Ffmpeg plugin usage with OPTS files}%
\label{sub:speedup_ffmpeg_plugin_opts}
-You can speed up some ffmpeg plugins that are quite time-consuming and use a lot of CPU. For a specific color-based example, Cinelerra uses 6 primary rendering color models. All of them have 3 components at full scale. Direct usage of a particular ffmpeg plugin from the ffmpeg command line might handle the planar at less than full scale chroma (yuv420), which means there is less data to manipulate. But when cinelerra loads a video it uses full scale color models. In other words:
+You can speed up some ffmpeg plugins that are quite time-consuming and use a lot of CPU. For a specific color-based example, \CGG{} uses 6 primary rendering color models. All of them have 3 components at full scale. Direct usage of a particular ffmpeg plugin from the ffmpeg command line might handle the planar at less than full scale chroma (yuv420), which means there is less data to manipulate. But when cinelerra loads a video it uses full scale color models. In other words:
\begin{itemize}[noitemsep]
- \item Cinelerra uses \textit{yuv444}
+ \item \CGG{} uses \textit{yuv444}
\item ffmpeg uses \textit{yuv420}
\end{itemize}
-if using an ffmpeg plugin that uses filters and many passes over the data, the amount of data is a big factor. If you load a file in Cinelerra with a
+if using an ffmpeg plugin that uses filters and many passes over the data, the amount of data is a big factor. If you load a file in \CGG{} with a
\texttt{same\_directory\_path\_and\_filename.opts}
file containing the following line, the full scale color modeling upgrade will not be performed until after any plugin, and then the render is faster:
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
video_filter=xxxxxx=threads=8 # where xxxxxx is the desired filter
\end{lstlisting}
When the file loads, however, it will initially take longer because it is running through the video filter. The format \textit{rgb} in ffmpeg uses more cpu time. For comparison, ffmpeg line that might be used:
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
ffmpeg -i /tmp/filename.mpeg -threads 15 -vf format=rgb24,xxxxxxs=threads=8 -acodec ac3 -vcodec libx265 - y /tmp/x.mp4
\end{lstlisting}
\label{sub:chorus}
It is a multitrack effect, where each track is a channel. For example if you have 4 voices per channel and 2 channels, you will have a total of 8 tracks.
-It is an effect that modulates the signal, precisely the pitches (instead of modulating the phases as for example in the \textit{Flanger}) plugin and creates voices from the original signal and adds them to the Output. You then get a chorus effect, with multiple voices \textit{singing} the same \textit{song} but with slightly different modulations. Voices not only modulate the original signal but also start with a certain delay. There are two components of delay, \textit{constant delay} and \textit{oscillating delay} (figure~\ref{fig:chorus}).
+It is an effect that modulates the signal, varies the pitch up and down (instead of modulating the phases as for example in the \textit{Flanger} plugin) and creates voices from the original signal and adds them to the Output. You then get a chorus effect, with multiple voices \textit{singing} the same song but with slightly different modulations. Voices not only modulate the original signal but also start with a certain delay. There are two components of delay, \textit{constant delay} and \textit{oscillating delay} (figure~\ref{fig:chorus}).
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.5\linewidth]{images/chorus.png}
+ \includegraphics[width=0.5\linewidth]{chorus.png}
\caption{GUI of configuration for Chorus plugin}
\label{fig:chorus}
\end{figure}
\item[Voices per channel]: number of items we want to put in the effect. Using more than 4 voices creates sound artifacts that lose the feel of a human voice choir, but can still be used as an artificial sound effect.
\item[Phase offset] (ms): is the constant delay, i.e. the amount of delay of the voices compared to the original signal.
\item[Depth] (ms): is the oscillating delay, i.e. the delay in the oscillation of the various voices from the original signal.
- \item[Rate] (Hz): is the speed at which we apply the oscillating delay. Practically the speed at which the oscillations occur.
+ \item[Rate] (Hz): is the speed at which we apply the oscillating delay. In other words, the speed at which the oscillations occur.
\item[Wetnwss] (db): Indicates how much of the original (dry) signal is taken into account compared to delayed voices.
\end{description}
\subsection{Compressor (Single Band)}%
\label{sub:compressor}
-Effect rewritten and improved.
-The audio compressor reduces the dynamic range of the audio, not the amount of data required to store the audio. In Cinelerra the compressor actually performs the function of an expander and compressor of the signal's dynamic range. A third and more sophisticated use serves to highlight the voice with respect to the sound background. It is a multitrack effect and can also be applied as a Shared Effect. (figure~\ref{fig:compressor}).
+The audio compressor reduces the dynamic range of the audio, not the amount of data required to store the audio. In \CGG{} the compressor actually performs the function of an expander and compressor of the signal's dynamic range. A third and more sophisticated use serves to highlight the voice with respect to the sound background. It is a multitrack effect and can also be applied as a Shared Effect. (figure~\ref{fig:compressor}).
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.7\linewidth]{images/compressor.png}
+ \includegraphics[width=0.7\linewidth]{compressor.png}
\caption{GUI of configuration for Compressor plugin}
\label{fig:compressor}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.7\linewidth]{images/compressorM.png}
+ \includegraphics[width=0.7\linewidth]{compressorM.png}
\caption{GUI of configuration for Compressor Multi plugin}
\label{fig:compressorM}
\end{figure}
\item[Solo]: brings only the active band to the Output, silencing the others. So we can make more precise adjustments without listening to the whole effect.
\item[Bypass band]: In contrast to Solo, it only brings the sound signals of the two inactive bands to the Output.
\item[Freq range]: is used to set bandwidth limits. You act separately on the left and right edge.
- \item[Stepness]: varies the slope of the edges of the band range. Creates some overlap in the band boundaries.
+ \item[Steepness]: varies the slope of the edges of the band range. Creates some overlap in the band boundaries.
\item[Channel]: is the equivalent of the \textit{Trigger} option in Compressor (single band). Allows you to choose the channel or track to act on.
\item[Window size]: Determines the number of samples used in the compression calculation. The more they are, the higher the quality of the result, but the more CPU usage.
\end{description}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.7\linewidth]{images/equalizer.png}
+ \includegraphics[width=0.7\linewidth]{equalizer.png}
\caption{Graphic Equalizer audio plugin}
\label{fig:equalizer}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.4\linewidth]{images/eq_param.png}
+ \includegraphics[width=0.4\linewidth]{eq_param.png}
\caption{Graphic Equalizer audio plugin}
\label{fig:eq_param}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.4\linewidth]{images/echo.png}
+ \includegraphics[width=0.4\linewidth]{echo.png}
\caption{The 3 dials of Echo plugin}
\label{fig:echo}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/echo-cancel.png}
+ \includegraphics[width=0.8\linewidth]{echo-cancel.png}
\caption{GUI for EchoCancel with crosshair and mode set to ON}
\label{fig:echo-cancel}
\end{figure}
It's a single-track effect. If you apply it to multiple tracks each will work on its own track independently of the others.
It consists of making a copy of the original sound wave and then playing it over the original one with a certain delay. The resulting signal (Output) will then be the sum of the two waves and will have peaks where the two values add up and gaps where the two values compensate each other. The result is a more \textit{evanescent} and \textit{metallic} sound. Much, however, depends on the intensity of the effect.
-The delay introduced consists of two distinct components: The \textit{constant delay} and the \textit{oscillating delay}. Their sum constitutes the total delay of the effect (figure~\ref{fig:flanger}).
+The delay introduced consists of two distinct components: the \textit{constant delay} and the \textit{oscillating delay}. Their sum constitutes the total delay of the effect (figure~\ref{fig:flanger}).
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.5\linewidth]{images/flanger.png}
+ \includegraphics[width=0.5\linewidth]{flanger.png}
\caption{GUI of configuration for Flanger plugin}
\label{fig:flanger}
\end{figure}
\begin{description}
- \item[Phase Offset]: it is the constant delay. Once set, its value does not change (unless we change it voluntarily, maybe with keyframes) for the duration of the effect.
+ \item[Phase Offset]: it is the constant delay. Once set, its value does not change (unless we change it, for example by use of keyframes) for the duration of the effect.
\item[Starting phase] \%: is the point of oscillation where we start the oscillating delay; basically it is the attack value at which the effect starts the calculations. Not to be confused with the point on the timeline where we apply the effect. It only matches this for the 0\% value. The position on the timeline where we want to start the flanger at a given starting phase value can be chosen using keyframes.
- \item[Depth]: It is the oscillating delay. This value determines the amplitude variation of the delayed (wet) signal phase. this oscillation will be maintained for the entire duration of the effect unless we change it voluntarily.
+ \item[Depth]: It is the oscillating delay. This value determines the amplitude variation of the delayed (wet) signal phase. this oscillation will be maintained for the entire duration of the effect unless we change it.
\item[Rate]: is the speed at which we apply the oscillating delay. Low values indicate a lower oscillation frequency, a high value a rapid succession of oscillations.
\item[Wetness]: indicates how much of the original (dry) signal is taken into account compared to the delayed (wet) signal.
\end{description}
\subsection{Reverb}%
\label{sub:reverb}
-Effect rewritten and improved.
-Reflections of sound to add depth and fullness; the sound will seem to come from a space that can go from a small bare room to large natural valleys, cathedrals, etc. The reverb is made up of a group of echoes that occur at the same time and feel, therefore, like a single effect. Basically simulates creation of a large number of reflections (lots of walls) which build up and then decay. You can use the reverb plugin to mix tracks together to simulate ambiance, because it is a multitrack effect.
+Reverb uses reflections of sound to add depth and fullness; the sound will seem to come from a space that can go from a small bare room to large natural valleys, cathedrals, etc. The reverb is made up of a group of echoes that occur at the same time making it feel like a single effect.
+Basically simulates creation of a large number of reflections, like lots of walls, which build up and then decay. You can use the reverb plugin to mix tracks together to simulate ambiance because it is a multitrack effect.
The configuration window (figure~\ref{fig:reverb}) shows a graph of the full band pass filter frequencies.
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.5\linewidth]{images/reverb.png}
+ \includegraphics[width=0.5\linewidth]{reverb.png}
\caption{GUI of configuration for Reverb plugin}
\label{fig:reverb}
\end{figure}
\begin{description}
- \item[Initial signal level](db): Allows you to set the level of the reflected signal. At 0 you start from its maximum level, decreasing the signal volume will give more presence to the original signal.
+ \item[Initial signal level](db): Allows you to set the level of the reflected signal. At 0 you start from its maximum level. Decreasing the signal volume will give more presence to the original signal.
\item[ms before reflections]: indicates when to start the reflected sounds in relation to the original sound (delay).
\item[First reflection level] (db): the sound level of the reflection that starts first.
\item[Last reflection leve] (db): the level of the last reflection. It is weaker than the first.
- \item[numbers of refelctions]: the number of reflections can be set as desired, CPU permitting. With a few reflections you get closer to the Chorus effect. You can start from values of 100 - 150, up to a maximum of 255.
- \item[ms of refelction]: Sets the action time of the effect. With high values you have more incisiveness
+ \item[numbers of refelctions]: the number of reflections can be set as desired as long as there is sufficient CPU to handle it. With a few reflections you get closer to the Chorus effect. You can start from values of 100 - 150, up to a maximum of 255.
+ \item[ms of refelction]: Sets the action time of the effect. With high values, the sound is more clear and sharp
\item[Low freq of bandpass] and \textbf{High freq of bandpass}: allow you to set the frequency limits (range) on which the effect acts.
- \item[Stepness of bandpass]: allows you to adjust the slope of the frequency range limits imposed by the previous items. With the value 1.00 we have a vertical edge that clearly separates the range of frequencies on which to act from the remaining ones (as you can see in figure~\ref{fig:reverb}). By sloping the edge we have a certain overlap and a smoother effect.
- \item[Window]: determines the number of frequency samples taken into account by the effect for its calculations. The higher the number, the smoother the effect; but the CPU is engaged more.
+ \item[Steepness of bandpass]: allows you to adjust the slope of the frequency range limits imposed by the previous items. With the value 1.00 we have a vertical edge that clearly separates the range of frequencies on which to act from the remaining ones (as you can see in figure~\ref{fig:reverb}). By sloping the edge we have a certain overlap and a smoother effect.
+ \item[Window]: determines the number of frequency samples taken into account by the effect for its calculations. The higher the number, the smoother the effect; but more CPU is used.
\end{description}
\subsection{Reverse Audio}%
\subsection{Synthesizer}%
\label{sub:Synthesizer}
-Effect rewritten and improved. Generate synthesizer sounds; to set key data, turn on Generate keyframes while tweaking (figure~\ref{fig:synthesizer}).
+Generate synthesizer sounds; to set key data, turn on Generate keyframes while tweaking (figure~\ref{fig:synthesizer}).
\begin{figure}[htpb]
\centering
- \includegraphics[width=1.0\linewidth]{images/synthesizer.png}
+ \includegraphics[width=1.0\linewidth]{synthesizer.png}
\caption{GUI for Synthesizer}
\label{fig:synthesizer}
\end{figure}
\subsection{Tremolo}%
\label{sub:tremolo}
-It serves to give flavors and vitality to the sound by modulating the amplitude of the sound signal and the delay (figure~\ref{fig:tremolo}).
+It serves to give various vibes and vitality to the sound by modulating the amplitude of the sound signal and the delay (figure~\ref{fig:tremolo}).
NOTE: There is often confusion between Tremolo and Vibrato, but the vibrato is the periodic variation of the height of a note (frequency) while the tremolo is the periodic variation of the height (amplitude) of the sound wave.
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.5\linewidth]{images/tremolo.png}
+ \includegraphics[width=0.5\linewidth]{tremolo.png}
\caption{GUI of configuration for Tremolo plugin}
\label{fig:tremolo}
\end{figure}
\begin{description}
- \item[Phase offset] (\%): is where the oscillation effect begins. At 0\% we are at maximum volume; increasing the percentage we start at a lower volume.
+ \item[Phase offset] (\%): is where the oscillation effect begins. At 0\% we are at maximum volume; to lower the volume, increase the percentage.
\item[Depth] (dB): is the oscillation damping value. You can only decrease the level, you cannot increase it.
\item[Rate] (Hz): is the speed at which the oscillations are repeated.
- \item[Waveform]: you can choose waveform algorithms to use in effect calculations. We have: \textit{Sine}; \textit{Sawtooth}; \textit{Rev Sawtooth}; \textit{Square} and \textit{Triangle}.
+ \item[Waveform]: you can choose waveform algorithms to use in effect calculations.
+Currently available waveforms are: \textit{Sine}; \textit{Sawtooth}; \textit{Rev Sawtooth}; \textit{Square} and \textit{Triangle}.
\end{description}
\section{Audio Ladspa Effects}%
\label{sec:audio_ladspa_effects}
\settocdepth{section}
-Ladspa effects are supported in realtime and rendered mode for audio. These audio effects are supported since Cinelerra implements the LADSPA interface as accurately as possible. Besides the supplied LADSPA effects\protect\footnote{credit Steve Harris}, additional LADSPA effects can be enabled by setting the \texttt{LADSPA\_PATH} environment variable to the location of your LADSPA plugins:
+Ladspa effects are supported in realtime and rendered mode for audio. These audio effects are supported since \CGG{} implements the LADSPA interface as accurately as possible. Besides the supplied LADSPA effects\protect\footnote{credit Steve Harris}, additional LADSPA effects can be enabled by setting the \texttt{LADSPA\_PATH} environment variable to the location of your LADSPA plugins:
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
export LADSPA_PATH=/usr/lib/ladspa
\end{lstlisting}
\section[Audio LV2 / Calf Plugins]{Audio LV2 / Calf Plugins\protect\footnote{Optional Feature - OS dependent}}%
\label{sec:audio_lv2_calf_plugins}
-LV2 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 Cinelerra audio without having to change Cinelerra every time. Because the LV2 plugins are separate from Cinelerra-GG Infinity, if one fails or does not perform as expected, Cinelerra should stay running and you will have to contact the programmers responsible for that plugin for a fix.
+LV2 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 Cinelerra 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 Cinelerra 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.
+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.
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.
-Cinelerra’s buffer size setting may cause a delay in activation of the changes you make taking effect, so you can lessen the time by using a small buffer. Notice that $1024$ samples at $48000$ samples per sec is only $\frac{1}{50}^{th}$ a second. This is not a lot of time to shuffle a bunch of stuff. Short buffers produce low latency, but no time for complex programs or lots of stacked effects. Bigger buffers allow for more complex setups.
+\CGG{}’s buffer size setting may cause a delay in activation of the changes you make taking effect, so you can lessen the time by using a small buffer. Notice that $1024$ samples at $48000$ samples per sec is only $\frac{1}{50}^{th}$ a second. This is not a lot of time to shuffle a bunch of stuff. Short buffers produce low latency, but no time for complex programs or lots of stacked effects. Bigger buffers allow for more complex setups.
To set the buffer size:
\texttt{Settings $\rightarrow$ Preferences $\rightarrow$ tab Playback A $\rightarrow$ section Audio Out $\rightarrow$ variable Playback buffer samples}
-However, be forewarned that due to variability in the lv2 plugin programming code, some of the plugins only work with the minimum buffer size of $1024$. In these cases, what you will see is the main track canvas cursor just bounces back and forth over a very small area in the timeline. This does not crash Cinelerra but you will have to remove the plugin to continue working.
-You can specify a certain set of LV2 plugins to use by setting \texttt{LV2\_PATH} as shown below before starting Cinelerra -- include a colon ($:$) separator for multiple paths. The default path for most operating systems is \texttt{/usr/lib64/lv2}. To list the system installed lv2 plugins key in: \texttt{lv2ls}.
+However, be forewarned that due to variability in the lv2 plugin programming code, some of the plugins only work with the minimum buffer size of $1024$. In these cases, what you will see is the main track canvas cursor just bounces back and forth over a very small area in the timeline. This does not crash \CGG{} but you will have to remove the plugin to continue working.
+You can specify a certain set of LV2 plugins to use by setting \texttt{LV2\_PATH} as shown below before starting \CGG{} -- include a colon ($:$) separator for multiple paths. The default path for most operating systems is \texttt{/usr/lib64/lv2}. To list the system installed lv2 plugins key in: \texttt{lv2ls}.
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[numbers=none]
export LV2_PATH=/tmp/j/balance.lv2/usr/local/lib/lv2/:/usr/local/lv2
\end{lstlisting}
When you change this field, cin will automatically restart and load the newly specified lv2 plugins. If when switching \texttt{LV2\_PATH} or if the lv2 audio plugins are not displayed/usable in the Resources window, you can execute a reload via:
\texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Interface tab $\rightarrow$ Reload plugin in\-dex}
-or else before you bring up Cinelerra, delete \texttt{\$HOME/.bcast5/Cinelerra\_\\plugins} so that the plugins get properly reloaded.
+or else before you bring up \CGG{}, delete \texttt{\$HOME/.bcast5/\CGG{}\_\\plugins} so that the plugins get properly reloaded.
There are some lv2 plugins that display a \textit{glitzy} UI (User Interface); for example the \textit{Calf plugins}. For these LV2 plugins, if you want that to automatically come up without having to click on the UI button on the simplified UI interface, there is a flag to enable that. It is at:
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/reload.png}
- \caption{\textit{Reload plugin index} in yellow and \textit{Auto start lv2 gui} unchecked}
+ \includegraphics[width=0.9\linewidth]{reload.png}
+ \caption{Reload plugin index in yellow and Auto start lv2 gui unchecked}
\label{fig:reload}
\end{figure}
-There is also a blacklist that prevents known problematic-for-Cinelerra lv2 plugins from loading to avoid crashes. If others are found to have problems, once informed about them, they will be added to this blacklist. In order to determine which lv2 plugin causes a SEGV on Cinelerra startup, you can start from a terminal window and you will see each plugin that is being loaded and the last one shown before the crash is a bad plugin. However, many of the plugins causing a crash are due to not having been compiled on your current system with the current compiler so may actually work correctly on other user systems and so will not be added to the Cinelerra-wide blacklist. You can either recompile the problematic plugin, or modify your own blacklist which you will have to maintain and save so as not to be written over when loading a new build.
+There is also a blacklist that prevents known problematic-for-\CGG{} lv2 plugins from loading to avoid crashes. If others are found to have problems, once informed about them, they will be added to this blacklist. In order to determine which lv2 plugin causes a SEGV on \CGG{} startup, you can start from a terminal window and you will see each plugin that is being loaded and the last one shown before the crash is a bad plugin. However, many of the plugins causing a crash are due to not having been compiled on your current system with the current compiler so may actually work correctly on other user systems and so will not be added to the \CGG{}-wide blacklist. You can either recompile the problematic plugin, or modify your own blacklist which you will have to maintain and save so as not to be written over when loading a new build.
Note the UI button in the upper right hand corner above the Reset button (figure~\ref{fig:calf}). If you click this button, a glitzy interface window comes up (if available) for changing variable values. It is possible that a bug in the LV2 plugin causes the glitzy window to appear as blank and then die, but in that case the original simple text window might still work -- in either case, if the timeline movement hangs, just detach the plugin to continue your current session. There is an environment variable that you can set, \texttt{BC\_TRAP\_LV2\_SEGV}, to get a dump of the failure which may be helpful for debugging.
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.9\linewidth]{images/calf.png}
+ \includegraphics[width=1.0\linewidth]{calf.png}
\caption{Screencast of simple text interface in the middle of the screen for a Calf LV2 plugin}
\label{fig:calf}
\end{figure}
-When the glitzy ui is up, the simple text window remains up also since it is the Cinelerra side and keeps track of the value changes so they remain in effect for further usage of the plugin. Changes to one or the other will occur in both with the exception of certain features in the glitzy window which are not communicated correctly back to Cinelerra; for example a reset button -- the simple interface Reset button must be used instead. To change values in the glitzy window you use the mouse and move up or down unlike a knob that turns! (Figure~\ref{fig:calf02})
+When the glitzy ui is up, the simple text window remains up also since it is the \CGG{} side and keeps track of the value changes so they remain in effect for further usage of the plugin. Changes to one or the other will occur in both with the exception of certain features in the glitzy window which are not communicated correctly back to \CGG{}; for example a reset button -- the simple interface Reset button must be used instead. To change values in the glitzy window you use the mouse and move up or down unlike a knob that turns! (Figure~\ref{fig:calf02})
-In order to test a particular plugin without bringing up Cinelerra, especially for ones that do not operate, it is possible to manually display an lv2ui gui with: \\
+In order to test a particular plugin without bringing up \CGG{}, especially for ones that do not operate, it is possible to manually display an lv2ui gui with: \\
\texttt{/cin-path/lv2ui <lv2-uri>} \\
For example:
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
/tmp/cinelerra-5.1/bin/lv2ui http://calf.sourceforge.net/plugins/Flanger
\end{lstlisting}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/calf02.png}
+ \includegraphics[width=0.8\linewidth]{calf02.png}
\caption{Screencast with a Calf plugin glitzy window that appears when clicking the simple interface UI button.}
\label{fig:calf02}
\end{figure}
Automatically scale to a specified size.
-\subsection{Blue Banana\protect\footnote{credit to Monty Montgomery programmer}}%
+\subsection{Blue Banana}%
\label{sub:blue_banana}
-Blue Banana is an \textit{HSL Qualifier} (HSL= hue, saturation, lightness), one of the basic tools of any grading software that are based on circumscribing a zone of the frame by extracting a chromatic key and producing a \textit{matte} in the alpha channel (Secondary Color Correction). Blue Banana differs not by creating a real matte, but by creating a \textit{selection mask} exclusively for use within the plugin. The BlueBanana plugin has a couple of useful purposes. It can be used for color transformation or remapping -- by isolating a specific color and then performing color change/correction on only that color (or color ranges). Another useful purpose is for chroma-key filtering, using multiple BlueBanana plugins on the same track. Also, it can be used in conjunction with the mask operation of the Compositor. Usage of BlueBanana may seem complicated at first, but it is necessarily so in order to get enough control to produce the desired effect simply and quickly. Just changing a single color is actually quite easy. BlueBanana is keyframable (figure~\ref{fig:bluebanana}).
+Blue Banana\protect\footnote{credit to Monty Montgomery programmer} is an \textit{HSL Qualifier} (HSL= hue, saturation, lightness), one of the basic tools of any grading software that are based on circumscribing a zone of the frame by extracting a chromatic key and producing a \textit{matte} in the alpha channel (Secondary Color Correction). Blue Banana differs not by creating a real matte, but by creating a \textit{selection mask} exclusively for use within the plugin. The BlueBanana plugin has a couple of useful purposes. It can be used for color transformation or remapping -- by isolating a specific color and then performing color change/correction on only that color (or color ranges). Another useful purpose is for chroma-key filtering, using multiple BlueBanana plugins on the same track. Also, it can be used in conjunction with the mask operation of the Compositor. Usage of BlueBanana may seem complicated at first, but it is necessarily so in order to get enough control to produce the desired effect simply and quickly. Just changing a single color is actually quite easy. BlueBanana is keyframable (figure~\ref{fig:bluebanana}).
The basic strategy for BlueBanana is to:
\begin{figure}[htpb]
\centering
- \includegraphics[width=1.0\linewidth]{images/bluebanana.png}
+ \includegraphics[width=1.0\linewidth]{bluebanana.png}
\caption{Screencast showing the BlueBanana plugin control}
\label{fig:bluebanana}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/brightness.png}
+ \includegraphics[width=0.6\linewidth]{brightness.png}
\caption{How it works Brightness and Contrast}
\label{fig:brightness}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.9\linewidth]{images/c41.png}
+ \includegraphics[width=0.9\linewidth]{c41.png}
\caption{C41 - Control window and compositor window in action}
\label{fig:c41}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.5\linewidth]{images/chroma-key.png}
+ \includegraphics[width=0.5\linewidth]{chroma-key.png}
\caption{Chroma Key control window}
\label{fig:chroma-key}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.55\linewidth]{images/chroma-key-hsv.png}
+ \includegraphics[width=0.55\linewidth]{chroma-key-hsv.png}
\caption{Keying a green screen with Chroma Key (HSV)}
\label{fig:chroma-key-hsv}
\end{figure}
\subsection{Color 3 Way}%
\label{sub:color_3_way}
-Together with \textit{Histogram Bezier / Curves} is the main tool of Color Grading because you can modify the colors of \textit{Shadows}, \textit{Midtones}, and \textit{Highlights} as desired. Color 3 Way is keyframable (figure~\ref{fig:color3way}).
+Together with \textit{Histogram Bezier / Curves} Color 3 Way is the main tool of Color Grading because you can modify the colors of \textit{Shadows}, \textit{Midtones}, and \textit{Highlights} as desired. Color 3 Way is keyframable (figure~\ref{fig:color3way}).
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/color3way.png}
+ \includegraphics[width=0.8\linewidth]{color3way.png}
\caption{Color 3 Way control window}
\label{fig:color3way}
\end{figure}
\item[White Balance] used in conjunction with the \textit{color picker} on a neutral color of the output, it will automatically balance the white.
\end{description}
+\subsection{ColorSpace}%
+\label{sub:color_space}
+
+This plugin is a tool that can be used to convert your input media, such as a recording from your camera,
+from one color space/range to another. It works for both RGB and YUV as set by your project format.
+Options are BT601, BT709, or BT2020 for Color Space input and output and JPEG or MPEG for Color Range
+input and output. The Inverse option checkbox is available in case your media was rendered in the wrong
+color space or range so that you can fix it.
+
+\textbf{Algorithm for conversion} -- where equations is a $3\times3$ matrix multiply
+
+\qquad $output = (input - input\_zero) \times equations + output\_zero$
+
+\textbf{Algorithm for inverse} -- where equations is a $3\times3$ matrix multiply
+
+\textit{Description}: invert(equations); swap(input,output); swap(input\_zero,output\_zero)
+
+\qquad $input = (output - output\_zero) \times inverse\_equations + input\_zero$
+
+\begin{figure}[hbtp]
+ \centering
+ \includegraphics[width=0.45\linewidth]{colorspace.png}
+ \caption{ColorSpace control window}
+ \label{fig:colorspace}
+\end{figure}
+
+
\subsection{CriKey}%
\label{sub:crikey}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/crikey.png}
+ \includegraphics[width=0.5\linewidth]{crikey.png}
\caption{three active point created in CriKey}
\label{fig:crikey}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/crikey01.png}
+ \includegraphics[width=0.8\linewidth]{crikey01.png}
\caption{The screenshot shows the compositor with some default settings in the controls window.}
\label{fig:crikey01}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/crikey02.png}
+ \includegraphics[width=0.8\linewidth]{crikey02.png}
\caption{same screenshot with moving Threshold}
\label{fig:crikey02}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=1.0\linewidth]{images/crop_position.png}
+ \includegraphics[width=1.0\linewidth]{crop_position.png}
\caption{Crop tool and Crop \& Position plugin compared}
\label{fig:crop_position}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/descratch01.png}
+ \includegraphics[width=0.6\linewidth]{descratch01.png}
\caption{DeScratch control window}
\label{fig:descratch01}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/descratch02.png}
+ \includegraphics[width=0.8\linewidth]{descratch02.png}
\caption{Various parameters of DeScratch}
\label{fig:descratch02}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.9\linewidth]{images/descratch.png}
+ \includegraphics[width=0.9\linewidth]{descratch.png}
\caption{Original video with scratch; Option Mark selected and Final video}
\label{fig:descratch}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/deinterlace.png}
+ \includegraphics[width=0.6\linewidth]{deinterlace.png}
\caption{Pulldown menu}
\label{fig:deinterlace}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.4\linewidth]{images/denoise.png}
+ \includegraphics[width=0.4\linewidth]{denoise.png}
\caption{Control window of the DeNoise plugin}
\label{fig:denoise}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/diff-key.png}
+ \includegraphics[width=0.8\linewidth]{diff-key.png}
\caption{Difference key and its problematic output}
\label{fig:diff-key}
\end{figure}
Interlaced video reading: $F1-f1$ then $F1-f2$ then $F2-f1$ then $F2-f2$ \dots
There may be visual problems if the Top type interlacing is read according to a Bottom scheme. So it's important to know if a video is Top or Bottom. Generally an \textit{HD} video is Top; a \textit{DV} video (both PAL and NTSC) is Bottom; \textit{SD} (PAL) is Top; \textit{SD} (NTSC) is Bottom (but not always). Instead, high-definition videos need to be more compressed and this contrasts with the interlacing that is little and badly compressible, so modern videos are mostly \textit{progressive}.
-\subsubsection*{In Cinelerra-GG}
+\subsubsection*{In \CGG{}}
\label{ssub:in_cin_gg}
\begin{enumerate}
\begin{enumerate}
\item Create a new project with doubled frame rate. That is, make it $50\,fps$ if your source footage is $25i$.
In \texttt{Resources $\rightarrow$ Media $\rightarrow$ Info} set the interlaced type (or unknown)
- \item Insert your source footage onto a video track in the timeline. Now, Cinelerra will playback each
+ \item Insert your source footage onto a video track in the timeline. Now, \CGG{} will playback each
frame of your footage twice. There will be visual artifacts because the video is interlaced and the
monitor is progressive.
\item Apply the \textit{Frames to Fields} effect. Be sure to choose the correct field order. If we know or believe that the original video is \textit{Top First} let's try it first, but it doesn't have to be the right solution. The only way is to playback and look for visual artifacts.
\item Render your project to an intermediate clip. Be sure to choose a rather lossless video codec, for
example \textit{Motion-JPEG-A} or even \textit{uncompressed YUV} if you have plenty of storage.
\item Insert the intermediate clip into your original project. Make sure the doubled framerate has been
- detected correctly by Cinelerra (by looking in the clip's media \textit{info} in the media resources folder).
+ detected correctly by \CGG{} (by looking in the clip's media \textit{info} in the media resources folder).
\item Apply the \textit{Fields to frames} effect to the intermediate clip. This will combine two adjacent fields
into one interlaced field with the original frame rate.
\item Do the final render on your original project. Now there will be no visual artifacts on the monitor.
\subsection{Gamma}%
\label{sub:gamma}
-\textit{Log} camera images store colors in a $logarithmic$ scale. The blacks in these images are nearly $0$ and the whites are supposed to be infinity. The graphics card and most video codecs store colors in a $linear$ scale but Cinelerra keeps log camera images in their original logarithmic scale when it renders them. This is necessary because the raw image parser can not always decode the proper gamma ($\gamma$) values for the images. It also does its processing in $16\,bit$ integers, which takes away a lot of information.
+\textit{Log} camera images store colors in a $logarithmic$ scale. The blacks in these images are nearly $0$ and the whites are supposed to be infinity. The graphics card and most video codecs store colors in a $linear$ scale but \CGG{} keeps log camera images in their original logarithmic scale when it renders them. This is necessary because the raw image parser can not always decode the proper gamma ($\gamma$) values for the images. It also does its processing in $16\,bit$ integers, which takes away a lot of information.
-Mathematically, the gamma function is exponential ($output = input^{\gamma}$) and therefore the inverse of the logarithmic function [$output = \log(input)$]. Actually the formula used by the Cinelerra-gg plugin is: $output = input^{\frac{1}{\gamma}}$ which allows for a range of values $0 \div 1.0$. The gamma effect converts the logarithmic colors to linear colors through a \textit{gamma value} and a \textit{maximum value}. The gamma value determines how steep the output curve is (i.e. the value of the gamma parameter; for color space Rec709 is $2.4$ ($\frac{1}{\gamma} =0.41\dots$), for sRGB is $2.2$ ($\frac{1}{\gamma} =0.45\dots$), etc.). The maximum value is where $1.0$ in the output corresponds to maximum brightness in the input. It serves to avoid clipped values because it allows you to set the maximum value of the output, $1.0$, whenever range adjustment is done (see figure~\ref{fig:gamma01}). It is important to adjust the two parameters accurately in order to avoid undesired and unexpected effects, such as excessive values, unbalanced image, incorrect linearization, etc.
+Mathematically, the gamma function is exponential ($output = input^{\gamma}$) and therefore the inverse of the logarithmic function [$output = \log(input)$]. Actually the formula used by the \CGG{} plugin is: $output = input^{\frac{1}{\gamma}}$ which allows for a range of values $0 \div 1.0$. The gamma effect converts the logarithmic colors to linear colors through a \textit{gamma value} and a \textit{maximum value}. The gamma value determines how steep the output curve is (i.e. the value of the gamma parameter; for color space Rec709 is $2.4$ ($\frac{1}{\gamma} =0.41\dots$), for sRGB is $2.2$ ($\frac{1}{\gamma} =0.45\dots$), etc.). The maximum value is where $1.0$ in the output corresponds to maximum brightness in the input. It serves to avoid clipped values because it allows you to set the maximum value of the output, $1.0$, whenever range adjustment is done (see figure~\ref{fig:gamma01}). It is important to adjust the two parameters accurately in order to avoid undesired and unexpected effects, such as excessive values, unbalanced image, incorrect linearization, etc.
\begin{figure}[htpb]
\centering
- \includegraphics[width=1.0\linewidth]{images/gamma01.png}
+ \includegraphics[width=1.0\linewidth]{gamma01.png}
\caption{settting \textit{Maximun} to $0.5900$}
\label{fig:gamma01}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=1.0\linewidth]{images/gamma02.png}
+ \includegraphics[width=1.0\linewidth]{gamma02.png}
\caption{Setting \textit{Maximun} to $0.6100$ and \textit{Gamma} to $0.3300$}
\label{fig:gamma02}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/histeq.png}
+ \includegraphics[width=0.8\linewidth]{histeq.png}
\caption{Control window and split screen}
\label{fig:histeq}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/histogram.png}
+ \includegraphics[width=0.8\linewidth]{histogram.png}
\caption{Master Histogram and RGB Histogram}
\label{fig:histogram}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/bezier.png}
+ \includegraphics[width=0.8\linewidth]{bezier.png}
\caption{Histogram Bezier / Curves}
\label{fig:bezier}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.75\linewidth]{images/ex-bezier.png}
+ \includegraphics[width=0.75\linewidth]{ex-bezier.png}
\caption{Gain Up/Down; clamp; S-Shaped curve and Luma Key}
\label{fig:ex-bezier}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/holographictv.png}
+ \includegraphics[width=0.8\linewidth]{holographictv.png}
\caption{Holographic messages in CinGG!}
\label{fig:holographictv}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/linear.png}
+ \includegraphics[width=0.8\linewidth]{linear.png}
\caption{For clarity of presentation only 2 fields are shown}
\label{fig:linear}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.9\linewidth]{images/motion51.png}
+ \includegraphics[width=0.9\linewidth]{motion51.png}
\caption{Motion51 plugin window with its default options set.}
\label{fig:motion51}
\end{figure}
\subsection{Motion 2 Point}%
\label{sub:motion_2_point}
-Motion stabilization using 2 pass tracking. For theory and explanations refer to the \href{sub:motion}{Motion} plugin.
+Motion stabilization using 2 pass tracking. For theory and explanations refer to the \hyperref[sub:motion]{Motion} plugin.
\subsection{Motion Blur}%
\label{sub:motion_blur}
\subsection{MotionCV}%
\label{sub:motioncv}
-Motion tracking/stabilization from the community version of Cinelerra. For theory and explanations refer to the \href{sub:motion}{Motion} plugin.
+Motion tracking/stabilization from the community version of \CGG{}. For theory and explanations refer to the \hyperref[sub:motion]{Motion} plugin.
\subsection{MotionHV}%
\label{sub:motionhv}
-Updated motion tracking/stabilization of 2017 from the original author of Cinelerra. For theory and explanations refer to the \href{sub:motion}{Motion} plugin.
+Updated motion tracking/stabilization of 2017 from the original author of \CGG{}. For theory and explanations refer to the \hyperref[sub:motion]{Motion} plugin.
\subsection{Oil painting}%
\label{sub:oil_painting}
\subsection{Overlay}%
\label{sub:overlay}
-This effect can combine several tracks by using the so called Overlayer. This is a basic internal device normally used by Cinelerra GG Infinity to create the dissolve transitions and for compositing the final output of every track onto the output bitmap. The Overlayer has the ability to combine one or several image layers on top of a bottom layer. It can do this combining of images in several different (and switchable) output modes such as \textit{Normal}, \textit{Additive}, \textit{Subtractive}, \textit{Multiply} (Filter), \textit{Divide}, \textit{Max} and \textit{Replace}. For a detailed list refer to the on \href{cha:overlays}{Overlays} chapter -- PorterDuff.
+This effect can combine several tracks by using the so called Overlayer. This is a basic internal device normally used by \CGGI{} to create the dissolve transitions and for compositing the final output of every track onto the output bitmap. The Overlayer has the ability to combine one or several image layers on top of a bottom layer. It can do this combining of images in several different (and switchable) output modes such as \textit{Normal}, \textit{Additive}, \textit{Subtractive}, \textit{Multiply} (Filter), \textit{Divide}, \textit{Max} and \textit{Replace}. For a detailed list refer to the on \hyperref[cha:overlays]{Overlays} chapter -- PorterDuff.
The \textit{overlay} plugin enables the use of this Overlayer device in the middle of any plugin stack, opening endless filtering and processing possibilities. It is only useful as a \textit{shared plugin} (i.e. a multitrack plugin). To use the overlay plugin:
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.5\linewidth]{images/perspective.png}
+ \includegraphics[width=0.5\linewidth]{perspective.png}
\caption{perspective control window}
\label{fig:perspective}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.8\linewidth]{images/perspective01.png}
+ \includegraphics[width=0.8\linewidth]{perspective01.png}
\caption{Clockwise: Nearest; Linear; OpenGL and Cubic}
\label{fig:perspective01}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.8\linewidth]{images/rgbshift.png}
+ \includegraphics[width=0.8\linewidth]{rgbshift.png}
\caption{Bad Misaligned color and after color aligned}
\label{fig:rgbshift}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.8\linewidth]{images/radial.png}
+ \includegraphics[width=0.8\linewidth]{radial.png}
\caption{For clarity of presentation only 2 fields are shown}
\label{fig:radial}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.45\linewidth]{images/rumbler.png}
+ \includegraphics[width=0.45\linewidth]{rumbler.png}
\caption{Rumbler control window}
\label{fig:rumbler}
\end{figure}
\subsection{SVG via Inkscape}%
\label{sub:svg_via_inkscape}
-This plugin allows the user to manipulate an SVG (scalable vector graphics) image with \textit{Inkscape} without having to leave the program. The associated Cinelerra window provides the ability to change the DPI, the Out $x/y$ coordinates, and the Out w/h values. For more information on use of inkscape, refer to: {\small \url{https://inkscape.org/develop/about-svg/}}
+This plugin allows the user to manipulate an SVG (scalable vector graphics) image with \textit{Inkscape} without having to leave the program. The associated \CGG{} window provides the ability to change the DPI, the Out $x/y$ coordinates, and the Out w/h values. For more information on use of inkscape, refer to: {\small \url{https://inkscape.org/develop/about-svg/}}
\begin{description}
\item[DPI] is Dots per inch and it represents the resolution of the SVG image. Since the image is scaled with interpolation mode linear, the edges will look blurry when the input resolution is lower than the output resolution. You can either set the desired \textit{DPI value} in the window or use the tumbler on the integer text box, then use the \textit{update dpi} button to have the change take effect. Changing DPI causes the entire image to be re-exported via inkscape. DPI changes cause adjustments in the resolution, speed of re-import, and storage needed for the image data.
\begin{figure}[hbtp]
\centering
- \includegraphics[width=1.0\linewidth]{images/svg.png}
+ \includegraphics[width=1.0\linewidth]{svg.png}
\caption{Control window and Inkscape}
\label{fig:svg}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.5\linewidth]{images/scaleratio.png}
+ \includegraphics[width=0.5\linewidth]{scaleratio.png}
\caption{Many parameters of scale ratio}
\label{fig:scaleratio}
\end{figure}
\vspace{2ex}
\begin{wrapfigure}[20]{O}{0.4\linewidth}
% \vspace{-4ex}
- \includegraphics[width=0.9\linewidth]{images/staveraging.png}
+ \includegraphics[width=0.9\linewidth]{staveraging.png}
\caption{STA control window}
\label{fig:staveraging}
\end{wrapfigure}
\subsection{Sketcher}%
\label{sub:Sketcher}
-Now you can sketch \textit{lines}, \textit{curves} or \textit{shapes}, on your video in different colors using various pen widths and pen type with the \texttt{sketcher} plugin. You can even fill them. You can do rotations and scaling and apply two Antialiasing modes; single and double. Getting started is fairly easy -- simply hold down the \textit{shift key} while using the \textit{left mouse button} to create a bunch of points in the compositor window. However, to do more than that you will need to understand the buttons and options or you may end up with unexpected results.
+Now you can sketch \textit{lines}, \textit{curves} or \textit{shapes}, on your video in different colors using various pen widths and pen type with the \texttt{sketcher} plugin. You can even fill them. You can do rotations and scaling and apply two anti-aliasing modes; single and double. Getting started is fairly easy -- simply hold down the \textit{shift key} while using the \textit{left mouse button} to create a bunch of points in the compositor window. However, to do more than that you will need to understand the buttons and options or you may end up with unexpected results.
(figure~\ref{fig:sketcher}) shows the Sketcher gui and the sketch lines/curves created in the Compositor.
\begin{figure}[hbtp]
\centering
- \includegraphics[width=1.0\linewidth]{images/sketcher.png}
+ \includegraphics[width=1.0\linewidth]{sketcher.png}
\caption{Sketcher control window and sketch on Compositor}
\label{fig:sketcher}
\end{figure}
-In the screencast, note the Sketcher window gui \textit{Curve top section} and the \textit{Point bottom section}. The pink circle sketch is $id\,\#1$ in the curve section. Since $id\,\#2$ is highlighted in the Curve section, the X/Y coordinates in the Point section below show the points used to create the blue shape. Point 6 is selected so we see a red crosshair (\textit{Drag point}) inside the rectangle. The yellow arrow on the image is $id\,\#3$ curve. Finally the cursor shows Double antialiasing.
+In the screencast, note the Sketcher window gui \textit{Curve top section} and the \textit{Point bottom section}. The pink circle sketch is $id\,\#1$ in the curve section. Since $id\,\#2$ is highlighted in the Curve section, the X/Y coordinates in the Point section below show the points used to create the blue shape. Point 6 is selected so we see a red crosshair (\textit{Drag point}) inside the rectangle. The yellow arrow on the image is $id\,\#3$ curve. Finally the cursor shows Double anti-aliasing.
\subsubsection*{Some basic rules}%
\label{ssub:some_basic_rules}
LMB click almost anywhere on the compositor screen will automatically show, in the currently highlighted curve, the closest point by turning it red.
-There is no \textit{undo} recorded between gui updates. Recommend using the option "b" to save a backup if you get to a place where you want to make sure you do not lose your sketch.
+There is no \textit{undo} recorded between gui updates. It is recommended that you use the option "b" to save a backup if you get to a place where you want to make sure you do not lose your sketch.
\begin{center}
\small
\begin{longtable}{{m{15em}m{13em}m{12em}}}
- \caption{Titler controls}
- \label{tabular:titler controls} \\ % note that double backslash is mandatory here
+ \caption{Sketcher controls}
+ \label{tabular:sketcher controls} \\ % note that double backslash is mandatory here
\toprule
\textbf{Compositor: Mouse usage} &
\textbf{Compositor: Action} &
\item[Anti-Aliasing] You can set Off; On or Double. Default is On.
\item[Color] refers to the current curve pen color. Click on the \textit{Color rectangle} to bring up the Color window to change any of the color values, including alpha.
\item[Drag] check to create curves and to be able to see any Off type curves. Uncheck for render/viewing.
- \item[Reset] -- in the \textit{Curve section}, all of the curve lines will be deleted except for an empty default curve.
+ \item[Reset] -- in the \textit{Curve section}, all of the curve lines will be deleted except for an empty default curve;
-- in the \textit{Point section}, all points for the highlighted curve in the Curve section will be deleted.
\item[Width] integer width of line; width of $1$ is the default; width of $0$ is the smallest size of $1$ pixel.
\item[ID] is the label number of the curve or point.
\item[Pen] value can be set with the pulldown to \textit{box} (a square), \textit{+}, \textit{/}, \textit{x} or \textit{off}. The default is \textit{x}.
\item[Alpha] alpha value as set in the Color window. Default is $1$ which is totally opaque.
- \item[Arc Type] value can be set with this pulldown, which is to the right of the \texttt{Drag} checkbox, to either \textit{off}, \textit{line}, \textit{curve}, or \textit{fill}. Off is the default. If the line type is off when you uncheck drag, you will no longer see the line/curve. Fill specifies a point be inside the region to be filled with the chosen color. Multiple fill points can be used within a single curve.
+ \item[Arc Type] value can be set with this pulldown, which is to the right of the \texttt{Drag} checkbox, to either \textit{off}, \textit{line}, \textit{curve}, or \textit{fill}. \textit{Off} is the default. If the line type is off when you uncheck drag, you will no longer see the line/curve. \textit{Fill} specifies a point be inside the region to be filled with the chosen color. Multiple fill points can be used within a single curve.
\item[Up] moves the highlighted Curve or Point Up in the stacking order. Multiple points, but not multiple curves, can be highlighted and moved.
- \item[Dn] moves the highlighted Curve or Point(s) Down in the stacking order.
+ \item[Dn] moves the highlighted Curve or Point(s) down in the stacking order.
\item[X] is the point’s $X$ coordinate.
\item[Y] is the point’s $Y$ coordinate.
\end{description}
\subsubsection*{Fill detailed information}%
\label{ssub:fill_detailed_information}
-The \textit{fill} point is a marker point, and not really part of the curve. That point identifies the inside of the loop. It can also be used to identify the outside of the loop in order to fill that. The loop is created by drawing a line draw from the last point to the first point in the curve. The line type of this last segment is from the last point of the curve. If there are isolated loops in the curve (it is self intersecting) then you will be able to use multiple fill points to fill these regions.
+The \textit{fill} point is a marker point, and not really part of the curve. That point identifies the inside of the loop. It can also be used to identify the outside of the loop in order to fill that. The loop is created by drawing a line from the last point to the first point in the curve. The line of this last segment is from the last point of the curve. If there are isolated loops in the curve (it is self intersecting) then you will be able to use multiple fill points to fill these regions.
\subsection{Sphere Cam}%
\label{sub:sphere_cam}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.35\linewidth]{images/timeaverage.png}
+ \includegraphics[width=0.35\linewidth]{timeaverage.png}
\caption{GUI for Time Average}
\label{fig:timeaverage}
\end{figure}
Space-temporal warping enables time to flow differently at different locations in the video (figure~\ref{fig:timefront}).
\begin{wrapfigure}[13]{O}{0.3\linewidth}
\vspace{-2ex}
- \includegraphics[width=0.8\linewidth]{images/timefront.png}
+ \includegraphics[width=0.8\linewidth]{timefront.png}
\caption{Temporal bands for Timefront}
\label{fig:timefront}
\end{wrapfigure}
\subsection{Title}%
\label{sub:title}
-The \textit{Titler} allows you to add text from within Cinelerra GG. The titler has standard options for font, size, and style plus many options as described next (figure~\ref{fig:title01}).
+The \textit{Titler} allows you to add text from within \CGG{}. The titler has standard options for font, size, and style plus many options as described next (figure~\ref{fig:title01}).
\begin{description}
\item[Justify] justifies the text relative to the entire frame. Once justified, the $X$ and $Y\, offset$ is applied. This allows text to be justified while at the same time letting you push it within the title safe region.
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.9\linewidth]{images/title01.png}
+ \includegraphics[width=0.9\linewidth]{title01.png}
\caption{GUI of the Title plugin}
\label{fig:title01}
\end{figure}
The titler supports mainly \textit{TTF}, true type fonts. It supports others but TTF are the most reliable. To add true type fonts, copy the \texttt{.TTF} files to the fonts directory. In that directory run
\vspace{1ex}
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
# /usr/lib/cinelerra/fonts
ttmkfdir && mv fonts.scale fonts.dir
\end{lstlisting}
-and restart Cinelerra. The new fonts should appear. The usage of ttmkfdir changes frequently so this technique might not work.
+and restart \CGG{}. The new fonts should appear. The usage of ttmkfdir changes frequently so this technique might not work.
If the video is displayed on a consumer TV, the outer border is going to be cropped by $5\%$ on each side. To avoid text which is too close to the edge looking bad, you may want to enable the \textit{title-safe} tool in the compositor window. The text should not cross the inner rectangle.
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.3\linewidth]{images/title02.png}
+ \includegraphics[width=0.3\linewidth]{title02.png}
\caption{Pulldown Attributes}
\label{fig:title02}
\end{figure}
\end{longtable}
\end{center}
-These attributes stay in effect until you change them or reset them. Additional cpu time is needed for the \textit{blink} attribute because it requires redrawing every frame and for the background option described below. Note that some Title window controls can not be set, such as Justify and Outline color. The lines below are examples for testing purposes. The accompanying screenshot displays the corresponding Cinelerra output.
+These attributes stay in effect until you change them or reset them. Additional cpu time is needed for the \textit{blink} attribute because it requires redrawing every frame and for the background option described below. Note that some Title window controls can not be set, such as Justify and Outline color. The lines below are examples for testing purposes. The accompanying screenshot displays the corresponding \CGG{} output.
\vspace{1ex} Examples of Title line keyins:
Figure~\ref{fig:title03}.
\vspace{1ex}
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
<size 15>Buddy, the <color red><bold 1>bad dog</bold><color white> ate my homework !<png /tmp/buddy.png><ul 1><size +>There are<ul 0><size +>2<sup 1>10<sup 0>cats <font Action man (misc)>to chase?
\end{lstlisting}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.9\linewidth]{images/title03.png}
+ \includegraphics[width=0.9\linewidth]{title03.png}
\caption{Final result of the exemple}
\label{fig:title03}
\end{figure}
\paragraph{Special Characters (< > / \textbackslash \#)} Besides the previously described <, >, and / characters, there are two special characters: backslash “\textbackslash”, and the pound sign “\#”. The backslash character is used for two things. With the advent of the attribute name and value, your line may become quite long so you can use “\textbackslash” followed by the carriage return to continue on the next line as if it is just a single line. It also can be used to designate that the following character does not represent the beginning of an attribute. For example, if you want to use the opening angle character “<“ as a title character, precede it with the backslash character. The pound sign, “\#”, designates the whole line as a comment or if in the middle of the line, then the rest of the line is a comment (this includes the carriage return).
\begin{description}
- \item[Background] in this box you can keyin the name of a file of the type that Cinelerra accepts and use that file as a background for your Title characters. This will be seen in the compositor window on top of the video that is loaded in the main track canvas. Besides typing in the filename, you must also check the checkbox. This makes it easy to turn it \textit{On} and \textit{Off} to see what it looks like. Next to the background box is a \textit{Loop} checkbox. If the background file takes less time than the main track canvas video to run, you can turn on the loop checkbox so that it runs over and over again to match the time size of your video.
+ \item[Background] in this box you can keyin the name of a file of the type that \CGG{} accepts and use that file as a background for your Title characters. This will be seen in the compositor window on top of the video that is loaded in the main track canvas. Besides typing in the filename, you must also check the checkbox. This makes it easy to turn it \textit{On} and \textit{Off} to see what it looks like. Next to the background box is a \textit{Loop} checkbox. If the background file takes less time than the main track canvas video to run, you can turn on the loop checkbox so that it runs over and over again to match the time size of your video.
\item[Stroker] to add \textit{pen strokes} to the text letters, adjust the stroke width numerically. This looks particularly nice on certain fonts and with a negative adjustment of the \textit{Drop shadow}.
\item[Unicode Insertion] if you want to enter a special character like the mathematical \textit{summation} symbol, you can use the unicode equivalent to do so. Press Ctrl-Shift-U followed by $2022$ and a carriage return is an example of the bullet. Refer to section \hyperref[sec:textbox_non_std_character_unicode]{17.5} for details.
\item[Popup Helper] put your cursor where you want to add an attribute, then right mouse will bring up a list of the available attributes for you to choose, along with a submenu to choose from. The program will insert that attribute for you and all you have to add is a value when required! (see figure~\ref{fig:title02}).
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.5\linewidth]{images/title04.png}
+ \includegraphics[width=0.6\linewidth]{title04.png}
\caption{Screencast showing the Color Picker menu.}
\label{fig:title04}
\end{figure}
\subsubsection*{Font Addition / Font Subtraction}%
\label{ssub:font_addition_subtraction}
-Some of the system fonts are automatically included in the set of fonts being used by Cinelerra. The easiest way to add additional fonts for the Title plugin's set, is to use ones available in specific directories on your computer as long as they have a \texttt{fonts.scale} file already set up. You can run \texttt{mkfontscale} to create this file within that directory. In order to include a specific directory you set an environment variable before starting Cinelerra which stays in effect until it is unset or until the next reboot. Below is the method and an example.
+Some of the system fonts are automatically included in the set of fonts being used by \CGG{}. The easiest way to add additional fonts for the Title plugin's set, is to use ones available in specific directories on your computer as long as they have a \texttt{fonts.scale} file already set up. You can run \texttt{mkfontscale} to create this file within that directory. In order to include a specific directory you set an environment variable before starting \CGG{} which stays in effect until it is unset or until the next reboot. Below is the method and an example.
\vspace{1ex}
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
export BC_FONT_PATH=<colon-separated-search-path-for-fonts>
export BC_FONT_PATH=/usr/share/fonts
\end{lstlisting}
-The current set of fonts in Cinelerra's directory will be automatically included and will be the default set if this environment variable is not set. Keep in mind that if you add a lot of fonts, it will considerably slow down the startup every time you bring up the Title plugin.
+The current set of fonts in \CGG{}'s directory will be automatically included and will be the default set if this environment variable is not set. Keep in mind that if you add a lot of fonts, it will considerably slow down the startup every time you bring up the Title plugin.
-If you want to only have a limited number of fonts set up, you can manipulate the Cinelerra directory directly at \texttt{<cinelerra\_install\_path> /bin/plug\-ins/fonts}.
-Here you will find the default set of fonts that come with the install. Copy any other fonts you would like to include here with read permission, delete any fonts you do not want to have, then execute \texttt{mkfontscale} which creates the file \texttt{fonts.scale} that Cinelerra will read. However, the next time you install a new version of Cinelerra GG, your changes will be written over so you will have to make sure to save them elsewhere and then re-establish.
+If you want to only have a limited number of fonts set up, you can manipulate the \CGG{} directory directly at \texttt{<cinelerra\_install\_path> /bin/plug\-ins/fonts}.
+Here you will find the default set of fonts that come with the install. Copy any other fonts you would like to include here with read permission, delete any fonts you do not want to have, then execute \texttt{mkfontscale} which creates the file \texttt{fonts.scale} that \CGG{} will read. However, the next time you install a new version of \CGG{}, your changes will be written over so you will have to make sure to save them elsewhere and then re-establish.
-If you have problems with a specific font or set of fonts, there is a debug option available to determine which font is an issue. When starting Cinelerra, you should set up the variable:
+If you have problems with a specific font or set of fonts, there is a debug option available to determine which font is an issue. When starting \CGG{}, you should set up the variable:
\vspace{1ex}
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
export BC_FONT_DEBUG=1 (default is 0 for no debug)
unset BC_FONT_DEBUG (to remove debug messages)
\end{lstlisting}
-Then start Cinelerra from a terminal window to see the fonts being loaded and previewed in the Titler. This should point out any issues. Another debug methodology is to remove all fonts from being used and subsequently add in the ones that you want. For example:
+Then start \CGG{} from a terminal window to see the fonts being loaded and previewed in the Titler. This should point out any issues. Another debug methodology is to remove all fonts from being used and subsequently add in the ones that you want. For example:
\vspace{1ex}
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
export BC_FONT_PATH=: #(the : "colon" removes all automatic system and Cinelerra fonts)
export BC_FONT_PATH=:/usr/share/fonts #(remove all fonts and then add /usr/shar/fonts)
\end{lstlisting}
One last item of information about fonts that may lead to some confusion. The checkbox for Bold and Italic will occasionally be ghosted out if no bold or italic version of the selected font is available. This is no guarantee, but currently as good as it can get due to inconsistency in the creation of fonts. It is mostly just a hint. If boxes are checkmarked, but ghosted, you can not uncheck until you change to a font that does not ghost out the boxes. If you use the popup helper with the boxes checked, and attempt to keyin a font that does not have the bold/italic attribute as checked, the font will be considered illegal.
-Text: chars is output and updated to indicate the number of characters already used. The only limit to the number of characters based on a count of single $8\, bit$ characters is the available resources on the user computer available for Cinelerra use. Keep in mind that unicode or other special characters may consist of $2$ to $4$ $8\,bit$ bytes. Also, newlines are a character and any of the attributes you use count in the total. There is now a horizontal scroll bar as well as the vertical one in the textbox and they only appear when there are more lines or characters that can fit in the original sized textbox.
+Text: chars is output and updated to indicate the number of characters already used. The only limit to the number of characters based on a count of single $8\, bit$ characters is the available resources on the user computer available for \CGG{} use. Keep in mind that unicode or other special characters may consist of $2$ to $4$ $8\,bit$ bytes. Also, newlines are a character and any of the attributes you use count in the total. There is now a horizontal scroll bar as well as the vertical one in the textbox and they only appear when there are more lines or characters that can fit in the original sized textbox.
\subsubsection*{Kerning}%
\label{ssub:kerning}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.5\linewidth]{images/title05.png}
+ \includegraphics[width=0.5\linewidth]{title05.png}
\caption{Kerning in action}
\label{fig:title05}
\end{figure}
\subsection{Tracer}%
\label{sub:tracer}
-Tracer creates an outline around an object after a few points are designated, so it traces the object. Its operation recalls Gimp's \textit{magic wand}. You can then Fill the alpha channel with a mask, like with a gradient or another object on another track or Invert that fill. Although it works best for still images or objects that stay in the same place on a video like a logo, you can also add keyframes. To limit the mis-tracking that occurs when working on a moving object, we can increase the number of points so that the tracking is more accurate and relies on a solid foundation. Rather than \textit{points} as in a mask, tracer is based on \textit{edges} to form an outline (figure~\ref{fig:tracer-01}). Frequently it will be desirable to use either RGB or YUV as the color model without the -A for Alpha.
+Tracer creates an outline around an object after a few points are designated, so it traces the object. Its operates in a similar manner to that of Gimp's \textit{magic wand}. You can then Fill the alpha channel with a mask, like with a gradient or another object on another track or Invert that fill. Although it works best for still images or objects that stay in the same place on a video like a logo, you can also add keyframes. To limit the mis-tracking that occurs when working on a moving object, we can increase the number of points so that the tracking is more accurate and relies on a solid foundation. Rather than \textit{points} as in a mask, tracer is based on \textit{edges} to form an outline (figure~\ref{fig:tracer-01}). Frequently it will be desirable to use either RGB or YUV as the color model without the -A for Alpha.
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.55\linewidth]{images/tracer-01.png}
+ \includegraphics[width=0.55\linewidth]{tracer-01.png}
\caption{Gui for Tracer plugin}
\label{fig:tracer-01}
\end{figure}
\item[Del] to delete the highlighted point.
\item[X, Y] are the point’s $x/y$ coordinate.
\item[Invert] to change the mask to outside.
- \item[Feather] to sort of blur the edges (inward and outward). Feather influences the softness of the edge. The more Feather is set, the softer the edge becomes.
+ \item[Feather] to sort of blur the edges (inward and outward). Feather influences the softness of the edge. The higher the number Feather is set to, the softer the edges become.
\item[Radius] for varying the size a little. Radius extends the area further in or out to cover more or less area.
\item[Drag] to enable or disable moving.
\item[Draw] to draw the outline for visual.
\item[Fill] to black out the object (no alpha); figure~\ref{fig:tracer-02}.
- \item[Mouse wheel] rotate the outline, centered on cursor. Note that rotates the outline around the nearest point. Normally the scroll is slow to be more precise. If you make a fast scroll you have an acceleration that allows you to make complete rotations in a short time.
+ \item[Mouse wheel] rotate the outline, centered on cursor. Note that this rotates the outline around the nearest point. The slower you scroll, the more precise the the result. If you scroll faster, an accelerator kicks in that allows you to make complete rotations more quickly.
\item[Mouse wheel + shift] scale the outline, centered on cursor.
\end{description}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.7\linewidth]{images/tracer-02.png}
+ \includegraphics[width=0.7\linewidth]{tracer-02.png}
\caption{Rug in the top picture is traced in order to black it out or replace later}
\label{fig:tracer-02}
\end{figure}
\subsection{Videoscope}%
\label{sub:videoscope}
-Videoscope summarizes intensity and color on a calibrated display. The Videoscope can be used in conjunction with other Cinelerra plugins such as \textit{Color 3 Way}, \textit{YUV}, \textit{Brightness}, \textit{Color Balance} or \textit{Histogram} to accurately correct video for contrast, clarity, conformance (to normalize various videos shot under different light settings), or for cinematic purposes. The human eye is not specialized to match precise level of light and color, but Videoscope is. Videoscope contains three displays: the waveform scope and the vectorscope, plus the histograms (figure~\ref{fig:videoscope01}).
+Videoscope summarizes intensity and color on a calibrated display. The Videoscope can be used in conjunction with other \CGG{} plugins such as \textit{Color 3 Way}, \textit{YUV}, \textit{Brightness}, \textit{Color Balance} or \textit{Histogram} to accurately correct video for contrast, clarity, conformance (to normalize various videos shot under different light settings), or for cinematic purposes. The human eye is not specialized to match precise level of light and color, but Videoscope is. Videoscope contains three displays: the waveform scope and the vectorscope, plus the histograms (figure~\ref{fig:videoscope01}).
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.8\linewidth]{images/videoscope01.png}
+ \includegraphics[width=0.8\linewidth]{videoscope01.png}
\caption{GUI of the Videoscope. You see Histogram, RGB Parade and Vectorscope}
\label{fig:videoscope01}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.9\linewidth]{images/videoscope02.png}
+ \includegraphics[width=0.9\linewidth]{videoscope02.png}
\caption{Colortest 75\% with RGB Parade (left) and Waveform (right)}
\label{fig:videoscope02}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.7\linewidth]{images/videoscope03.png}
+ \includegraphics[width=0.7\linewidth]{videoscope03.png}
\caption{Example of waveform}
\label{fig:videoscope03}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.9\linewidth]{images/videoscope04.png}
+ \includegraphics[width=0.9\linewidth]{videoscope04.png}
\caption{Balancing a yellow dominace tint}
\label{fig:videoscope04}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.7\linewidth]{images/yuvshift.png}
+ \includegraphics[width=0.7\linewidth]{yuvshift.png}
\caption{Before and after YUVShift adjusting}
\label{fig:yuvshift}
\end{figure}
\begin{figure}[hbtp]
\centering
- \includegraphics[width=0.8\linewidth]{images/zoom.png}
+ \includegraphics[width=0.8\linewidth]{zoom.png}
\caption{For clarity of presentation only 3 fields are shown}
\label{fig:zoom}
\end{figure}
+\section{CUDA plugins}%
+\label{sec:cuda_plugins}
+\settocdepth{section}
+
+Only for Nvidia GPU and Cuda SDK
+
+\subsection{Mandelbrot}%
+\label{sub:mandelbrot}
+
+Produce fractal figures (figure~\ref{fig:mandelbrot}). Use case:
+\begin{enumerate}
+ \item add the Mandelbrot Cuda video effect to the timeline
+ \item you must enable Drag in the plugin popup menu
+ \item drag the mouse with the RMB down and you will see the fractal change
+ \item enable "Generate keyframes while tweaking" and move to another spot on the timeline and RMB drag again
+ \item so now when you play the video from the beginning because you have keyframes, the fractal will be animated between keyframes.
+\end{enumerate}
+
+\begin{figure}[hbtp]
+ \centering
+ \includegraphics[width=0.9\linewidth]{mandelbrot.png}
+ \caption{Mandelbrot Cuda plugin}
+ \label{fig:mandelbrot}
+\end{figure}
+
+\subsection{N\_Body}%
+\label{sub:n_body}
+
+Produce animated particles (figure~\ref{fig:n_body}).
+
+\begin{figure}[hbtp]
+ \centering
+ \includegraphics[width=1.0\linewidth]{n_body.png}
+ \caption{N\_Body Cuda plugin}
+ \label{fig:n_body}
+\end{figure}
+
\section{OpenCV plugins}%
\label{sec:opencv_plugins}
\settocdepth{section}
\item internally the colormodel is converted to greyscale, which means the color information is not used
\end{enumerate}
-Because of the build size of opencv, it is not normally included in the thirdparty directory. Building opencv adds a lot of storage demand ($4\,GB$) to the Cinelerra build tree, and the opencv compile time is significant. For these reasons, \textit{findobject} is not normally built. You can however invoke a build which adds findobject to the Cinelerra plugin library. Building findobject will configure and build opencv into the thirdparty library build area if needed (it does not rebuild if already done). System builds are possible, but the system compatibility of the newer opencv interfaces can vary between distros. The opencv interface is rapidly changing; we recommend the static library build and link to avoid problems.
+Because of the build size of opencv, it is not normally included in the thirdparty directory. Building opencv adds a lot of storage demand ($4\,GB$) to the \CGG{} build tree, and the opencv compile time is significant. For these reasons, \textit{findobject} is not normally built. You can however invoke a build which adds findobject to the \CGG{} plugin library. Building findobject will configure and build opencv into the thirdparty library build area if needed (it does not rebuild if already done). System builds are possible, but the system compatibility of the newer opencv interfaces can vary between distros. The opencv interface is rapidly changing; we recommend the static library build and link to avoid problems.
\subsection{How to Build OpenCV Plugins}%
\label{sub:how_build_opencv_plugins}
To build findobject and the other plugins using opencv, access the src using git:
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
git clone -depth 1 "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5
\end{lstlisting}
then configure the build, but add the \texttt{-{}-with-opencv} configure parameter.
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
cd <path>/cinelerra-5.1
./autogen.sh
./configure <add std params, eg: --with-single-user> --with-findobect=sta
To get opencv built in the easiest way possible (need internet access because builds directly from the opencv github but this changes wildly):
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
./configure <params> --with-opencv=sta,git
\end{lstlisting}
The OpenCV plugins are built only in the 64-bit tarball builds, both static and dynamic. However, due to size these plugins are not included with pkgs. But it is relatively easy to add the current 6 plugins for your distro via a simple procedure of copying the plugins from the tarball to the cin5 install plugin path. They are:
-\begin{lstlisting}[language=Bash,numbers=none]
+\begin{lstlisting}[style=sh]
cin/plugins/opencv/findobj.plugin
cin/plugins/opencv/flowobj.plugin
cin/plugins/opencv/gaborobj.plugin
\item \texttt{cd} that-directory;
\item \texttt{tar -xf} location-of-the-tarball-you-downloaded;
\item \texttt{cp plugins/*obj.plugin <see below for your location>/.} (note the period on the end!)
- \item Start Cinelerra and look for the six plugins in Video Effects;
+ \item Start \CGG{} and look for the six plugins in Video Effects;
\item To reverse this, simply delete the six plugin files (eg.
\texttt{rm /usr/lib*/cin*/*obj.plugin}).
\item [Don’t Calculate] Do nothing
\end{description}
-The Cinelerra plugin has several additional features for ease of use and more flexibility. A description of parameters is outlined below.
+The \CGG{} plugin has several additional features for ease of use and more flexibility. A description of parameters is outlined below.
\begin{description}
\item[Mode:]
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.9\linewidth]{images/findobj.png}
+ \includegraphics[width=0.9\linewidth]{findobj.png}
\caption{Timeline; control window and compositor for FindObj}
\label{fig:findobj}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/opencv.png}
+ \includegraphics[width=0.8\linewidth]{opencv.png}
\caption{FlowObj; GaborObj (before and after) and PuzzleObj}
\label{fig:opencv}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/stylizeobj01.png}
+ \includegraphics[width=0.6\linewidth]{stylizeobj01.png}
\caption{Pulldown of Stylize mode on the original image}
\label{fig:stylizeobj01}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.95\linewidth]{images/stylize.png}
+ \includegraphics[width=0.95\linewidth]{stylize.png}
\caption{Clockwise: Edge Smooth and Recursive; Detail Enhance; Stylization; Color and Pencil Sketch}
\label{fig:stylize}
\end{figure}
\section[FFmpeg Audio and Video Plugins]{FFmpeg Audio and Video Plugins\protect\footnote{credit to WPfilmmaker for the Ffmpeg info description lines taken from his contributed pdf}}%
\label{sec:ffmpeg_audio_video_plugins}
-Cinelerra GG Infinity currently comes with more than $140$ of the video plugins and $55$ of the audio plugins developed by the FFmpeg project {\small \url{www.ffmpeg.org}}. These plugins do not have a GUI with buttons like the rest of plugins, therefore to change settings it is necessary to change the variables by hand by highlighting the \textit{option}, typing a value in the \textit{Range} box, and then hitting the \textit{Apply} button. Many of these plugins provide tooltips at the bottom right corner of the window when the option is highlighted. A \textit{slider} bar and a \textit{dial} for numerical values can be used to easily vary the values which take effect immediately.
+\CGGI{} currently comes with more than $140$ of the video plugins and $55$ of the audio plugins developed by the FFmpeg project {\small \url{www.ffmpeg.org}}. These plugins do not have a GUI with buttons like the rest of plugins, therefore to change settings it is necessary to change the variables by hand by highlighting the \textit{option}, typing a value in the \textit{Range} box, and then hitting the \textit{Apply} button. Many of these plugins provide tooltips at the bottom right corner of the window when the option is highlighted. A \textit{slider} bar and a \textit{dial} for numerical values can be used to easily vary the values which take effect immediately.
Figure~\ref{fig:ffchromakey} shows what an FFmpeg video plugin looks like; example is \texttt{F\_chromakey}.
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/ffchromakey.png}
+ \includegraphics[width=0.6\linewidth]{ffchromakey.png}
\caption{GUI for FFmpeg plugins}
\label{fig:ffchromakey}
\end{figure}
Currently FFmpeg audio and video plugins that do not have a personalized icon use one of the default icons as shown below.
-Default Audio Icon: \quad \includegraphics[height=\baselineskip]{images/ffaudio.png}
-\quad Default Video Icon: \quad \includegraphics[height=\baselineskip]{images/ffvideo.png}
+Default Audio Icon: \quad \includegraphics[height=\baselineskip]{ffaudio.png}
+\quad Default Video Icon: \quad \includegraphics[height=\baselineskip]{ffvideo.png}
If you want to replace the icon with a more descriptive picture, see a previous section on Updatable Icon Image Support and Details on where to put Plugin Icons.
Simply drag and drop the plugin on the timeline. To enter the settings option, once you have added the plugin to the timeline, right click on the colored bar that appears below the timeline track of the plugin and highlight the \textit{show} option. Alternatively, you can left click the \textit{magnifying glass} icon that appears on the right side of the colored bar. For the audio plugins, if the plugin is not working at all, you will hear a trouble tone waveform to indicate that. If the value is unspecified, it uses default. If you specify the default, the value becomes unspecified which means that nothing gets sent into the program.
-Some of the ffmpeg plugins are not usable with Cinelerra GG Infinity due to input/output requirements. Also, some do not come with legal initial supplied values for the parameters (ffmpeg works on filtergraph, while Cinelerra works on stack). These plugins get tested at least once and if they crash, cause problems, or are deemed unusable, they are commented out in the \texttt{plugin.opts} file in the Cinelerra ffmpeg subdirectory. Generally they are not retested so if the ffmpeg software changes them making them usable, they will still not be accessible until the \texttt{plugin.opts} file is changed. You can easily retest these, by temporarily uncommenting the copy of the \texttt{plugin.opts} file in the \texttt{bin} subdirectory and using \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Interface tab $\rightarrow$ Reload plugin index}
+Some of the ffmpeg plugins are not usable with \CGGI{} due to input/output requirements. Also, some do not come with legal initial supplied values for the parameters (ffmpeg works on filtergraph, while \CGG{} works on stack). These plugins get tested at least once and if they crash, cause problems, or are deemed unusable, they are commented out in the \texttt{plugin.opts} file in the \CGG{} ffmpeg subdirectory. Generally they are not retested so if the ffmpeg software changes them making them usable, they will still not be accessible until the \texttt{plugin.opts} file is changed. You can easily retest these, by temporarily uncommenting the copy of the \texttt{plugin.opts} file in the \texttt{bin} subdirectory and using \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Interface tab $\rightarrow$ Reload plugin index}
FFmpeg’s plugin guide is at the link:
\textbf{F\_colorkey:} Turns a certain color into transparency. Operates on RGB colors.\\
\textbf{F\_colorlevels:} Adjusts the color levels.\\
\textbf{F\_colormatrix:} Converts color matrix.\\
+\textbf{F\_colorspace:} Converts color space.\\
\textbf{F\_cover\_rect:} Find and cover a user specified object.\\
\textbf{F\_crop:} Crops the input video.\\
\textbf{F\_cropdetect:} Auto-detect crop size.\\
projects / goodguy / cin-manual-latex.git / blobdiff