rav1e
libavif
Our great sponsors
- InfluxDB - Access the most powerful time series database as a service
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- CodiumAI - TestGPT | Generating meaningful tests for busy devs
- SonarLint - Clean code begins in your IDE with SonarLint
rav1e | libavif | |
---|---|---|
69 | 42 | |
3,232 | 1,104 | |
2.7% | 4.5% | |
9.4 | 8.6 | |
3 days ago | 7 days ago | |
Assembly | 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.
rav1e
- Any new Opensource projects in (rust) looking for contributors. I want to start my journey as an OSS contributor.
-
A little script to parse large libraries to AV1, if you're interested
You can speed up the sampling process with --vmaf n_subsample=5, which in my experience works more accurately than either 2 or 4, possibly due to this bug/feature present in multiple encoders. You might also need to manually set the number of threads used for VMAF calculation with --vmaf n_threads=16, but YMMV.
-
rav1d: a Rust port of dav1d (currently experimental)
That remember me of https://github.com/xiph/rav1e which is an AV1 encoder
-
HDR10, HDR10+, Dolby Vision with AV1?
It's getting there.. Initial steps for FFmepg: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8444 rav1e: https://github.com/xiph/rav1e/pull/3000
-
Use HW hevc encoding for first pass · Issue #2945 · xiph/rav1e
I doubt much will be done on such an exotic feature any time soon. Progress has been slow on rav1e, it's missing a lot of features, and only supports tile threading.
-
Announcing Rust 1.67.0
rav1e is quite well maintained, the fix for the lint was merged days after the ilog PR merged. But the 0.5.1 release of rav1e was one year ago, in December 2021, while the ilog rename was end of August 2022. There hadn't been a release though of rav1e until end of November 2022, which was also a semver incompatible one. Users had only 2-ish months of time to get to the new rav1e version without experiencing breakage.
-
Symphonia: Audio decoding in safe Rust, now often faster than FFmpeg!
The rav1e encoder for AV1 has more assembly in it than Rust, which also doesn't bode well for memory-safe video codec implementations. But this might change once Rust provides portable and memory-safe explicit SIMD.
- .Webp is the bane of my existence
-
I built a Zoom clone 100% IN RUST
Obviously not super important, but would be super cool to see AV1 encode/decode support added. There's a great rust library for this too : https://github.com/xiph/rav1e
libavif
-
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.
----
-
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.
-
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.
-
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
-
[libavif git] libavif 0.11.0 RC (release candidate) has been released
AV1 encoders in libavif apparently now have access to autotiling as an option, which automatically sets the number of tiles in a frame based on frame area: https://github.com/AOMediaCodec/libavif/commit/ff322862b708e505349c9396fdcf7aaec9123f47
- Losslessly Optimising Images
-
What is AVIF?
The Alliance for Open Media's AVIF encoding and decoding library is also in a Github repo. Sharp, a Node module, has AVIF support. To make AVIF images, you can use avif.io, Squoosh, and the Squoosh command line tool aimed at supporting Node.js apps. GIMP and Paint.net support AVIF and there are Photoshop plugins. Mac has no plans to support AVIF, but you can easily install a codec plugin on Windows 10 for native support.
-
How can I install avifenc on Ubuntu 20.04?
git clone --depth 1 https://github.com/AOMediaCodec/libavif.git
What are some alternatives?
SVT-AV1
dav1d - A read-only mirror of dav1d source code repository. The origin is at https://code.videolan.org/videolan/dav1d/
ffmpeg-build-script - The FFmpeg build script provides an easy way to build a static FFmpeg on OSX and Linux with non-free codecs included.
obs-amd-encoder - AMD Advanced Media Framework Encoder Plugin for Open Broadcaster Studio
cavif-rs - AVIF image creator in pure Rust
SVT-AV1 - Welcome to the GitHub repo for the SVT-AV1! This repo is set to read-only for archiving purposes. Please join us at https://gitlab.com/AOMediaCodec/SVT-AV1. We look forward to seeing you there
av1-avif - AV1 Image File Format Specification - ISO-BMFF/HEIF derivative
broot - A new way to see and navigate directory trees : https://dystroy.org/broot
qt-avif-image-plugin - Qt plug-in to allow Qt and KDE based applications to read/write AVIF images.
vvenc - Fraunhofer Versatile Video Encoder (VVenC)
av-scenechange - Scenechange detection tool
libjxl - JPEG XL image format reference implementation