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}.
-\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}
\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 Cinelerra. 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 Cinelerra. 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 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 \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.8\linewidth]{images/stylizeobj01.png}
+ \includegraphics[width=0.6\linewidth]{images/stylizeobj01.png}
\caption{Pulldown of Stylize mode on the original image}
\label{fig:stylizeobj01}
\end{figure}
\chapter{Translations}%
\label{cha:translations}
-There are several \textit{po} files for various languages to make Cinelerra more usable for non-English countries. A program, \textit{xlat.C}, assists in providing several variations of text files that can be used in order to allow anyone to help make meaningful translations. All of the \textit{po} files are located in Cinelerra’s \texttt{/po} subdirectory. There are 3 different ways to proceed described below.
+There are several \textit{po} files for various languages to make Cinelerra more usable for non-English
+countries. These are listed below along with the po file name with the translations, the frequency
+of updates, and date of last update as of this writing.
+
+\begin{tabular}{llll}
+\hline
+ English& cin.po& Baseline &(en\_US) \\
+ French& fr.po& Updated often& Last update 2019 May\\
+ German& de.po& Updated often& Last update 2019 December\\
+ Russian& ru.po& Updated often& Last update 2019 October\\
+ Spanish& es.po& Updated often& Last update 2020 February\\
+\\
+ Basque& eu.po& From CV with Google Translate & Last update 2016 October\\
+ Italian&it.po& From CV with Google Translate & Last update 2016 October\\
+ Norwegian& nb.po& From CV with Google Translate & Last update 2016 October\\
+ Portuguese& pt.po& From CV with Google Translate& Last update 2016 October \\
+ Slovenian& sl.po & From CV with Google Translate& Last update 2016 October \\
+\\
+ Chinese& zh.po& Only Google Translate & 2016 October\\
+ Greek& el.po& Only Google Translate & 2016 October\\
+ Hindi& hi,po& Only Google Translate & 2016 October\\
+ Japanese& ja.po& Only Google Translate & 2016 October \\
+ Korean& ko.po& Only Google Translate & 2016 October \\
+ Ukrainian& uk.po & Only Google Translate & 2016 October \\
+ Vietnamese& vi.po& Only Google Translate & 2016 October \\
+\hline
+\end{tabular}
+
+A program, \textit{xlat.C}, assists in providing several variations of text files that can be used in order to allow anyone to help make meaningful translations. All of the \textit{po} files are located in Cinelerra’s \texttt{/po} subdirectory. There are 3 different ways to proceed described below.
Because Cinelerra frequently is changing, it is a good idea to start by building a new \texttt{cin.po} file which contains the latest messages/words in English to be translated, along with a comment line of the routine name and line number. To create this, run the following lines from a window:
-\begin{lstlisting}[language=bash,numbers=none]
+\begin{lstlisting}[numbers=none]
cd /{your top level cinelerra directory}
./po/xlat.sh > /tmp/cin.po
\end{lstlisting}
To use the msgmerge command after creating a new cin.po as suggested previously:
-\begin{lstlisting}[language=bash,numbers=none]
+\begin{lstlisting}[numbers=none]
cd /{your top level cinelerra directory}
./po/xlat.sh > /tmp/cin.po # use /tmp as a temporary place
cp /{your cinelerra directory}/po/xx.po /tmp/xx.po # substitute your language for x
To use the \textit{xlat.C} program, first compile it with \texttt{c++ xlat.C}. You can see the usage help here:
-\begin{lstlisting}[language=bash,numbers=none]
+\begin{lstlisting}[numbers=none]
./a.out
list csv ./a.out csv < data.csv > data.po
list po ./a.out po < data.po > data.csv
The xlat command line parameters specify a new cin.po template, usually created with xlat.sh, and a list of key/value files which are used to build a mapping for the desired translation. The mapping files are added to the mapping in the order they appear on the command line, and any existing key is replaced with the newest definition; so typically the newest key/value data is last in the command parameters.
Once the mapping is built, the first parameter which is the new po template is scanned and the keys it contains are used to find the latest mapping in the key/value files. The new value replaces the existing value in the template. For example, to overlay a new map onto an existing po using the Spanish es.po file and where cin.po represents the latest english words:
-\begin{lstlisting}[language=bash,numbers=none]
+\begin{lstlisting}[numbers=none]
c++ xlat.C
./a.out po < es.po > /tmp/es.csv
./a.out po < cin.po > /tmp/cin.csv
projects / goodguy / cin-manual-latex.git / commitdiff