From: Good Guy Date: Tue, 9 Nov 2021 00:08:02 +0000 (-0700) Subject: minor fixes to include need for libGLU for OpenGL/AppImage X-Git-Tag: 2021-11~8 X-Git-Url: https://git.cinelerra-gg.org/git/?p=goodguy%2Fcin-manual-latex.git;a=commitdiff_plain;h=5532aef6c024e0cd81833d961fdcc57489f28cb0 minor fixes to include need for libGLU for OpenGL/AppImage --- diff --git a/parts/Configuration.tex b/parts/Configuration.tex index b1a796b..944c9f6 100644 --- a/parts/Configuration.tex +++ b/parts/Configuration.tex @@ -94,7 +94,7 @@ The video drivers are used for video playback in the compositor and the viewer. \item[White balance CR2 images] this enables white balancing for CR2 images if interpolation is also enabled. This is because proper white balancing needs a blending of all 3 primary colors. White balance uses the camera's matrix which is contained in the CR2 file. Disabling white balancing is useful for operations involving dark frame subtraction. The dark frame and the long exposure need to have the same color matrix. If you disable Interpolate CR2 Images and use the Interpolate Pixels effect, be aware the Interpolate Pixels effect always does both interpolation and white balancing using the camera's matrix, regardless of the settings in Preferences. Dark frame subtraction needs to be performed before Interpolate Pixels. \item[Video driver] \index{video!driver} normally video on the timeline goes to the compositor window during both continuous playback and when the insertion point is repositioned. Instead of sending video to the Compositor window, the video driver can be set to send video to another output device during continuous playback. However, this does not affect where video is routed when the insertion point is repositioned. Options are listed next. \begin{description} - \item[\textit{X11}] this was the first method of graphical display on Unix systems. It just writes the RGB triplet for each pixel directly to the window. It is useful when graphics hardware can not handle very large frames. And when X11 is usled with the associated checkbox enabled of \textit{use direct x11 render if possible} it can be a really good playback method to speed up playback for large frames. + \item[\textit{X11}] this was the first method of graphical display on Unix systems. It just writes the RGB triplet for each pixel directly to the window. It is useful when graphics hardware can not handle very large frames. And when X11 is used with the associated checkbox enabled of \textit{use direct x11 render if possible} it can be a really good playback method to speed up playback for large frames. \item[\textit{X11-XV}] this was an enhancement to X11 in 1999. It converts YUV to RGB in hardware with scaling. In some cases it may be the preferred playback method, but it can not handle large frame sizes. Maximum video size for XV is usually $1920\times1080$. \item[\textit{X11-OpenGL}] the most powerful video playback method is OpenGL. With this driver, most effects are done in hardware with the graphics board installed in the computer. OpenGL allows video sizes up to the maximum texture size, which is usually larger than what XV supports, depending on the graphics driver. OpenGL relies on PBuffers and shaders to do video rendering. Plugins or transitions that do not have \textit{handle OpenGL} in the code will use software instead of hardware and this will slow down playback. OpenGL does not affect rendering. It just accelerates playback. X11-OpenGL processes everything in 8 bit color models, although the difference between YUV and RGB is retained. The scaling equation set in the preferences window is ignored by OpenGL -- it always uses linear scaling. Camera and projector operations use OpenGL, but some of the effects may not support OpenGL acceleration. diff --git a/parts/Installation.tex b/parts/Installation.tex index c4687d7..55d3b70 100644 --- a/parts/Installation.tex +++ b/parts/Installation.tex @@ -59,6 +59,10 @@ And Leap 15.3 (OpenSUSE) requires installation of the \textit{appimage} package. sudo zypper se -is appimage \end{lstlisting} +In addition, if you are using the OpenGL video driver, you will need to install the appropriate OpenGL +drivers for your Operating System graphics board because libGLU.so and other OpenGL libraries are +not included in the AppImage. + \section{Download Already Built \CGG{}}% \label{sec:download_already_built_cinelerra_gg} diff --git a/parts/Trouble.tex b/parts/Trouble.tex index e188330..ca3fe58 100644 --- a/parts/Trouble.tex +++ b/parts/Trouble.tex @@ -215,6 +215,9 @@ bottom of the main window (figure~\ref{fig:automation}). \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