Den 15.11.2023 00:05, skrev Andrew Randrianasulu:


ср, 15 нояб. 2023 г., 01:56 Terje J. Hanssen <terjejhanssen@gmail.com>:


Den 14.11.2023 23:18, skrev Andrew Randrianasulu:


ср, 15 нояб. 2023 г., 01:10 Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org>:


Den 14.11.2023 17:51, skrev Phyllis Smith via Cin:
AppImage has some great advantages but also some disadvantages, one of which is stated below from the manual:
     
.......
There is an AppImage workaround that another user provided to solve this library problem, but it is not for the casual user -


Not to confuse the topic itself, but to complement the last section of the manual url listed:

IMO the bdwrite program was easier to use from a package build
https://www.mail-archive.com/cin@lists.cinelerra-gg.org/msg05138.html

And possibly also a bundled ffmpeg with Cinelerra can be used from a package build (please correct me if I'm wrong here!):
As an example, ffmpeg-6 with Cinelerra (soon) may optional be used, while the official distro still deliver ffmpeg-5

I do not think we package ffmpeg binary itself, but if users build from source they get it as bonus.

Nor in Andrey's prebuild packages at https://github.com/einhander/cin-gg-packages/releases ?

It is quite a long time ago, so it is possible I remember wrong ...

Well, there was ffmpeg-kino in Kino DV editor, but cinelerra(s)  were not packaging ffmpeg (because they used it via library interface and not cli binary) since at least 2016 when I first looked at Slackware packaging.

Other binaries from mjpegtools project are packaged, but not ffmpeg.

Thank you for clarifying that. I think I also verified this by finding no ffmpeg binary file in the (installed) cinelerra rpm.

but if users build from source they get it as bonus.

Did you mean Cinelerra  and/or ffmpeg build from source here?