Q2
Is the AppImage static linked and RPM dynamic linked or combined
dynamic/staticvwith regards to libs?
Appimage uses mix of statically-added thirdparty libs embedded in "cin" binary and system's dynamic libs put into self-extracting squashfs archive.
RPM depends on those dynamic libs from system to be present and compatible between build system and system rpm ran on.
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
it is not packaged/installed.
Hardware acceleration methods:This ffmpeg has 25 enabled features plus a lot of thirdparties
vdpau
cuda
vaapi
qsv
vulkan
So no secrets here :)
Q5
Who make and maintain the thirdparty ffmpeg and what extra codecs are added?
At this moment it seems that I try to maintain it. I mostly added giant array of pixelformats to yuv4mpeg so cin can show that in GUI. Other patches carrying from earlier versions, dealing with seeking, mpegts muxing for BluRay disks, some gopro-specific cases for hw acceleration and may be something else