From: Good Guy Date: Fri, 31 Jan 2020 20:43:17 +0000 (-0700) Subject: more Andrea fine-tuning + added Windows 10/Cygwin X-Git-Tag: 2021-05~131 X-Git-Url: https://cinelerra-gg.org/git/?a=commitdiff_plain;h=5eb85a40a89efd492f7876163af1d205369dfbc3;p=goodguy%2Fcin-manual-latex.git more Andrea fine-tuning + added Windows 10/Cygwin --- diff --git a/CinelerraGG_Manual.tex b/CinelerraGG_Manual.tex index 6f291f4..cc6fa70 100644 --- a/CinelerraGG_Manual.tex +++ b/CinelerraGG_Manual.tex @@ -1,6 +1,6 @@ % \documentclass[ -Letter, +a4paper, 14pt, oneside, openright, @@ -35,10 +35,10 @@ svgnames \include{parts/Editing} \include{parts/Rendering} \include{parts/Keyframes} -\settocdepth{subsection} +%\settocdepth{subsection} \include{parts/FFmpeg} \include{parts/Plugins} -\settocdepth{section} +%\settocdepth{section} \include{parts/Transition} \include{parts/Overlays} \include{parts/Recording} diff --git a/common/packages.tex b/common/packages.tex index 0676531..f2f9036 100644 --- a/common/packages.tex +++ b/common/packages.tex @@ -101,10 +101,11 @@ \usepackage{enumitem} % custom lists \usepackage[colorinlistoftodos,textsize=tiny]{todonotes} % todo package -\setlength{\marginparwidth}{1.6cm} % fix left margin for todo +\setlength{\marginparwidth}{2.0cm} % fix left margin for todo \usepackage{scrextend} \usepackage{enumitem} +\usepackage{ifthen} \usepackage{[tocvsec2} \usepackage[intoc]{nomencl} % glossary package \makenomenclature % make glossary diff --git a/parts/Installation.tex b/parts/Installation.tex index 4c2f387..0695aa0 100644 --- a/parts/Installation.tex +++ b/parts/Installation.tex @@ -567,6 +567,160 @@ pacman -S cin ##pacman -R cin \end{lstlisting} +\section{Windows 10 with Cygwin for Cinelerra limited}% +\label{sec:ms_windows10} + +To run Cinelerra on a Windows 10 computer, you will need to have Cygwin installed on your system, +along with the Cinelerra static tar and a patched library: libxbc. This setup has been tested +with Windows 10, version 1909, on an HP EliteBook 820 at 2.3 GHz. + +This limited version provides \textit{core} functionality at this time with the standard Windows FFmpeg +executable, meaning that specific modifications in FFmpeg needed for Cinelerra are not available. +Limited capabilities include only a few render output formats available - for example \textit{mov}, \textit{qt} +as \textit{mjpeg}, and \textit{mpeg} for videos and \textit{avi} and \textit{qt} as \textit{s16le} +for audio, but not \textit{mkv} or \textit{mp4}. +This is due to the fact that several codec and utility libraries are not currently compiled to +work with Windows. + +\underline{Installing Cygwin:} + +Cygwin is an environment that runs natively on Windows which allows Unix programs to be compiled +and run on Windows. With cygwin installed on your Windows 10 computer, you will be able to run +Cinelerra. Before installing cygwin, you need to be warned that the Avast anti-virus software +kills files necessary for cygwin installation and execution, so you will have to remove it and +use alternative anti-virus software (the standard default already included with Windows 10 +is Defender). Below are the steps for installation: + +\begin{enumerate} + \item Download cygwin for your 64-bit computer at: \url{https://www.cygwin.com/} + \item Generally just take the defaults as they show up, but the next steps show what comes up. + \item When a warning window pops up, click \textit{Yes}. + \item Click \textit{Next}. + \item Choose \textit{Install from Internet} option and then click \textit{Next}. + \item Choose your desired directory by clicking on Browse button. Choose \textit{All Users (Recommended)} and then click \textit{Next}. + \item Choose the local package directory where you would like your installation files to be placed. Click \textit{Next}. + \item Choose \textit{Direct Connection} if you are using Internet with plug and play device. Click \textit{Next}. + \item Choose any download site preferably "cygwin.mirror.constant.com" and then click \textit{Next}. + \item For list of things to install, leave all set to \textit{Default} except these to \textit{Install} instead: + +\begin{tabular}{ll} + base& devel\\ + gnome& graphics\\ + system& video\\ + X11 \\ +\end{tabular} + + This install takes a long time; approximately 2 hours on an EliteBook and requires approximately 20GB storage. + \item Finally you will want to have the icons on your desktop (already default) and then click \textit{Finish}. +\end{enumerate} + +Then to install the Cinelerra tar files, you will need to start a cygwin console terminal from the startup menu as shown here: + Start $\rightarrow$ Cygwin $\rightarrow$ Cygwin64 Terminal + +\underline{Installing Cinelerra:} + +\begin{enumerate} + \item Download the tar file at: + https://cinelerra-gg.org/download/testing/libxcb-bld.tar.bz2 + \item Install libxbc from the tar file -- installs into /usr/local and requires approximately 21MB storage. +\begin{lstlisting}[language=bash,numbers=none] + $ tar -C /usr/local -xJf /path/libxcb-bld.tar.bz2 +\end{lstlisting} +The libxcb path repairs an error (XIOError), which stops the program. + \item Download the tar file at: + https://cinelerra-gg.org/download/testing/cygcin-bld.tar.bz2 + \item Install cygcin from the tar file - this installs into home directory. Note this is cygcin NOT cygwin. +\begin{lstlisting}[language=bash,numbers=none] + $ cd + $ tar -xJf /path/cygcin-bld.tar.bz2 +\end{lstlisting} +\end{enumerate} +This creates \~{}/cygcin , a user build installation of Cinelerra and requires approximately 400MB storage. + +\underline{Running Cinelerra:} + +You will need to start a cygwin desktop from the startup menu: +\begin{enumerate} + \item Start$\rightarrow$ Cygwin-X $\rightarrow$ Openbox + +You should start a console controlling terminal so that you can see program logging. + \item Start$\rightarrow$ Cygwin $\rightarrow$ Cygwin64 Terminal + +This opens a separate window that can survive a cygwin hang and bugs. Without these logs, it is much more difficult to use. + + \item Type into that console controlling window, the following: +\begin{lstlisting}[language=bash,numbers=none] + $ export DISPLAY=:0.0 +\end{lstlisting} + \item Change directories to where Cinelerra is installed: +\begin{lstlisting}[language=bash,numbers=none] + $ cd /path/cygcin (NOT cygwin) +\end{lstlisting} + \item Finally keyin: +\begin{lstlisting}[language=bash,numbers=none] + $ ./cin +\end{lstlisting} +which starts up your 4 Cinelerra windows. +\end{enumerate} + +The most noticeable difference from the Linux versions is that Cinelerra seems to run +very slowly on Windows 10. You must be very tolerant and patient to see this work. +It can however exhibit astonishing speed when encoding. Cinelerra has to be downgraded significantly due to lack of supported interfaces, codecs (for example h264/h265), and utilities. +The only graphics driver is X11 and the only sound driver is pulseaudio. Almost all configurable +omissions are applied to this build. + +\underline{Cinelerra build on cygwin from source code:} + +\begin{enumerate} + \item Download and install ffmpeg into /usr/local : + + download ffmpeg (currently 4.2.2) +\begin{lstlisting}[language=bash,numbers=none] + $ cd /tmp + $ tar -xJf /path/ffmpeg-4.2.2.tar.bz2 + $ cd ffmpeg-4.2.2 + $ ./configure + $ make -j + $ make install +\end{lstlisting} + \item Download and install a patched libxcb: +\begin{lstlisting}[language=bash,numbers=none] + $ cd /tmp + $ rm -rf libxcb-1.13/ + $ tar -xf /path/libxcb-1.13.tar.bz2 + $ cd libxcb-1.13/ + $ patch -p1 < /path/cinelerra-5.1/thirdparty/src/libxcb.patch1 + patching file configure.ac + patching file src/xcb_in.c + $ ./autogen.sh + $ ./configure + $ make -j + $ make install +\end{lstlisting} + \item Download cinelerra-gg: +\begin{lstlisting}[language=bash,numbers=none] + $ cd /build_path/ + $ git clone "git://git.cinelerra-gg.org/goodguy/cinelerra.git" + $ cd cinelerra-gg/cinelerra-5.1 +\end{lstlisting} + \item Apply cygwin patch: +\begin{lstlisting}[language=bash,numbers=none] + $ patch -p2 < blds/cygwin.patch +\end{lstlisting} + \item Run the build with: +\begin{lstlisting}[language=bash,numbers=none] + $ ./blds/cygwin.bld +\end{lstlisting} +\end{enumerate} + +This produces a directory: $/build\_path$/cinelerra-gg$/cinelerra-5.1$/bin \newline +which is used to create the cygcin archive. + +Currently, the targets are not stripped and can be run from gdb. +There is only very limited signal handler dmp file support. +Running gdb from inside a desktop resident console (not a cygwin64 window) will hang cygwin (and cin) when it hits a breakpoint. You must run from an external console window to avoid this issue. + + \section{Distribution Systems with Cinelerra Included}% \label{sec:distribution_systems_with_cinelerra_included} diff --git a/parts/Introduction.tex b/parts/Introduction.tex index a7e6407..27301ec 100644 --- a/parts/Introduction.tex +++ b/parts/Introduction.tex @@ -227,7 +227,7 @@ And which chapters are important for beginning to learn to use Cinelerra-GG. At Only read this chapter if you are confused about a specific covered topic and how it works. - \item[Chapter \ref{cha:Troubleshooting and Help}] \nameref{cha:Troubleshooting and Help}. + \item[Chapter \ref{cha:troubleshooting_help}] \nameref{cha:troubleshooting_help}. Use this chapter for diagnosing a problem and find out what to report to get the best resolution or help. diff --git a/parts/Plugins.tex b/parts/Plugins.tex index 7b4f169..decd72e 100644 --- a/parts/Plugins.tex +++ b/parts/Plugins.tex @@ -346,6 +346,7 @@ This converts the input to rgb before xxxxxx runs, and so it too is slower (beca \section{Audio Effects - Native}% \label{sec:audio_effects_native} +\settocdepth{subsection} \subsection{AudioScope}% \label{sub:audioscope} @@ -698,6 +699,7 @@ NOTE: There is often confusion between Tremolo and Vibrato, but the vibrato is t \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: @@ -782,6 +784,7 @@ For example: \section[Video Effects --- Native]{Video Effects -- Native}}% \label{sec:video_effects_native} +\settocdepth{subsection} \subsection{1080 to 480}% \label{sub:1080_to_480} @@ -1967,7 +1970,7 @@ This effect makes video tracks appears as a painting. It can be controlled by \t \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 \nameref{cha: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 \href{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: @@ -2866,6 +2869,7 @@ Figure~\ref{fig:zoom} shows the parameters: Radius=21 and Steps=3. \section{OpenCV plugins}% \label{sec:opencv_plugins} +\settocdepth{section} The \textit{Find Object} plugin searches a Scene for an Object, and the Object can be overlayed with a Replacement object. It requires the thirdparty \textit{OpenCV} (Open Computer Vision) library and you will have to do your own build. Also, be aware that the two useful algorithms of \textit{Sift} and \textit{Surf} have been removed from versions of OpenCV after version $4$. diff --git a/parts/Tips.tex b/parts/Tips.tex index bec6c66..6fe12f2 100644 --- a/parts/Tips.tex +++ b/parts/Tips.tex @@ -527,7 +527,7 @@ This section is a handy guide for describing various kinds of software computer \begin{description} \item[System lockups:] When the system locks up, it is usually a system problem. Normally an application program cannot lock up the system. It is a major goal of system design to prevent an application (app) from failing a system interface. This does not mean an app can not cause a system lockup, but it is unusual. - \item[Cinelerra crash:] This is covered in \ref{cha:Crash Dumps for Analysis} Crash Dumps for Analysis, chapter 18. Just a reminder that for best results you should be root and by providing a crash dump and as much other information as possible, you will be helping the developer to analyze the problem and fix it so that it can be avoided in the future. + \item[Cinelerra crash:] This is covered in \ref{cha:crash_dumps_analysis} Crash Dumps for Analysis, chapter 18. Just a reminder that for best results you should be root and by providing a crash dump and as much other information as possible, you will be helping the developer to analyze the problem and fix it so that it can be avoided in the future. \item[X Server crash:] Keyboard does not respond, screen is frozen, caps lock may operate LED light. Sometimes using \texttt{ctrl-alt-F1} $\dots$ \texttt{ctrl-alt-F7} (etc.) will allow you to regain control of a VT console. You can use this to login and check logs: eg. \textit{/var/log/Xorg.0.log}, \textit{dmesg}, \textit{journalctl} $\dots$ etc. If you have another computer, make sure a terminal server is configured (for example: rsh, ssh, or telnet), then remote login via this other computer and check the logs. Most important is to immediately note the current software state, and the very last thing that preceded the crash, i.e. last button click, last keystroke, $\dots$ or whatever. \item[Kernel crash:] The machine goes completely dead. The keyboard caps lock LED will probably be flashing. Most likely the only way to see anything after the kernel crashes is to use a serial port console log and usually kdb, the kernel debugger, and special cabling. This requires a lot of setup, and is normally reserved for experts. Login from another computer will not work. Pinging the ip address will not respond since the network stack is part of the kernel. There are some virtual machine setups that will let you debug a \textit{guest} kernel, but this also requires a lot of setup, and affects which kernel is currently under test. The kdb route is preferable. \item[Keyboard grabs, Server grabs, and Deadlocks:] A grab is an X-server state where all events are forced to just one window event stream. This forces the user to respond to the dialog. Things seems to be working, but no keypresses do anything useful. The system clock and other programs will still be working. The network will work for remote logins. Grabs can be canceled if the \texttt{/etc/X11/xorg.conf} X config contains special setup as shown below: diff --git a/parts/Trouble.tex b/parts/Trouble.tex index 934b0bd..683fd28 100644 --- a/parts/Trouble.tex +++ b/parts/Trouble.tex @@ -1,95 +1,85 @@ \chapter{Troubleshooting and Help}% -\label{cha:Troubleshooting and Help} +\label{cha:troubleshooting_help} You can report potential problems, bugs, and crashes to the Cinelerra-GG website at: -\medskip -\hspace{10mm}\href{https://www.cinelerra-gg.org/}{https://www.cinelerra-gg.org} -\medskip +\begin{center} + \href{https://www.cinelerra-gg.org/}{https://www.cinelerra-gg.org} +\end{center} Here you can log the problem into the MantisBT bugtracker, or use the forum Q\&A for help from other users, or email the -problem using the address: \href{mailto:cin@lists.cinelerra-gg.org}{cin@lists.cinelerra-gg.org} . It is usually more +problem using the address:{\small \href{mailto:cin@lists.cinelerra-gg.org}{cin@lists.cinelerra-gg.org}} It is usually more helpful if instead of starting Cinelerra from its application icon, start from a window so that if there are error messages related to the problem, they can be captured from the screen and emailed or logged. The command to run -from a window is: {\textless}directory\_path of where you installed cinelerra{\textgreater}/bin/cin -- for example if -installed in the directory /mnt0/build5/cinelerra-5.1, you would execute the following command to start the program: -\ \ /mnt0/build5/cinelerra-5.1/bin/cin \ . \ The problem you are experiencing may be as simple as an error due to the -settings in your \$HOME/.bcast5 subdirectory so you may want to first rename your current .bcast5 in order to start -with default settings. By renaming the directory instead of deleting it, you will be able to put it back and not lose -all of your preferences. -\medskip +from a window is: \texttt{/bin/cin} -- for example if +installed in the directory \texttt{/mnt0/build5/cinelerra-5.1}, you would execute the following command to start the program:\\ +\texttt{/mnt0/build5/cinelerra-5.1/bin/cin} \\ +The problem you are experiencing may be as simple as an error due to the settings in your \texttt{\$HOME/.bcast5} subdirectory so you may want to first rename your current \texttt{.bcast5} in order to start with default settings. By renaming the directory instead of deleting it, you will be able to put it back and not lose all of your preferences. Some other troubleshooting help is also included in other sections of this manual for specific features. \section{What to Include in Problem Reports}% -\label{cha:What to Include in Problem Reports} +\label{cha:include_in_problem_reports} For the best help, if you have a reproducible problem and can provide the following list of materials for analysis, it -is usually possible to figure out what the problem is and how to fix it. \ It may be a simple usage or setup mistake or -a real bug which a programmer would like to fix rather quickly. \ Although it is not always necessary to provide this -much information, it eliminates the ``try this'' or ``did you do this?'' and a lot of ``guessing'' rather than heading -straight for a solution. \textcolor{red}{Even if you can not provide all of this information, please report the problem in case other users are having the same issue.} -\medskip +is usually possible to figure out what the problem is and how to fix it. It may be a simple usage or setup mistake or +a real bug which a programmer would like to fix rather quickly. Although it is not always necessary to provide this +much information, it eliminates the \textit{try this} or \textit{did you do this?} and a lot of \textit{guessing} rather than heading straight for a solution. \textcolor{red}{Even if you can not provide all of this information, please report the problem in case other users are having the same issue.} -Basically we\textbf{ need to see what you see }with the input, output, and session file. \ Here is a list of the items that will most likely help to resolve the problem, but all of them will not necessarily be needed. -\medskip +Basically we\textbf{ need to see what you see }with the input, output, and session file. Here is a list of the items that will most likely help to resolve the problem, but all of them will not necessarily be needed. \begin{itemize}[nosep] \item Provide a detailed description of the problem and the last operation performed if you remember it. \item Supply a small representative sample of the original input that exhibits the issue. \item If possible, also provide the rendered output, again using that representative sample. - \item Save a session file used with that same sample which will contain a lot of setup parameters; the best method to do this is to use the File pulldown of ``Export Project...'' with the Copy option. That way all of the files will be in 1 location and easily loaded onto any other computer. + \item Save a session file used with that same sample which will contain a lot of setup parameters; the best method to do this is to use the \texttt{File $\rightarrow$ Export Project}$\dots$ with the Copy option. That way all of the files will be in 1 location and easily loaded onto any other computer. \item To make sure that the same rendering setup is used, it may be necessary to send an additional session file at the definition point just before rendering starts. - \item Include the Operating System name and version number and version of Cin that you are running. You can find the date and time ``built'' in the Settings$\rightarrow$Preferences, About tab, bottom left corner. + \item Include the Operating System name and version number and version of Cin that you are running. You can find the date and time \textit{built} in the \texttt{Settings $\rightarrow$ Preferences, About} tab, bottom left corner. \end{itemize} -\medskip It is better to upload any files to a drop site as some of them can be quite large. -\medskip -\textbf{How to create a session file:} \ from the menubar pulldown File$\rightarrow $Save\_as{\dots} \ and choose a -filename, for example /tmp/beforerender.xml . \ Do this after you have the situation setup so can see values in use. -\ As just stated, \textit{Export Project} option provides the most inclusive session information, but size could make -it very large and cumbersome to upload or download. -\medskip +\textbf{How to create a session file:} \quad from the menubar pulldown \texttt{File $\rightarrow $ Save\_as}{\dots} \quad and choose a filename, for example \texttt{/tmp/beforerender.xml} Do this after you have the situation setup so can see values in use. As just stated, \textit{Export Project} option provides the most inclusive session information, but size could make it very large and cumbersome to upload or download. + +\textbf{How to create a representative small sample:} -\textbf{How to create a representative small sample:} \begin{enumerate}[nosep] \item open the input media, set up the scenario as you normally would to start the project render; \item select 5-15 seconds of media using the edit mode left mouse button drag highlighting on the timeline; - \item start the render dialog (Shift R), set the filename path, and set ``Render range'' to ``Selection''; - \item recommended ``Insertion strategy'' is ``Replace current project''; then press the checkmark OK. The result will ``load replace'' the current project for you to review to ensure the error still occurs. If this small sample does not create the error, try a different section or upload the entire input media. + \item start the render dialog (Shift-R), set the filename path, and set \textit{Render range} to \textit{Selection}; + \item recommended \textit{Insertion strategy} is \textit{Replace current project}; then press the checkmark OK. The result will \textit{load replace} the current project for you to review to ensure the error still occurs. If this small sample does not create the error, try a different section or upload the entire input media. \end{enumerate} \section{Crash Dumps for Analysis}% -\label{cha:Crash Dumps for Analysis} -If you get a SEGV crash and can explain what steps you took, a /tmp/cinelerra\_{\textless}pid{\textgreater}.dmp file is -very useful for analysis. \ You can also use Ctrl-c in the controlling window to force an INTR signal interrupt when -you think the program is hung up. \ You can only perform one Ctrl-c as the second Ctrl-c quits out of the program. \ It -is best to upload the .dmp, input files and other files to datafilehost or similar temporary site as they may be quite -large. \ The .dmp filename looks like /tmp/cinelerra\_{\textless}pid{\textgreater}.dmp. \ Log a bug report or email all +\label{cha:crash_dumps_analysis} +If you get a SEGV crash and can explain what steps you took, a \texttt{/tmp/cinelerra\_ .dmp} file is +very useful for analysis. You can also use Ctrl-c in the controlling window to force an INTR signal interrupt when +you think the program is hung up. You can only perform one Ctrl-c as the second Ctrl-c quits out of the program. It +is best to upload the \texttt{.dmp}, input files and other files to datafilehost or similar temporary site as they may be quite large. The \texttt{.dmp} filename looks like \texttt{/tmp/cinelerra\_ .dmp} Log a bug report or email all helpful information on the crash, location of uploaded files, and list of setup steps that illustrate the problem to -\href{mailto:cin@lists.cinelerra-gg.org}{cin@lists.cinelerra-gg.org} . -\medskip +{\small \href{mailto:cin@lists.cinelerra-gg.org}{cin@lists.cinelerra-gg.org}} \begin{enumerate}[nosep] \item Use the latest version of Cinelerra as you want to make sure the problem has not been fixed. - \item Be sure gdb is installed (usually installed but if not, it is easy to do so). - \item Run as root if at all possible (this enables using gdb to create a full /tmp/cinelerra*.dmp file). - \item Be sure Settings-{\textgreater}Preferences-{\textgreater}Interface-{\textgreater}trap SEGV and trap INTR are checked. - \item Invoke the error. This should create the file /tmp/cinelerra-{\textless}pid{\textgreater}.dmp . + \item Be sure \textit{gdb} is installed (usually installed but if not, it is easy to do so). + \item Run as root if at all possible (this enables using gdb to create a full \texttt{/tmp/cinelerra* .dmp} file). + \item Be sure \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Interface $\rightarrow$ trap SEGV} and \texttt{trap INTR} are checked. + \item Invoke the error. This should create the file \texttt{/tmp/cinelerra-.dmp} \end{enumerate} \medskip For those who can not run as root or can not create the problem while running as root, another method to create a dump -is available. \ Here are the steps to do so -- you should also have gdb installed. +is available. Here are the steps to do so -- you should also have gdb installed. \medskip \begin{enumerate}[nosep] - \item Temporarily login as root and key in: \ \ echo 0 {\textgreater} /proc/sys/kernel/yama/ptrace\_scope . This opens up ptrace, used by gdb (the debugger). You will want to reverse this when done. - \item Run Cinelerra as an ordinary user from a window using the command line and try to create the problem. If the program crashes, this should produce a file named /tmp/cinelerra*.dmp where * is a number. The dump usually takes about 30 seconds or so to complete after the failure invokes the crash handler, so be patient. - \item Email the output that shows in the window from where you started up Cinelerra and upload or directly email the /tmp/cinelerra*.dmp file (this file may be too large for the Mailing List). - \item After you are finished creating/testing the problem, reverse the previous setting while logged in as root by keying in:\ \ echo 1 {\textgreater} /proc/sys/kernel/yama/ptrace\_scope . + \item Temporarily login as root and key in:\\ + \texttt{echo 0 > /proc/sys/kernel/yama/ptrace\_scope} \\ + This opens up \textit{ptrace}, used by gdb (the debugger). You will want to reverse this when done. + \item Run Cinelerra as an ordinary user from a window using the command line and try to create the problem. If the program crashes, this should produce a file named \texttt{/tmp/cinelerra*.dmp} where * is a number. The dump usually takes about 30 seconds or so to complete after the failure invokes the crash handler, so be patient. + \item Email the output that shows in the window from where you started up Cinelerra and upload or directly email the \texttt{/tmp/cinelerra*.dmp} file (this file may be too large for the Mailing List). + \item After you are finished creating/testing the problem, reverse the previous setting while logged in as root by keying in:\\ + \texttt{echo 1 > /proc/sys/kernel/yama/ptrace\_scope} \end{enumerate} \textcolor{red}{Even if you are not logged in as root or have ptrace enabled, if you @@ -97,29 +87,25 @@ have a .dmp file and know what the last thing you did is, please provide the .dm probability that the dump will prove useful, but if the problem can be recreated it can usually be fixed! \section{When things go wrong}% -\label{cha:When things go wrong} +\label{cha:when_things_go_wrong} Sometimes things go wrong and there are some ways to continue your work without much trouble. Below is a list of items to try before abandoning your session. -\begin{enumerate}[nosep] - \item If you suddenly get hangs on media or strange looking tracks, you might want to rebuild indexes. You can do this in the Resources window with a right mouse click on the media to get a pulldown\ with the \textit{Rebuild index} option. For an easy way to rebuild for all of your media use Settings$\rightarrow$Preferences, Interface tab, Index Files section, ``Delete existing indexes''. This will take some time to recreate all of the currently loaded media and subsequent loads, but can be an easy fix. - \item On an older computer, if you are playing media and it can not keep up, you can turn off ``Play every frame'' in the Video Out tab of Settings$\rightarrow$Preferences, Playback tab. You will then see the video jump as it skips frames in order to stay caught up. - \item The \textit{Cache size} can be lowered to 1048 if playback seems choppy or if you have problems with lv2 plugins, or you can increase the \textit{Cache size} for better flow. This can be changed in Settings$\rightarrow$Preferences, Performance tab. - \item After saving your current session and exiting Cinelerra, you might want to rename your current \$HOME/.bcast5 directory and start with the default setup. This will eliminate your settings as the potential cause of a problem; however, all of your current preferences will be lost until you go back to your original .bcast5. - \item Some media has only a single keyframe at the beginning of the file so that moving anywhere on the timeline results in just a black image in the compositor. Cinelerra needs more keyframes to determine position. You can temporarily use Settings$\rightarrow$Proxy to 1/2 size to put in keyframes. How to use Proxy is explained in Performance Tips and Other Tips, chapter 19. - \item If the rate at which frames are captured during Recording is much lower than the framerate of the source, the video will accumulate in the recording buffers over time and the audio and video will become out of sync. Decrease the number of frames to buffer in the device in Settings$\rightarrow $Preferences, Recording tab so that the excess frames are dropped instead of buffered. - \item If loading files locks up, this might be because Cinelerra is building picons/vicons for the Resources window. If you load a large number of images it needs to decompress every single image to build a picon/vicon. Go into Settings$\rightarrow$Preferences, Appearance tab and disable \textit{Use}\textit{thumbnails in resource window} to skip this process. Keep in mind though, that it only has to create these thumbnails the first time a new piece of media is loaded or the values are changed. - \item For an older computer with less CPU power, in Settings$\rightarrow$Preferences, Appearance tab, be sure that \textit{Autocolor assets }is disabled; set \textit{View thumbnail size} \& \textit{Vicon quality}\& \textit{Vicon color mode} to lower values or switch to \textit{No Play} instead of \textit{Full Play} in the Resources window (this is to the right of the word \textit{Visibility} in the left hand side of that window). You will then have more CPU and more memory available to do actual editing. +\begin{enumerate} + \item If you suddenly get hangs on media or strange looking tracks, you might want to rebuild indexes. You can do this in the Resources window with a right mouse click on the media to get a pulldown with the \textit{Rebuild index} option. For an easy way to rebuild for all of your media use \texttt{Settings $\rightarrow$ Preferences, Interface} tab, Index Files section, \textit{Delete existing indexes}. This will take some time to recreate all of the currently loaded media and subsequent loads, but can be an easy fix. + \item On an older computer, if you are playing media and it can not keep up, you can turn off \textit{Play every frame} in the \textit{Video Out} tab of \texttt{Settings $\rightarrow$ Preferences, Playback} tab. You will then see the video jump as it skips frames in order to stay caught up. + \item The \textit{Cache size} can be lowered to 1048 if playback seems choppy or if you have problems with lv2 plugins, or you can increase the \textit{Cache size} for better flow. This can be changed in \texttt{Settings $\rightarrow$ Preferences, Performance} tab. + \item After saving your current session and exiting Cinelerra, you might want to rename your current \texttt{\$HOME/.bcast5} directory and start with the default setup. This will eliminate your settings as the potential cause of a problem; however, all of your current preferences will be lost until you go back to your original \texttt{.bcast5}. + \item Some media has only a single keyframe at the beginning of the file so that moving anywhere on the timeline results in just a black image in the compositor. Cinelerra needs more keyframes to determine position. You can temporarily use \texttt{Settings $\rightarrow$ Proxy} to $\frac{1}{2}$ size to put in keyframes. How to use Proxy is explained in \href{sec:proxy_settings}{Proxy settings and Transcode}. + \item If the rate at which frames are captured during Recording is much lower than the framerate of the source, the video will accumulate in the recording buffers over time and the audio and video will become out of sync. Decrease the number of frames to buffer in the device in \texttt{Settings $\rightarrow $ Preferences, Recording} tab so that the excess frames are dropped instead of buffered. + \item If loading files locks up, this might be because Cinelerra is building picons/vicons for the Resources window. If you load a large number of images it needs to decompress every single image to build a picon/vicon. Go into \texttt{Settings $\rightarrow$ Preferences, Appearance} tab and disable \textit{Use thumbnails in resource window} to skip this process. Keep in mind though, that it only has to create these thumbnails the first time a new piece of media is loaded or the values are changed. + \item For an older computer with less CPU power, in \texttt{Settings $\rightarrow$ Preferences, Appearance} tab, be sure that \textit{Autocolor assets }is disabled; set \textit{View thumbnail size} \& \textit{Vicon quality}\& \textit{Vicon color mode} to lower values or switch to \textit{No Play} instead of \textit{Full Play} in the Resources window (this is to the right of the word \textit{Visibility} in the left hand side of that window). You will then have more CPU and more memory available to do actual editing. \end{enumerate} -\medskip -{\bfseries -Some Helpful User Readable Text Dumps} -\medskip +\textbf{Some Helpful User Readable Text Dumps} -On the File pulldown, there is a {\textquotedbl}Dumps{\textquotedbl} option with a submenu of dump EDL, Plugins, Assets, and Undo. \ In all cases, you will have to have started Cinelerra from a window instead of from an application icon and +On the File pulldown, there is a \textit{Dumps} option with a submenu of dump EDL, Plugins, Assets, and Undo. In all cases, you will have to have started Cinelerra from a window instead of from an application icon and the text results will be shown in that window. -\medskip \begin{itemize}[nosep] \item \textit{Dump EDL} will display your current EDL state on the screen in the window from where you started Cin. This can be useful to see information concerning a specific edit or a file path. @@ -127,55 +113,50 @@ the text results will be shown in that window. \item \textit{Dump Assets} displays the media assets that you have loaded and various pertinent details on each, such as samplerate, width, and height. \item \textit{Dump Undo }will dump the last 32 edits on the undo stack exactly as kept, which can be useful if you are looking to see how far back in the undo to go to get to a specific spot. \end{itemize} -\medskip -{\bfseries -Common Problems} +\textbf{Common Problems} Some messages you may see in the startup window may or may not be errors. Some examples are: \bigskip -\textit{FFMPEG::open\_decoder: some stream times estimated:}\textbf{ \ \ }/your directory/filename -\medskip +\textit{FFMPEG::open\_decoder: some stream times estimated:} \quad \texttt{/your directory/filename} This is not a problem. Basically, when you open a file if a stream has a known duration, there is no message. If the duration is unknown, it is estimated by using the File Size and Bitrate to estimate the duration. This may just indicate that the stream number Cinelerra uses versus ffmpeg may be counted differently. \bigskip \textit{AudioALSA::write\_buffer err -32(Broken pipe) at sample \#} -\medskip This indicates that there is something wrong with the audio. Some reasons for this are: \begin{itemize}[nosep] \item You simply stopped playing in Cinelerra while the audio is in progress. \item Running on a computer where there is no sound card. - \item Incorrect setup of the audio parameters in the Settings-{\textgreater}Preferences, Playback tab. - \item Your sound system is already in use by another program, like when playing {\textquotedbl}tunes{\textquotedbl} outside Cin. + \item Incorrect setup of the audio parameters in the \texttt{Settings $\rightarrow$ Preferences, Playback} tab. + \item Your sound system is already in use by another program, like when playing \textit{tunes} outside Cin. \end{itemize} \bigskip \textit{Playback does not keep up so you hear the audio ahead of the video.} -\medskip -When this occurs, it most likely means that there is not enough CPU power to keep up. You can go into Settings$\rightarrow$Preferences, the Playback tab and uncheck ``Play every frame''. Not playing every frame means that as it plays, if it can not keep up with doing all it has to do to change the frame into a vframe and then draw it, the program just notes that it is falling behind so skips frames to catch back up. This does not affect rendering. A different solution is to use Background Rendering as described in Rendering, chapter 7. +When this occurs, it most likely means that there is not enough CPU power to keep up. You can go into \texttt{Settings $\rightarrow$ Preferences, Playback} tab and uncheck \textit{Play every frame}. Not playing every frame means that as it plays, if it can not keep up with doing all it has to do to change the frame into a vframe and then draw it, the program just notes that it is falling behind so skips frames to catch back up. This does not affect rendering. A different solution is to use Background Rendering as described in \href{sec:background_rendering}{Rendering}. \bigskip \textit{Cinelerra will not start and produces error message on the startup window.} -\medskip -There can be various reasons that Cinelerra does not come up. Some of the recent reasons are listed here. Please notify the \href{http://www.cinelerra-gg.org/}{www.cinelerra-gg.org} website when you have any unknown startup issues. +There can be various reasons that Cinelerra does not come up. Some of the recent reasons are listed here. Please notify the {\small \href{http://www.cinelerra-gg.org/}{www.cinelerra-gg.org}} website when you have any unknown startup issues. \medskip \begin{itemize}[nosep] \item Cin doesn't come up in Debian with compiz window manager running. Workaround is to use a different window manager or bring up cin first and then compiz. There is also a report that Compiz leads to single frame problems after a certain amount of time in the case where you switch to fullscreen mode and than back to normal node -- cin stops working and so you will have to restart cin. - \item When a library goes from one version to a later version, sometimes a pre-built Cin binary will fail because it was created at a different version than the one the user has on their computer. This seems to happen more frequently on Arch distros because Arch has continuous releases and is usually kept up to date. An example of the error message you might see in your startup window would be:\newline``cin: error while loading shared libraries: libvpx.so.5: cannot open shared object file: No such file'' + \item When a library goes from one version to a later version, sometimes a pre-built Cin binary will fail because it was created at a different version than the one the user has on their computer. This seems to happen more frequently on Arch distros because Arch has continuous releases and is usually kept up to date. An example of the error message you might see in your startup window would be:\\ + \texttt{cin: error while loading shared libraries: libvpx.so.5: \\ + cannot open shared object file: No such file} \end{itemize} \medskip -You can usually install the required library to fix the problem. A temporary fix may be to create a symlink but this must be done with extreme caution as it may create an unstable condition. \ A better workaround is to use a tarball to install the software instead of the package build until the libraries are in sync between the build and your Operating System install. +You can usually install the required library to fix the problem. A temporary fix may be to create a symlink but this must be done with extreme caution as it may create an unstable condition. A better workaround is to use a tarball to install the software instead of the package build until the libraries are in sync between the build and your Operating System install. \bigskip \textit{ Loading a very large number of media files, for example 500 clips, crashes Cinelerra with messages similar to the following that are displayed in the window from where you started Cin:} -\medskip \begin{lstlisting}[numbers=none,xleftmargin=10mm] @@ -188,11 +169,10 @@ You can usually install the required library to fix the problem. A temporary fix \end{lstlisting} -This usually indicates that you are out of Operating System file descriptors. You can increase the amount easily with the following command line: ulimit -n 4096 where 4096 is a size suggestion but can be increased. You can include this command line in your .bashrc or .profile file for the user login which gets run every time you login, or modify the Operating System limit for everyone in the system file, which for Fedora is /etc/security/limits.conf. Alternatively, you can reduce the number of file descriptors needed by going into Settings>Preferences, Appearance tab and unchecking the flag “use thumbnails in resource window”. +This usually indicates that you are out of Operating System file descriptors. You can increase the amount easily with the following command line: \texttt{ulimit -n 4096} where 4096 is a size suggestion but can be increased. You can include this command line in your \texttt{.bashrc} or \texttt{.profile} file for the user login which gets run every time you login, or modify the Operating System limit for everyone in the system file, which for Fedora is \texttt{/etc/security/limits.conf}. Alternatively, you can reduce the number of file descriptors needed by going into \texttt{Settings $\rightarrow$ Preferences, Appearance} tab and unchecking the flag \textit{use thumbnails in resource window}. \bigskip \textit{Masking Feather is not working and produces error messages on the startup window similar to:} -\medskip \begin{lstlisting}[numbers=none,xleftmargin=10mm] 0:1(10): error: GLSL 4.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.40, 1.00 ES, and 3.00 ES @@ -207,76 +187,73 @@ main000(); } \end{lstlisting} -In the mask window, check the box ``Disable OpenGL masking'' to use software instead of OpenGL. +In the mask window, check the box \textit{Disable OpenGL masking} to use software instead of OpenGL. \section{Menu Bar Shell Commands}% -\label{Menu Bar Shell Commands} +\label{menu_bar_shell_commands} -In order to provide some types of help, the Menu Bar Shell Commands are available for customization purposes. \ In the +In order to provide some types of help, the Menu Bar Shell Commands are available for customization purposes. In the main window on the top line containing the File, Edit, {\dots} Window pulldown menus, all the way to the right hand -side is the ``shell cmds'' icon. \ You might see a small gold-color bordered box with the {\textgreater}\_.\_ inside -and if you mouse over it, the tooltip says ``shell cmds''. This is a configurable popup which gives you the ability to +side is the \textit{shell cmds} icon. You might see a small gold-color bordered box with the $>\_.\_$ inside +and if you mouse over it, the tooltip says \textit{shell cmds}. This is a configurable popup which gives you the ability to see a table of Shortcuts in html format, refer to the reference manual or execute a pre-defined script to perform a -specific task, such as some type of post processing which you plan on performing on a repeat basis. \ Unless redirected +specific task, such as some type of post processing which you plan on performing on a repeat basis. Unless redirected elsewhere, the output from executing any script-type commands will be displayed in the window from where you started Cinelerra. -\medskip The Shell Cmds popup menu items are configured in: -\medskip -\hspace{10mm}Settings$\rightarrow$Preferences$\rightarrow$Interface$\rightarrow$Shell Commands -\medskip +\texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Interface $\rightarrow$ Shell Commands} This runs a dialog that lets you Add/Del/Edit the scripts in the main menu popup. \ Possible options are:\newline -\begin{enumerate}[nosep,] - \item \textit{Add} a new menu item/script:\newline -\ \ \ \ click on the \textit{Add} button\newline -\ \ \ \ in the Label box, change the word {\textquotedbl}new{\textquotedbl} to the desired menu label (for example: -Graphics Editor)\newline -\ \ \ \ in the Commands box, type the command lines to be included in the script (for example: gimp)\newline -\ \ \ \ click the green checkmark for OK in the Commands window\newline -\ \ \ \ click the green checkmark for OK in the Shell window\newline -\ \ \ \ click on OK or Apply in the Preferences window\newline - \item \textit{Del} to delete an existing menu item:\newline -\ \ \ \ \ select to highlight an entry in the Cinelerra: Shell listbox\newline -\ \ \ \ \ click on the \textit{Del }button\newline -\ \ \ \ \ click the green checkmark for OK in the Shell window\newline -\ \ \ \ \ click on OK or Apply in the Preferences window (the entry is now deleted)\newline - \item \textit{Edit} an existing menu item:\newline -\ \ \ \ select to highlight an entry in the Cinelerra: Shell listbox\newline -\ \ \ \ click on the \textit{Edit} button (the Commands window appears)\newline -\ \ \ \ set the label and/or commands to the new desired values\newline -\ \ \ \ click on the green checkmark for OK in the Commands window\newline -\ \ \ \ click on the green checkmark for OK in the Shell window\newline -\ \ \ \ click on OK or Apply in the Preferences window +\begin{enumerate} + \item \textit{Add} a new menu item/script: + \begin{itemize}[noitemsep] + \item click on the \textit{Add} button + \item in the Label box, change the word \textit{new} to the desired menu label (for example: Graphics Editor) + \item in the Commands box, type the command lines to be included in the script (for example: gimp) + \item click the green checkmark for OK in the Commands window + \item click the green checkmark for OK in the Shell window + \item click on OK or Apply in the Preferences window + \end{itemize} + \item \textit{Del} to delete an existing menu item + \begin{itemize}[noitemsep] + \item select to highlight an entry in the Cinelerra: Shell listbox + \item click on the \textit{Del }button + \item click the green checkmark for OK in the Shell window + \item click on OK or Apply in the Preferences window (the entry is now deleted) + \end{itemize} + \item \textit{Edit} an existing menu item: + \begin{itemize}[noitemsep] + \item select to highlight an entry in the Cinelerra: Shell listbox + \item click on the \textit{Edit} button (the Commands window appears) + \item set the label and/or commands to the new desired values + \item click on the green checkmark for OK in the Commands window + \item click on the green checkmark for OK in the Shell window + \item click on OK or Apply in the Preferences window + \end{itemize} \end{enumerate} -\medskip -Next time you click on the ``shell cmds'' icon, you will have the changes you made in effect.\newline +Next time you click on the \textit{shell cmds} icon, you will have the changes you made in effect. Both the \textit{Add} and \textit{Edit} options have checkboxes in the Commands window for the following: -\medskip \begin{itemize}[nosep] - \item OnExit notify \ \ \ choose Always, Never, or On error to get a popup window notify - \item run path/script.sh + argvs \ \ \ to run a particular script with argvs (\$1, \$2,{\dots} arguments) + \item \textit{OnExit notify} \quad choose Always, Never, or On error to get a popup window notify + \item run \texttt{path/script.sh + argvs} \quad to run a particular script with argvs (\$1, \$2,{\dots} arguments) \end{itemize} -{\ttfamily -\textrm{{When modifications to the Shell Cmds are included in a new Cinelerra release, they are not added to your Preferences file automatically unless you create a new one. \ But if you have added no custom scripts, you can update your currently existing \$HOME/.bcast5/Cinelerra\_rc file to delete the lines that are all grouped together that begin with the letters: \ SHBTN \ \ (the entire line - these are the SHell BuTtoNs). \ You should first Quit out of Cinelerra, edit the file, and then when you restart Cinelerra, it will create the new default buttons in that same file.}}} -\medskip +When modifications to the Shell Cmds are included in a new Cinelerra release, they are not added to your Preferences file automatically unless you create a new one. But if you have added no custom scripts, you can update your currently existing \texttt{\$HOME/.bcast5/ Cinelerra\_rc} file to delete the lines that are all grouped together that begin with the letters: \texttt{SHBTN} (the entire line -- these are the \textbf{SH}ell \textbf{B}u\textbf{T}to\textbf{N}s). \ You should first Quit out of Cinelerra, edit the file, and then when you restart Cinelerra, it will create the new default buttons in that same file. There are 2 specific Cinelerra file names that have unique characteristics that allow for usage from a user-defined -script. \ The first one is an environment variable, CIN\_RENDER which is used in the RenderMux shell command that is already setup. \ It contains the complete path and filename of the file in your session that you selected as ``Select a file to render to'' when you ran a Render operation. -\medskip +script. The first one is an environment variable, \texttt{CIN\_RENDER} which is used in the \textit{RenderMux} shell command that is already setup. It contains the complete path and filename of the file in your session that you selected as \textit{Select a file to render to} when you ran a Render operation. -The second one concerns usage of the Resource window assets to use as argvs in shell scripts. \ The added command line -can ONLY be a script. \ Then if your script refers to \$1, \$2 and \$3 and you highlight 3 files in the Media folder, -their full path name will be used as the argvs to your script. \ For example, if you added a shell commands script -\ /workspace/script.sh \ that contains the following lines: +The second one concerns usage of the Resource window assets to use as argvs in shell scripts. The added command line +can ONLY be a script. Then if your script refers to \$1, \$2 and \$3 and you highlight 3 files in the Media folder, +their full path name will be used as the argvs to your script. For example, if you added a shell commands script +\texttt{/workspace/script.sh} that contains the following lines: \begin{lstlisting}[numbers=none,xleftmargin=10mm] cp ``\$1'' /tmp/temporary_copy @@ -284,42 +261,37 @@ cp ``\$2'' /tmp/new_copy cp ``\$3'' /tmp/file_to_upload \end{lstlisting} -and you highlight 3 files in the Resources window called ABC.mp4, 123.mp4, and Final.mp4 and execute your added script -from the Shell Cmds icon, you will be copying those 3 highlighted files to the new names on /tmp. -\medskip +and you highlight 3 files in the Resources window called\textit{ ABC.mp4}, \textit{123.mp4}, and \textit{Final.mp4} and execute your added script from the Shell Cmds icon, you will be copying those 3 highlighted files to the new names on \texttt{/tmp}. -There are some Help features currently included in the Shell Cmds menu. \ Those available are: -\medskip +There are some Help features currently included in the Shell Cmds menu. Those available are: -\begin{enumerate}[nosep] +\begin{enumerate} \item \textit{Current Manual} in PDF format from cinelerra-gg.org or automatically downloaded. - \item \textit{Setting Shell Commands} ``how to'' which explains how to configure your own commands. + \item \textit{Setting Shell Commands} \textit{how to} which explains how to configure your own commands. \item \textit{Shortcuts} html file for easily looking up a particular shortcut. - \item \textit{RenderMux} shell script to use ffmpeg concatenate to copy files such as look.mp4001, look.mp4002, look.mp4005{\dots} that were rendered using ``Create new file at each label'' or with the Render Farm. + \item \textit{RenderMux} shell script to use ffmpeg concatenate to copy files such as \textit{look.mp4001}, \textit{look.mp4002}, \textit{look.mp4005}{\dots} that were rendered using \textit{Create new file at each label} or with the Render Farm. \end{enumerate} \clearpage \begin{figure}[h!] \centering - \includegraphics[width=0.8\linewidth]{trouble-img001.png} + \includegraphics[width=1.0\linewidth]{trouble-img001.png} \caption{Some windows used to manipulate Shell Commands scripts} - \label{fig:Shell script manupulation} + \label{fig:shell_script_manupulation} \end{figure} \section{Cinelerra Command Line -h}% -\label{cha:Cinelerra Command Line -h} +\label{cha:cinelerra_command_line_-h} To see the command line parameters available to use with Cinelerra, key in: -\hspace{10mm}/\{your Cinelerra directory path\}/bin/cin -h -\medskip +\qquad \texttt{/bin/cin -h} What will be shown in the window where this line was entered is: -\medskip Usage: -./cin [-f] [-c configuration] [-d port] [-n nice] [-r batch file] [filenames] +\texttt{./cin [-f] [-c configuration] [-d port] [-n nice] [-r batch file] [filenames]} -d = Run in the background as renderfarm client. The port (400) is optional.\\ -f = Run in the foreground as renderfarm client. Substitute for -d.\\ @@ -328,6 +300,5 @@ Usage: -r = batch render the contents of the batch file (/root/.bcast5/batchrender.rc) with no gui. batch file is optional.\\ -S = do not reload perpetual session\\ -x = reload from backup\\ -\\ filenames = files to load