All very good questions.  I think a new section in the manual would be a good idea to cover these.  AppImages make it possible for anyone to test out Cinelerra quickly without having to build it themselves.  But with all of the gains from the graphics cards these days, serious users are best served by building in their own environment, although Vulcan is "supposed" to make that unnecessary.

Andrey's releases are actually the most useful for the majority of people for ease of installation and do not have the restrictions that AppImages do.

On Sat, Mar 14, 2026 at 2:13 PM Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org> wrote:
This is a bunch of follow-up questions I feel both users and
occasionally builders want easy clarified without to much research or
experiments. I neither say these cannot be partly answered in nor
derived from the manual documentation.  Additional questions may appear ;)

Q1
What capabilites/features does the pre-build Cingg AppImage and/vs the
package build (ex. RPM) have?
especially with regards to ffmeg, multimedia codecs, encoders etc.

Q2
Is the AppImage static linked and RPM dynamic linked or combined
dynamic/staticvwith regards to libs?

Q3
Does the AppImage use the thirdparty ffmpeg and the RPM the local system
ffmpeg?
or are both static builds with third party ffmpeg

Q4
Where is possibly the ffmpeg binary for the extracted AppImage and
installed RPM?
for own build ffmpeg binary is found in
cinelerra-5.1/thirdparty/ffmpeg-8.0/ffmpeg

Q5
Who make and maintain the thirdparty ffmpeg and what extra codecs are added?

Q6
What are the configure scripts for the AppImage vs RPM?

Q7
What extra capabilites/features may be achieved and justified with own
custom build?
what config elements?

Q8
How often is it needed or suggested to download (or update if possible)
the source repo via git clone?





_______________________________________________
Cin mailing list -- cin@lists.cinelerra-gg.org
To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org