SVT-AV1
Av1an
Our great sponsors
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.
SVT-AV1
-
Any recent comparison between the encoders, specially rav1e and SVT-AV1?
The docs mention that the unit for this option is in "frames" (not "seconds").
-
SVT-AV1 git: Neon optimizations across all processes - part2
From the pull request:
- SVT-AV1 git: Updating encoding parameters during the encoding session (RTC only)
-
Guide to Adopting AV1 Encoding
In these tests SVT-AV1 beats x265 on quality:
- FullHD: http://compression.ru/video/codec_comparison/2022/main_repor...
- FullHD 10-bit: http://compression.ru/video/codec_comparison/2022/10_bit_rep...
- 4K: http://compression.ru/video/codec_comparison/2022/4k_report....
SVT-AV1 has seen a number of speed ups in recent releases:
-
10-bit and 4:2:2 Chroma Subsampling support for AV1?
I don't see this options under the "Advanced features" like for H.265/HEVC (for example). Also, adding "-input-depth 10" manually to the command line doesn't work (it doesn't recognize the parameter, despite it clearly being written here as one of them).
-
Does Handbrake publish AV1 documents?
Docs for SVT-AV1 at https://gitlab.com/AOMediaCodec/SVT-AV1/-/tree/master/Docs
-
[SVT-AV1 Git] The experimental SSIM RD tune in SVT-AV1 has been added to mainline
I find it interesting that you know the project well enough to get to the pre-compiled binaries page, yet somehow missed that the merge request explictly calls out a VMAF LOSS for the SSIM tune by several percentage points.
-
What's the status of AV1 encoding on ARM?
SVT-AV1 has no NEON.
-
My AV1 testing (Part 3)
I used the precompiled FFmpeg from SVT-AV1's git: https://gitlab.com/AOMediaCodec/SVT-AV1/-/jobs/4540276837
- SVT-AV1 1.6.0 windows x64 binaries ?
Av1an
-
Guide to Adopting AV1 Encoding
The hardware encoders are very fast and generally better than x264 (but not by as much as you'd think with the x264 slow preset).
In addition, there are threaded AV1 encoders you may be overlooking, like SVT-AV1. For non-realtime, my favorite is av1an, which also yields better quality than is possible from aomenc: https://github.com/master-of-zen/Av1an
-
I have a feeling crunchyroll should be using AV1
I specifically used https://github.com/master-of-zen/Av1an with --target-quality 100 to keep the compression as close to lossless as possible (you could probably shave even more size off if you didn’t use near-lossless compression)
-
Automatic choose encode settings?
There's also Av1an as suggested by someone else. It's going to produce more efficient encodes because it uses chunk-based encoding to reach the required VMAF for every single chunk, but this is also slower because every chunk will be re-encoded until the VMAF target is reached. It's also a PITA to compile, has a long list of bugs, and isn't very actively developed. One of the long-standing issues is that frames have a tendency to go missing during splitting, which IME is going to keep happening when the input files aren't standardized. And thus the recommendation is to transcode the input to lossless first, which is just completely unsustainable.
-
Building pc for ffmpeg rendering
i'm still trying to figure out if av1an is the breakthrough to using large CPU counts without losing quality. but it's a ridiculously poorly documented program. i haven't gotten it to run effectively yet. https://github.com/master-of-zen/Av1an
-
Codecs for the 4K Era: HEVC, AV1, VVC and Beyond
I don't know about VVC, but I've never seen a recommendation of preset 0 for SVT-AV1. The docs say "presets 1-3 represent extremely high efficiency, for use when encode time is not important and quality/size of the resulting video file is critical". It seems like 0 is the equivalent placebo preset. But if you want AV1 with coding efficiency over all else, IIRC the typical approach is to use av1an to detect scene transitions and farm out parallel encodes with aomenc.
-
Automating av1 encoding?
That might be because it doesn't work.
-
VMAF is confusing me
Have you seen Av1an? It's supposed to encode to a target VMAF.
-
Trying to use av1an without success
Are you using the current version, 0.4.0, from https://github.com/master-of-zen/Av1an/releases
- Av1an - Cross-platform command-line AV1 encoding framework written in Rust
- Av1an: Cross-platform command-line AV1 encoding framework written in Rust
What are some alternatives?
rav1e - The fastest and safest AV1 encoder.
HandBrake - HandBrake's main development repository
FFmpeg-Builds
FastFlix - FastFlix is a free GUI for HEVC and AV1 encoding, GIF/WebP/AVIF creation, and more!
aom-av1-lavish - A fork of aom-av1-psy, which is a fork of aomenc. Designed to open up the encoder for hyper-tuning and fidelity.
NotEnoughAV1Encodes - GUI for AV1 (aomenc, rav1e & svt-av1)
media-autobuild_suite - This Windows Batchscript helps setup a Mingw-w64 compiler environment for building ffmpeg and other media tools under Windows.
ab-av1 - AV1 re-encoding using ffmpeg, svt-av1 & vmaf.
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
nmkoder - Media encoding, muxing, analysis toolkit for Windows