The latest AppImages include FFmpeg 8.1 (updated from 8.0) and dav1d updated from 0.5.1 to 1.5.3. Note that an updated version of nasm at 2.15.05 is needed for FFmpeg if doing your own builds (more about this later).
Website ongoing improvements by Sam:- Major security improvements were added preventing compromising the website; as well as the
addition of multiple guards and checks saving time from having to handle spam that arrives in the
Forum and Mailing list or impacts GIT cloning.
- Mantis Bug Tracker was modified to allow for anonymous user login in order to be able to read the
items without being able to add spam.
FFmpeg updated from version 8.0 to 8.1 with our 13 patches tested/verified by Andrew.
Several text files updated: downloads.txt, info/plugins.txt, and ffmpeg/plugin.opts.
Andrew-R work:
- Minor fix to correct usage of “use direct x11 for render if possible” for older16 integer formats.
- Fixes to formats ffv1_vulkan.mov, h264_vaapi.mp4,
prores_4444xq.pro,
prores_4444.pro, and
created new
prores_vulkan.pro.
- Additional patch2 for x264 to “fix ppc64* pink artefacting and not passing test suite for Altivec
optimizations – fix sad_x4 and adjust chroma shift – as provided by videolan team.
- Fix added for building libaom 3.8.0 with older versions to continue support for Ubuntu 16. The
patch removes some warning flag add and switched to using in-tree nasm. It is not for sure an
acceptable solution so more testing and reporting of any anomalies would be useful. This may be
backed out in the future as updating Nasm and Cmake may be a more usable solution.
- Dav1d updated from 0.5.1 to 1.5.3 with a non-trivial patch to use cmake instead of their meson.
- X265 compile for multibit now uses multiple cpus when available so that total compile time can be
cut a few minutes (sometimes 21 minutes on a Ryzen 7 with 16 cpus instead of 43).
Manual updates:
- Additional “Tip” for taking advantage of a computer’s multiple gpus was provided by
Terje and
nicely Latex formatted by
Andrea.
- New section added to explain more about AppImages as prompted by Terje’s questions.