Context help can be requested from almost any \CGG{} window or subwindow by pointing with the mouse cursor on the GUI element of interest and pressing \texttt{Alt/h}. That HTML manual page will be shown via the configured web browser, which is assumed as most relevant to the GUI element currently under the mouse pointer.
-\subsection{How it works}%
+\subsection{How Context Help works}%
\label{sub:how_it_works}
The hotkey to request context help is \texttt{Alt/h}. What particular help page is shown, depends on the mouse cursor location while \texttt{Alt/h} is pressed. Usually, when the mouse is located in some window or dialog, the help page related to the functionality of this window or dialog is shown. In this case the mouse can point either on some widget, or on an empty area in the window. In \CGG{} GUI there are several rich loaded windows, \textit{Timeline} and \textit{Compositor} for example. In such a case different help pages can be requested depending on the particular GUI element under the mouse. For example, pressing \texttt{Alt/h} while pointing on the \textit{Autos curve} in a track would show help on \textit{automation keyframes} section, pointing on the \textit{Overlay} mode button in the \textit{patchbay} would show help on \textit{overlays}, pointing on the \textit{camera control} in \textit{Compositor} would show help on \textit{camera and projector}.
\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 session and settings and exiting \CGG{}, 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 preferences will be lost until you go back to your original \texttt{.bcast5}.
- \item You can also temporarily rename just \CGG{}\_rc in your \$HOME/.bcast5 directory, so
+ \item You can also temporarily rename just Cinelerra\_rc in your \$HOME/.bcast5 directory, so
that a new file with the original name will be created with original defaults. You will lose your preferences,
but it is just for testing and you can move back the renamed \CGG{}\_rc over the new one if that is not the
cause of the problem. Be sure to stop and restart \CGG{} whenever you rename this file.
\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 \CGG{} 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.
+ \item When using AppImage to run with the OpenGL video driver, you must have the OpenGL drivers
+for your Operating System graphics board installed as it is not included in the AppImage library set. The
+error message you might see if this is not installed is: \textit{error while loading shared libraries: libGLU.so.1: cannot open shared object: No such file or directory}.
+ \item If you have updated your Operating System or newly installed some applications, it is
+possible that your LV2 plugin path may have been modified and be in disagreement with what you have set
+for \CGG{}. This could result in a crash upon startup. Look at the messages in the window from where
+you started \CGG{} to see if they look similiar to the following:
+\begin{lstlisting}[numbers=none,xleftmargin=10mm]
+LOAD: http://eq10q.sourceforge.net/matrix\_lr2ms
+LOAD: http://eq10q.sourceforge.net/matrix\_ms2lr
+LOAD: https://community.ardour.org/node/7596
+LOAD: urna-comp
+** segv at 0x7f2cd80813c4 in pid 4540, tid 4540
+\end{lstlisting}
+The last line before the \textit{segv} indicates the name of the LV2 plugin that is causing problems.
+Please refer to the section on LV2 plugins \ref{sec:audio_lv2_calf_plugins} to resolve the issue.
+ \item Check your \textit{Overlays} window if you do not see your Assets, Titles, Transitions, Plugin Keyframes, or other lines such as Fade, Cameras, etc. on your timeline.
+These items will still be functional, but you may be confused when you do not actually see their physical presence if you inadvertently unchecked them in the \textit{Overlays} window. Use the \textit{Window} pulldown to enable/disable the \textit{Show Overlays} window.
+ \item BugTracker - sometimes there is a problem creating a new report issue in the website's Mantis Bugtracker
+using the Chrome web browser and you lose what you just typed in. Generally when logging into the bugtracker, the
+option "only allow with this IP address" needs to be disabled, then the bug tracker will work fine.
+ \item Forum - if you can not register your username in the website's Forum, it could be
+because the protection measures against spammers also is in effect with real users, so sometimes the website blocks the registration for the forum. This often affects email addresses of well-known email providers. Send email to the mailing list (({\small \url{https://lists.cinelerra-gg.org/mailman/listinfo/cin}}) so that you can be added to the forum manually as long as
+you confirm that you agree with the terms of use of this website and the forum.
+ \item Forum - in the website's Forum, use of unacceptable characters or strings can result in the error
+message "A potentially unsafe operation has been detected in your request to this site". You lose what
+you had typed in and you will have to check what you remember typing in for a non-converational set of
+characters. This can be as simple as ../../ (dot dot slash dot dot slash) or some types of C++ code.
\end{enumerate}
\textbf{Some Helpful User Readable Text Dumps}
This is not a problem. \CGG{} is building an index for your file in order to better seek. In that process, different methods are tried until a successful scan is complete.
\bigskip
+\textit{int FFMPEG::init\_encoder(const char*);} followed by
+\newline
+\textit{bad file format:} \quad \texttt{your directory/filename}
+
+This error occurs when you are rendering, or possibly capturing media via recording, when the
+file format/type are set to an incompatible option. To fix this in the Render window, check
+the Video and Audio wrenches configure compression settings and choose a compatible Compression
+as shown when clicking on the down arrow in the Preset window.
+\bigskip
+
\textit{AudioALSA::write\_buffer err -32(Broken pipe) at sample \#}
This indicates that there is something wrong with the audio. Some reasons for this are:
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{Using a non-supported locale could cause a failure in starting \CGG{} with the following error.}
+
+\begin{lstlisting}[numbers=none,xleftmargin=10mm]
+
+ BC_WindowBase::init_im: Could not open input method.
+ unjoined tids / owner 1
+ 00007f543dffb700 / 00007f54989d5840 12BC_Clipboard
+
+\end{lstlisting}
+
+This is caused by LC\_CTYPE setting you are using, and maybe other Locale settings too.
+For example, using the following will cause the \textit{unjoined tids} error.
+
+\begin{lstlisting}[numbers=none,xleftmargin=10mm]
+ LC_CTYPE="en_IL" /mnt0/build5/cinelerra-5.1/bin/cin # set LC_CTYPE and start cin
+\end{lstlisting}
+
+This is an operating system error which is resolved by using the following startup instead:
+
+\begin{lstlisting}[numbers=none,xleftmargin=10mm]
+
+ LC_CTYPE="en_GB.utf8" /mnt0/build5/cinelerra-5.1/bin/cin # set LC_CTYPE and start cin
+\end{lstlisting}
+
+You can either export the LC\_CTYPE variable before starting \CGG{} or
+add this in your bash startup file or simply run from the command line as shown above.
+
\bigskip
\textit{Masking Feather is not working and produces error messages on the startup window similar to:}
projects / goodguy / cin-manual-latex.git / blobdiff