SVT-AV1
ffmpeg-windows-build-helpers
Our great sponsors
SVT-AV1 | ffmpeg-windows-build-helpers | |
---|---|---|
176 | 9 | |
- | 1,050 | |
- | - | |
- | 7.3 | |
- | 16 days ago | |
Shell | ||
- | GNU General Public License v3.0 only |
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 ?
ffmpeg-windows-build-helpers
-
Can't cross compile lensfun module with rdp ffmpeg-windows-build-helper
$ git clone https://github.com/rdp/ffmpeg-windows-build-helpers.git $ cd ffmpeg-windows-build-helpers $ ./cross_compile_ffmpeg.sh --disable-nonfree=n --compiler-flavors=multi
-
Can anyone tell me how you compile ffmpeg from a GitHub version, preferably into a static build?
ffmpeg has the option to build in quite a few dependencies / external libraries, so it's rather complex. Last time I did it I used https://github.com/rdp/ffmpeg-windows-build-helpers but there are other build scripts on GitHub that also seem like they'd be good
- Struggling with compilation on Mac
-
SVT-AV1 v1.1.0 released
I recommend the ffmpeg windows build helpers and simply build your own.
-
help installing FFMPEG on windows with NVidia GPU support
If you do want to compile yourself, there's a more thorough build script here https://github.com/rdp/ffmpeg-windows-build-helpers
-
patching ffmpeg on windows
I've run into this situation myself, and in order to generate a version of the ffmpeg executable with the change I wanted I used VirtualBox to spin up a virtual linux machine, and then used https://github.com/rdp/ffmpeg-windows-build-helpers this script to build a new binary (adding in the diff patch at the appropriate point). It's an informative process, you learn a lot about how software is taken from source code into something usable, but if you're new to that world I wouldn't recommend taking it lightly. It took me a few solid days of work before I had a binary I could actually use.
-
yt-dlp release 2021.09.02
For Windows I've used: https://github.com/rdp/ffmpeg-windows-build-helpers. (cross-compiling on Linux)
-
Adding patch to custom build
use a build script that someone else has put together. Don't try and do it yourself. Ffmpeg with all the usual libraries takes sooo many parts, that way madness lies. I had a lot of luck with https://github.com/rdp/ffmpeg-windows-build-helpers but I have no idea if that's better or worse than other options. Maybe u/_gyan has some advice there
-
error: could not find jni.h
I tried googling up the issue and came across a very outdated solution for a file which I cannot find because the wiki says is deprecated https://github.com/rdp/ffmpeg-windows-build-helpers/issues/268
What are some alternatives?
Av1an - Cross-platform command-line AV1 / VP9 / HEVC / H264 encoding framework with per scene quality encoding
media-autobuild_suite - This Windows Batchscript helps setup a Mingw-w64 compiler environment for building ffmpeg and other media tools under Windows.
rav1e - The fastest and safest AV1 encoder.
ffmpeg-apple-arm64-build - Build script for ffmpeg targeting the latest open source video codecs running on macOS using Apple's M1 processor.
FFmpeg-Builds
yt-dlp - A feature-rich command-line audio/video downloader
ffmpeg
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.
FFMPEG-HD-GXF - patches providing HD resolution GXF support for FFMPEG
ab-av1 - AV1 re-encoding using ffmpeg, svt-av1 & vmaf.
FFmpeg - Mirror of https://git.ffmpeg.org/ffmpeg.git