qt-avif-image-plugin
libavif
Our great sponsors
qt-avif-image-plugin | libavif | |
---|---|---|
5 | 44 | |
83 | 1,370 | |
- | 4.5% | |
7.1 | 9.7 | |
6 days ago | 3 days ago | |
C | C | |
BSD 2-clause "Simplified" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
qt-avif-image-plugin
-
How to use ksnip application to save screenshots in JPEG XL on Windows
Download qjpegxl.dll and qavif.dll and copy the DLL files into imageformats folder.
- How can I install avifenc on Ubuntu 20.04?
-
AOM AV1 encoder/decoder in Debian needs update to enable AVIF saving
libavif supports building selected dependencies locally. I have a script which builds static libaom to be bundled into libavif together with libyuv. It was necessary to add -DCONFIG_PIC=1 https://github.com/novomesk/qt-avif-image-plugin/blob/master/ext/build_local_libaom_libavif.sh Does Debian allow bundled dependencies? Because that would be a possibility how to build feature complete libavif.
-
How to open AVIF image format?
KDE apps (for example gwenview) are able to open AVIF when new versions of the following packages are installed: shared-mime-info, libavif, kimageformats When you have old packages, you can still register image/avif mime-type manually and to build/install the Qt plug-in manually. If you want to try it, read manual How to install AVIF support in KDE https://github.com/novomesk/qt-avif-image-plugin
-
KDE Frameworks 5.78 Brings Support for the AV1 Image Format to All KDE Apps, More
Thanks to Daniel Novomeský https://github.com/novomesk/qt-avif-image-plugin
libavif
-
CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
It's 2023, surely this is not yet another bug related to memory unsafety that could be avoided if we'd stop writing critical code that deals with extremely complex untrusted input (media codecs) in memory unsafe languages?
Yep, of course it is: https://github.com/webmproject/libwebp/commit/902bc919033134...
I guess libwebp could be excused as it was started when there were no alternatives, but even for new projects today we're still committing the same mistake[1][2][3].
[1] -- https://code.videolan.org/videolan/dav1d
[2] -- https://github.com/AOMediaCodec/libavif
[3] -- https://github.com/AOMediaCodec/libiamf
Yep. Keep writing these in C; surely nothing will go wrong.
- Libavif 1.0 Released
-
Is there any clear documentation on how to make avif collections and how to read them?
As far as I understand you are talking about this plugin. I don't know c++ and half of the code was like a black magic, but if I get it correctly, it encodes your images with libavif, and adds custom metadata ([solar/time of day] -> json -> base64).
-
FSF Slams Google over Dropping JPEG-XL in Chrome
So a few dozen comments, but so far it doesn't look like any mention the immediate thing that jumped out at me which was the claims vs AVIF:
>"In turn, what users will be given is yet another facet of the web that Google itself controls: the AVIF format."
Huh? I'll admit I haven't been following codecs as super ultra closely as I used to, but I thought AOM was a pretty broad coalition of varying interests and AV1 an open, royalty free codec that was plenty open source friendly? I've heard plenty of reasonable arguments that JPEG XL has some real technical advantages over AVIF and as well as superior performance is much more feature rich and scalable. So I could see people being bummed for that. But this is the first time I've heard the assertion that it's somehow a Google project? I mean, AOM's libavif reference is BSD too [0]? I'd love some more details on that from anyone who has been following this more closely. I can even understand if AOM isn't as community friendly and an accusation that it's dominated by big corps, but in that case why single out Google alone? From wiki:
>The governing members of the Alliance for Open Media are Amazon, Apple, ARM, Cisco, Facebook, Google, Huawei, Intel, Microsoft, Mozilla, Netflix, Nvidia, Samsung Electronics and Tencent.
Like, Google is certainly significant, but that's a lot of equally heavy hitters. And interesting that Mozilla is there too.
----
0: https://github.com/AOMediaCodec/libavif
-
JPEG XL support has officially been removed from Chromium
> You have a good point that AVIF layered image items can act like such P/B-frames. Do libavif (or other AVIF implementations if any) make use of them?
Seemingly. As search for "libavif progressive encoding" shows several issues about this, and a search for "progressive" in https://github.com/AOMediaCodec/libavif/blob/main/include/av... shows an enum for avifProgressiveState, appears to show support for it.
-
Wavif discussion
I mean, it already has it: https://github.com/AOMediaCodec/libavif/commit/570c42c2c10a878c8cc896f1c5daf1a955274142
-
Animated AVIF and JXL tools for Windows
Apart from mpv and ffplay, the only software I currently have installed that can play animated AVIF is Chromium. And from what I've read from this libavif bug report, I'm not sure if looping animated files in general is something that's just done by default by a lot of software regardless of whether the file is marked as a loop or not.
-
How to create progressive AVIF images?
The support for progressive AVIF decoding has landed in libavif and in Chromium. But are there any docs on how to create and test progressive AVIF images?
-
The Case for JPEG XL
The "for example" is the key here, because AVIF does support multi-layer coding per the spec now (though not currently implemented in libavif from what I can tell).
-
Google Outlines Why They Are Removing JPEG-XL Support From Chrome
libavif is at version 0.11.1, see https://github.com/AOMediaCodec/libavif/tags
What are some alternatives?
rav1e - The fastest and safest AV1 encoder.
gimp-avif-plugin - Plug-in for development GIMP 2.99.11 for loading/saving AVIF images.
cavif-rs - AVIF image creator in pure Rust
xviewer - A generic Image viewer
av1-avif - AV1 Image File Format Specification - ISO-BMFF/HEIF derivative
qt-jpegxl-image-plugin - Qt plug-in to allow Qt and KDE based applications to read/write JXL images.
libjxl - JPEG XL image format reference implementation
org.gimp.GIMP
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
lxqt-archiver - A simple & lightweight desktop-agnostic Qt file archiver
benchmarks - Test images and results of compression benchmarks.