From af000e989e1b806fd27864622011a9401ad9d90b Mon Sep 17 00:00:00 2001 From: Good Guy Date: Wed, 17 Mar 2021 12:15:18 -0600 Subject: [PATCH] add Andrea FAQ section and other cleanup --- parts/Advanced.tex | 20 -------------------- parts/Developer.tex | 4 ++++ parts/Real-World.tex | 43 +++++++++++++++++++++++++++++++++++++++++++ parts/Rendering.tex | 31 +++++++++++++------------------ 4 files changed, 60 insertions(+), 38 deletions(-) diff --git a/parts/Advanced.tex b/parts/Advanced.tex index 0c84fd4..87eecea 100644 --- a/parts/Advanced.tex +++ b/parts/Advanced.tex @@ -290,9 +290,6 @@ off even though it gives you the option to do so. These include: Instead just use the X to dismiss the warning. \end{enumerate} -Workaround cases for the alpha channel not working as intended when using an EDL inserted as a reference -is described in \ref{sub:nested_clips}. - Here is a step by step example of how you can use \textit{File by Reference}: \begin{enumerate} @@ -634,23 +631,6 @@ way they did originally with respect to the audio waveforms. This is simply a re video track which is independent from the redrawing of the audio tracks. The playback is still synchronized. \end{itemize} -Workaround cases for the alpha channel not working as intended when using an EDL inserted as a reference -or when an EDL is nested, is described here. - -\paragraph{Case 1 using the Projector on the EDL within a Master Project:} follow these next steps. -\begin{itemize} - \item Open your EDL with \textit{Open EDL} by using the middle mouse button on the Nested edit on its track. - \item In this nested EDL, insert a new Video track below the last video track. - \item Add the Alpha plugin to the new Video track for the entire length of the nested EDL. - \item Change the value of the Alpha to 0.00. - \item Close the EDL. -\end{itemize} This solves the alpha channel not working as expected and the Master Project now looks correct. - -\paragraph{Case 2 using FadeIn/Out with autos:} -In the Master Project for the Videeo track containing the nested EDL, in its Patchbay change -the \textit{Overlay Mode} from \textit{Normal} to \textit{PorterDuff->SrcOver}. - - \paragraph{Usage Examples of Nested Clips} \begin{description} diff --git a/parts/Developer.tex b/parts/Developer.tex index 6fc9f00..f199694 100644 --- a/parts/Developer.tex +++ b/parts/Developer.tex @@ -483,6 +483,10 @@ The best way to compile and run valgrind is to run the developer static build. T \texttt{CFLAGS=-ggdb make -j8 rebuild\_all} \end{enumerate} +If you frequently make mods and changes in \CGG{} or the thirdparty libraries, do not depend on those +compiled versions to have the headers updated; so be sure to fully rebuild as shown in the previous 2 +steps before running valgrind or you will get false errors. + Now your \CGG{} obj has all of the debug stuff. Next run valgrind as root for the most useful results: \hspace{2em}\texttt{cd /path/cinelerra-5.1/cinelerra} diff --git a/parts/Real-World.tex b/parts/Real-World.tex index c89d219..2ac8091 100644 --- a/parts/Real-World.tex +++ b/parts/Real-World.tex @@ -224,3 +224,46 @@ To render, do not forget to uncheck the P (proxy) button in the main program win \paragraph{Note:} If our files have Jam-syncing timecodes, we can speed up the workflow (steps 4 - 15) with the simple command : \texttt{Tracks $\rightarrow$ Align Timecodes}. More info can be found in \nameref{sub:align_timecodes}. + +\chapter{FAQ, Known Problems and Workarounds}% +\label{cha:faq_problems_workarounds} +\index{workarounds} + +There are a few known problems that have not yet been fixed for which there are some workarounds presented here. + +\paragraph{Workaround for the \textit{alpha channel not working as intended when using an EDL} inserted as a reference or when an EDL is nested.} +Using the Projector on the EDL within a Master Project follow these next steps. +\begin{itemize} + \item Open your EDL with \textit{Open EDL} by using the MMB (Middle Mouse Button) on the Nested edit on its track. + \item In this nested EDL, insert a new Video track below the last video track. + \item Add the Alpha plugin to the new Video track for the entire length of the nested EDL. + \item Change the value of the Alpha to 0.00. The Alpha Plugin may be disabled or left enabled. + \item Close the EDL. +\end{itemize} This solves the alpha channel not working as expected and the Master Project now looks correct. + +\paragraph{Workaround for using a transition, like Dissolve, between 2 edits with the plugin Motion51.} +In this case, the Motion51 plugin and the Dissolve transition are not seen during the transition phase +and is stopped at the cut point between 2 edits. +The left edit's plugin should be in effect until the end of that clip and should include the +dissolve. Instead, there is a jump inside the dissolve, as if the plugin does not exist. There are +2 possible workarounds. For example, extend the Motion51 plugin to cover both clips rather than +having a separate plugin for each clip. Or another workaround is to use two tracks and have the +plugin cover the cut point and use a Fade auto instead of the Dissolve transition. + +\paragraph{The Fade auto in certain circumstances produces an unwanted black flash.} +When you insert an effect on an empty track the fade fades as if it were on a black background; +it interprets the alpha as black where there is transparency, which is what produces the fade. +So the problem in the case of text is that the letters appear as a black flash briefly in the first +few frames, then goes back to transparent, then the fade starts normally with the white color. +To avoid the unwanted effect produced by the fade over black (because there is no content) leave +the fade in/out of the effect at 0 and use the fade line to perform the intended results to +avoid the problem with the alpha channel. The same problem occurs when using transparent PNG +images with fade video transitions and can be resolved in the same manner. +However this workaround can be quite tedious and complicated if you want to fade many snippets of text +and transparent PNGs on the same track, with always the same video transition filter set to the same +duration. + +Just a side note here. Fade in/out in the Title plugin works fine if there is a clip/image above +the plugin in the same track without an alpha channel but not if there is no clip/image. +And the Transition effect works fine when there is a transition between two clips/images without +an alpha channel. \ No newline at end of file diff --git a/parts/Rendering.tex b/parts/Rendering.tex index b65fffd..d4428c6 100644 --- a/parts/Rendering.tex +++ b/parts/Rendering.tex @@ -679,9 +679,9 @@ Batch Rendering as implemented in \CGG{} is considered to be more of an advanced feature and careful usage is advised. It automates the rendering of audio/video files in that you can establish a set of job parameters, save them, and use them -repeatedly. It also allows for \CGG{} to be run by external -programs, with no need for the user to manually interact with the -user interface (figure~\ref{fig:batch01}). +repeatedly (figure~\ref{fig:batch01}). It also allows for \CGG{} to +be run by external programs, with no need for the user to manually +interact with the user interface. \begin{figure}[htpb] \centering \includegraphics[width=1.0\linewidth]{batch01.png} @@ -821,9 +821,9 @@ program, execute: \texttt{batchjob.rc}. \textbf{Warning} this file will be modified so if you use any filename that is not a legitimate list of batch jobs to render, that file will be overwritten and its previous contents destroyed. -When invoked with these parameters, \CGG{} -will start up and perform the rendering jobs in the list contained -in that file, without creating its usual windows. If you do not +When invoked with these parameters, \CGG{} will start up and run the +rendering jobs in the list contained in that file starting at the defined +\textit{active region}, without creating its usual windows. If you do not specify a filename, the default will be \$HOME/.bcast5/batchrender.rc. Possible messages you might see where you started up the job are as follows. \begin{description} @@ -925,15 +925,16 @@ operation is somewhat difficult. That is why the command line aborts if any output files already exist. To perform rendering from the command line, first run \CGG{} in -graphical mode. Go to \texttt{File $\rightarrow$ Batch - Render}. Create the batches you intend to render in the batch window -and close the window. This automatically saves the batches in a file +graphical mode. Go to \texttt{File $\rightarrow$ Batch Render}. +Create the batches you intend to render in the batch window and +close the window. This automatically saves the batches in a file with the name of \$HOME/.bcast5/batchrender.rc. Set up the desired render farm attributes in \texttt{Settings $\rightarrow$ Preferences} and quit out of \CGG{} if you want to use the Render Farm capability. These settings are used the next time command line rendering is used to process the current set of batch jobs without a -GUI\@. +GUI\@. It is important to remember that the rendering will begin at +the defined \textit{active region} saved when the project was saved. On the command line run: @@ -1044,7 +1045,7 @@ communication, shared filesystem, permissions and usernames synched. \item in the \textit{Hostname} box, keyin your hostname or ip address such as 192.168.1.12 or \textit{localhost}; \item enter in a port number such as 401--405 (only a root user - can use privileged ports) or $1025$ and click on \textit{Add Nodes}; + can use privileged ports) or $10400...$ for non-root and click on \textit{Add Nodes}; \item you will see something like the following in the Nodes listbox to the right:\newline \begin{tabular}{lllc} On & Hostname & Port & Framerate @@ -1337,12 +1338,6 @@ RenderFarmClient::main_loop: Session started from 127.0.0.1 \end{lstlisting} As it completes its jobs, you will should see: \begin{lstlisting}[style=sh] RenderFarmClientThread::run: Session finished -\end{lstlisting} A quick way to start a sequence of clients is to - use: -\begin{lstlisting}[style=sh,mathescape] -for n in `seq 1501 1505`; do - cin -d $\$$n -done \end{lstlisting} \item[Render Using Render Farm] After you have followed the preceding steps, you are ready to use the render farm. Click on @@ -1477,7 +1472,7 @@ list of items to check. section of the video so keep that in mind when designating port numbers. \item If not running as root, a port number in the higher range of - $1024$ and above must be used instead of the $400+$ range. + $1024$ and above must be used instead of the $401+$ range. \item The master and client jobs on the ports do not go away so if you want to stop them, you will have to kill them via: \texttt{kill PID\#}. -- 2.26.2