#
CINELERRA-GG AppImage

The main way to install CINELERRA-GG is to use the AppImage. This is updated regularly and works for every distro, since it already contains the necessary dependencies. A big advantage of using the AppImage format is that it is only 1/3 the size of the normal install, and since each release is named differently, you can keep a number of versions in a directory, and when testing from a terminal you just have to type CinGG, then hit tab, and complete it to the desired date release. A small disadvantage of using the AppImage format is that some of the options to make minor text type changes are not available and any graphics board speedups most likely will not work. In many cases, rendering has been found to take a small percentage longer than if you do your own build or use a package RPM as documented at Pre-built Packages and Distros with CINELERRA-GG Included. It is assumed that general processing will be slightly slower also.

For 64-bit systems you can choose between an image with up-to-date libraries or one that supports older libraries (named older-distro), which you should use only if the first image gives you problems with unsupported libs.

There are also 32-bit distros available that have i386 as part of the filename that currently works on older distros but may not work on the newest distros (most of the popular Linux distributions such as Arch, Ubuntu, and Fedora have dropped support for this older architecture). In any case, if you are using a 32-bit Linux distro, you might want to compile your sources from git or use a precompiled binary1.

Installing the appimage is simple, download the file from:

`https://cinelerra-gg.org/download/images/`

Some example file names are as follows - where 8 digits represent yyyymmdd and i386 are 32-bit:

    	CinGG-20241231-x86_64.AppImage
    	  (currently based on Fedora 32, linux kernel 5.8.15, libc version 2.31)
    	CinGG-20241231-x86_64-older-distros.AppImage
    	  (currently based on Ubuntu 16.04, libc version 2.23)
    	CinGG-20240731-x86_64-older-distros-multibit.AppImage
    	  (currently based on Fedora 29 - runs on RHEL8 - linux kernel 4.19.9, libc version 2.28)
    	CinGG-20241231-alternative_shortcuts.AppImage
    	  (currently based on Ubuntu 16.04, libc version 2.23)
    	CinGG-20241231-i386.AppImage
    	  (currently based on Debian 9, linux kernel 4.9, use "newer" for Debian 11.0)
    	CinGG-20241231-i386-newer-distros.AppImage
    	  (currently based on Debian 11, linux kernel 5.10)
    	CinGG-20241120-x86_64-IntelHW.AppImage
    	  (currently hardware bells and whistles for Intel to include QSV/AV1/oneVPL)

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:

    	\$ chmod u+x CinGG-yyyymmdd.AppImage

Finally start the program from a window in the directory where the image is stored:

    	\$ ./CinGG-yyyymmdd.AppImpage

or create a convenient desktop icon with a link to the run action, or do a Desktop Integration manually or with external programs. There is a description of a GUI methodology for doing so in this file on the webiste:

`https://cinelerra-gg.org/download/images/README_appimage.txt`

Most distros already have the libraries to run the appimage, but if not you may need an additional installation. For example Arch Linux needs the libappimage package.

    	sudo pacman -S libappimage

And Leap 15.3 (OpenSUSE) requires installation of the appimage package.

    	sudo zypper se -is appimage

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.

Using AppImage means you do not have the installation folder and work on the files. To unpack the AppImage and get its structure in folders and files see Managing AppImage To create, edit and manage appimages see Build the CinGG.AppImage from scratch.

#### Footnotes

... binary 1
  Remember that a 32-bit distro does not address more than 4GB of memory, so you may have stability and performance problems with large, high-resolution mediafiles.

Subsections

- AppImage with Standard Shortcuts