Some example file names are as follows - where 8 digits represent yyyymmdd:
\begin{lstlisting}[style=sh]
- CinGG-20220131-x86_64.AppImage
+ CinGG-20230131-x86_64.AppImage
(currently based on Fedora 32, linux kernel 5.8.15, libc version 2.31)
- CinGG-20220131-x86_64-older-distros.AppImage
+ CinGG-20230131-x86_64-older-distros.AppImage
(currently based on Ubuntu 16.04, libc version 2.23)
- CinGG-20220131-i686.AppImage
+ CinGG-20230131-i686.AppImage
(currently based on Debian 9, linux kernel 4.9, use "newer" for Debian 11.0)
- CinGG-20220131-i686-newer-distros.AppImage
+ CinGG-20230131-i686-newer-distros.AppImage
(currently based on Debian 11, linux kernel 5.10)
- CinGG-20220131-x86_64-multibit.AppImage
+ CinGG-20230131-x86_64-multibit.AppImage
(currently based on Fedora 32, libc version 2.31)
- CinGG-20220131-x86_64-older-distros-multibit.AppImage
+ CinGG-20230131-x86_64-older-distros-multibit.AppImage
(currently based on Fedora 29 - runs on RHEL8 - linux kernel 4.19.9, libc version 2.28)
+ CinGG-20230930-alternative_shortcuts.AppImage
+ (currently based on Ubuntu 16.04, libc version 2.23)
\end{lstlisting}
Make the file executable with the proper execute permissions either from the GUI of the Desktop Environment used (link to the file) or from a terminal window. Make sure you are already in the directory containing the appimage:
Using AppImage means you can't have the installation folder and work on the files. To unpack the AppImage and get its structure in folders and files see \nameref{sub:managing_appimage} To create, edit and manage appimages see \nameref{sub:built_appimage_scratch}.
+\subsection{AppImage with Standard Shortcuts}
+\label{sec:appimage_standard_shortcuts}
+
+In video editing it is important to learn how to use shortcuts to speed up your work. \CGG{} uses shortcuts different from those considered standard in both the Linux world and video editing. For example, \texttt{"s"} is used instead of \texttt{Ctrl+S}, \texttt{"q"} instead of \texttt{Ctrl+Q}, and even the classic editing keys \texttt{J, K, L} are different.
+In addition, in \CGG{} the keys are fixed and not customizable. A new user may have a hard time getting used to a new combination of shortcuts. To make it a little easier, an appimage containing a patch that makes use of some of the more frequently used classic key combinations is available. It can be downloaded \href{https://cinelerra-gg.org/download/images/CinGG-20230930-alternative_shortcuts.AppImage}{here} (note that the file contains the month and last day of the month, but you will want to go up a directory and download the latest date instead to include the current changes). A table showing the changes from \CGG{} mode to standard mode can be found here: \nameref{sec:alternative_shortcuts}.
+
\section{Download Already Built \CGG{}}%
\label{sec:download_already_built_cinelerra_gg}
\item You need about 6.0 \,GB of disk storage to operate a build and
you need to have \textit{git} installed.
-\item Obviously in order to install into the system, you must run as
- \textbf{root}.
+\item You do not need to be \textbf{root} (or \textit{sudo} ...) to install, except to run \texttt{bld\_prepare.sh} which calls in the distro's package manager. However if there are problems with permissions you can try to compile as root.
\item The \textit{git:} step has to download many files (approx
130\,MB) so allow time. When decompressed this will expand to
\begin{lstlisting}[style=sh]
./blds/bld_prepare.sh <os> # where <os> represents the
# Operating System of
- # centos, fedora, suse, ubuntu, mint, debian.
+ # centos, fedora, suse, ubuntu, mint, debian, arch, debian-older, ubuntu-older.
./autogen.sh
./configure --prefix=/usr # optional parameters can be added here
make 2>&1 | tee log # make and log the build
\end{lstlisting}
- \texttt{bld\_prepare.sh} does not work for Arch Linux or Gentoo,
- so we have to install the dependencies
- manually. \texttt{README.arch} or \texttt{README.gentoo}, which
- contain the list of dependencies, can be found at:
- \begin{list}{}{}
+\texttt{bld\_prepare.sh} works for Arch and Gentoo with some additional information. For Arch linux, a README file containing many more dependencies is maintained. For Gentoo, a README file lists other dependencies that have to be installed manually.
+\begin{list}{}{}
\item \href{https://cinelerra-gg.org/download/README.arch}{https://cinelerra-gg.org/download/README.arch}
\item \href{https://cinelerra-gg.org/download/README.gentoo}{https://cinelerra-gg.org/download/README.gentoo}
- \end{list}
+\end{list}
+
+ \texttt{bld\_prepare.sh} option of debian-older and ubuntu-older is currently for older operating system versions since before about 06/2022.
\item Check for obvious build errors:
\begin{lstlisting}[style=sh]
make install
\end{lstlisting}
Where <os> represents the Operating System supported by \CGG{}, such
-as centos, fedora, suse, ubuntu, mint, debian.
+as centos, fedora, suse, ubuntu, mint, or debian.
The ``with-single-user'' parameter makes it so.
% Make and log build (
Check for errors before proceeding.
\item You need at least 6\,GB of disk storage to operate a build +
you need to have “\texttt{git}” installed.
-\item Recommend you build and run as \textbf{root}, just to avoid
- permission issues initially.
+\item You can install it without being \textbf{root} or without using \textit{sudo}. In case of problems you can use \textit{sudo} to avoid permission issues.
\item The \textit{git} step has to download many files (approx
130\,MB) so allow time.
NOTE: if your system has never had \CGG{} Infinity installed, you
will have to make sure all the compilers and libraries necessary are
-installed. So on the very first build you should run as
-\textbf{root}:
+installed. Thus, for the execution part of \texttt{bld\_prepare.sh} you must use sudo, but the other steps can be done as a normal user.
% FIXME No novels in the listings.
\begin{lstlisting}[style=sh]
make install
\end{lstlisting}
Where <os> represents the Operating System supported by \CGG{}, such
-as centos, fedora, suse, ubuntu, mint, debian.
+as centos, fedora, suse, ubuntu, mint, debian and arch.
The ``with-single-user'' parameter makes it so.
% Make and log build (
Check for errors before proceeding.
Then just start the application by keying in: \texttt{./cin} in the
bin subdirectory OR add a desktop icon by using the appropriate
-directory to copy the files to, run as \textbf{root}, and edit to
+directory to copy the files to and edit to
correct the directory path. Below are generic directions of how to
do this.
Then just start the application by keying in: \texttt{./cin} in the
bin subdirectory OR add a desktop icon by using the appropriate
-directory to copy the files to, run as \textbf{root}, and edit to
-correct the directory path. Below are generic directions of how to
+directory to copy the files to, run as root, and edit to correct the directory path. Below are generic directions of how to
do this.
\begin{lstlisting}[style=sh]
the \texttt{Exec=cin} line to be
\texttt{Exec=<your\_directory\_path>/bin/cin}.
-The preceding directions for doing a single-user build may work
-without being root on some distros except for the \texttt{bld\_prepare.sh}
-and creating the desktop icon. For example in Arch Linux installing without being root
-works using the following steps:
+A working example of how to build in Arch as a normal user:
\begin{lstlisting}[style=sh]
$ git clone --depth 1 "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5
$ cd /home/USER/cinelerra5/cinelerra-5.1
$ ./autogen.sh
-$ ./configure --prefix=/usr --with-single-user --with-booby
+$ ./configure --with-single-user --with-booby
$ make 2>&1 | tee /tmp/cin5.log && make install
+$ mv Makefile Makefile.cfg
+$ cp Makefile.devel Makefile
\end{lstlisting}
-
\subsection{Notable Options and Caveats}%
\label{sub:notable_options_and_caveats}
\index{./configure}
success. Included in this section are some of the build variations
easily available for normal builds.
+You can, during compilation, use a patch that changes the main non-standard shortcuts of \CGG{} to standard ones (\texttt{Ctrl+S} and \texttt{J, K, L}, etc.).
+A table showing the changes from \CGG{} mode to standard mode can be found here: \nameref{sec:alternative_shortcuts}.
+The instructions for the build with the patch are as follows. After downloading the sources from the git repository in the usual way, you apply the patch:
+
+\begin{lstlisting}[style=sh]
+ cd cinelerra-5.1
+ patch -p1 -i alt_shortcuts.patch
+ ./bld.sh
+\end{lstlisting}
+
To see the full list of features use:
\begin{lstlisting}[style=sh]
export FFMPEG_EXTRA_CFG=" --disable-vdpau"
\end{lstlisting}
+Note for building 32-bit packages on hybrid 32/64 x86 systems, you may
+need to add the following:
+
+\begin{lstlisting}[style=sh]
+setarch i686 (befire configure and package build)
+\end{lstlisting}
+
NOTE: as of May 31, 2021 when Context Help was added, to include
this Context Help you will need to download the corresponding
tgz file containing the HTML manual sections referenced for the
have already installed libraries which are normally in the
thirdparty build, getting them to be recognized means you have to
install the \textit{devel} version so the header files which match
-the library interfaces exist. Below is the list of thirdparty
+the library interfaces exist. If you want to build using only the
+thirdparty libraries installed in your system, just include
+"--without-thirdparty" to your configure script. For example:
+\begin{lstlisting}[style=sh]
+./confgure --with-single-user --disable-static-build --without-thirdparty
+\end{lstlisting}
+Below is the list of thirdparty
builds, but this list may have changed over time.
% It's list of Table?
If you have a problem with the current GIT version, you can revert
to a previous working version easily. The commands to use will be
similar to these next lines which are then explained in more detail.
+You need "history" to do this, so should not have used the "depth 1"
+parameter on your GIT.
\strut
\begin{lstlisting}[style=sh]
gdb ./ci
\end{lstlisting}
+When you get the gdb prompt, type the letter "r", for run, and the windows will come up.
+If there is a crash, the windows will freeze and typing "bt" for backtrace in the startup window
+after the gdb prompt, provides useful information.
+
\subsection{Unbundled Builds}%
\label{sub:unbundled_builds}
\url{https://wiki.termux.com/wiki/Package\_Management}
\newline \url{https://wiki.termux.com/wiki/Building\_packages}
-\section{Distro with \CGG{} Included}%
+\section{Pre-built Packages and Distros with \CGG{} Included}%
\label{sec:distro_with_cinelerra_included}
\index{linux distro}
There are also some special complete distribution systems
available that include \CGG{} for audio and video production
-capabilities.
+capabilities as well as some pre-built packages in a build farm.
+
+\subsection{Build Farm pre-built Deb and RPM packages}
+\label{sec:packages}
+A build farm for \CGG{} deb and rpm packages that is in development is at this location \url{https://github.com/einhander/cin-gg-packages/releases}.
+It can build packages on every git change in the main repo with
+releases corresponding to a build date, not a git commit date.
+Current build hosts are \textbf{debian 12}, \textbf{alma linux 8},
+\textbf{Suse Leap 15.5}, \textbf{Fedora 38}, and \textbf{Ubuntu 22.04}.
\subsection{AV Linux}
\label{sec:AV_Linux}
Click \href{https://www.elivecd.org/}{Elive} for more information. The \CGG{} packages for the program
and the manual are in the direcotry at
+\href{https://repo.bookworm.elive.elivecd.org/pool/multimedia/c/} {Bookworm version 12} and
\href{https://repo.bullseye.elive.elivecd.org/pool/multimedia/c/} {Bullseye version 11} and
\href{http://repo.buster.elive.elivecd.org/pool/multimedia/c/}{Buster version 10} - just download
the .deb files inside that directory and install via “dpkg -i “.
projects / goodguy / cin-manual-latex.git / blobdiff