\item The insertion point or selected region must start inside the other effects.
\end{itemize}
+Before going into further detail about how to use \textit{Shared effects}, an easier
+alternative method of application which is especially useful for Audio tracks is
+available. In this method, all you have to do is use the \textit{Audio} pulldown and
+choose \textit{Attach effect}, highlight the effect you would like and make sure the
+default of \textit{Attach single standalone and share others} is checked on. It will
+automatically be a "Shared Effect" on all audio tracks (be sure to disarm any audio
+tracks that you do not want to have the effect shared on). This method also works for
+Video tracks using the \textit{Video} pulldown choice of \textit{Attach effect}.
+
In the case of a shared track, there must be another track on the timeline of the same type as the track you are applying an effect to. If you right clicked on a video track to attach an effect, there will not be anything in the shared tracks column if no other video track exists. The same applies equally to audio tracks in that another audio track must exist. Shared tracks are often used as layers for titles, curves and keyframes.
If shared effects or shared tracks are available, they appear in the shared effects and shared tracks columns when you used the \textit{Attach effect} option (RMB on a track). When the green colored checkmark is clicked OK, anything highlighted in the column is attached under the current track.
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})
+\begin{figure}[htpb]
+ \centering
+ \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}
+
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:
/tmp/cinelerra-5.1/bin/lv2ui http://calf.sourceforge.net/plugins/Flanger
\end{lstlisting}
-\begin{figure}[htpb]
- \centering
- \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}
\section[Video Effects --- Native]{Video Effects -- Native}%
\label{sec:video_effects_native}
\label{fig:perspective01}
\end{figure}
+Just a side note about the possibility of ending up with a divide by 0 case when manipulating
+the endpoints. Sometimes this results in a single frame anomaly but you can workaround this
+by setting the X value for the middle keyframe of a series to just a little more than 0,
+such as .01 so that dividing by 0 is avoided. The actual cause of the problem is that the
+interpolated X1..X4 auto coordinates used by perspective eventually have x1==x2, x3==x4, so
+that all points x are scaled by zero. Another solution is to tweak the frame count to an even
+number, so that the center is not over the point where x1==x2, x3==x4, or perturb the midpoint
+position a little so that the answers are not exactly zero.
+
\subsection{Polar}%
\label{sub:polar}
projects / goodguy / cin-manual-latex.git / blobdiff