r/AV1 • u/juliobbv • 1d ago
SVT-AV1-HDR 4.3.0 "Crankcase" is out!
r/AV1 • u/Farranor • Aug 02 '25
This post will help you get started with AV1.
Noteworthy posts:
Links:
Related subs:
r/AV1 • u/shreytyagi • 6d ago
Can you believe that YouTube's HDR AV1 encoding now has better bitrates and a superior codec than even AppleTV?😳
New researched article: https://shreytyagi.com/articles/youtubeav1encoding/index.html
r/AV1 • u/ExpressPost5048 • 7d ago
I am finding that modern movies shot on digital cameras can get you some extreme compression ratios.
Example: andor 4k. I own the 4k blu ray of it. One episode is 21.4gb
On av1-svt preset 3 and q26. Audio is 128kbs opus stereo.
Size: 509mb. 2.3% of the original file size. That is a 43:1 compression ratio.
r/AV1 • u/ProfessionalDish • 7d ago
Saw that the last build of HandBrake-SVT-AV1-Tritium was about two weeks ago. Considering 4.3.0 dropped last week (https://gitlab.com/AOMediaCodec/SVT-AV1/-/releases/v4.3.0) I'm hesitant to start new batches of encodes. Anyone knows something about the state of the tritium fork?
r/AV1 • u/Appropriate-Ice7937 • 8d ago
AV2, the AOMedia codec that follows AV1, already has a software decoder in VideoLAN's dav2d, but FFmpeg's main branch had no AV2 decoder at the end of October, so mpv and the players built on libmpv cannot open AV2 files on their own.
I wrote a small program for the desktop version of my open source player, Immuch360, that closes that gap without touching the player: it decodes with dav2d and serves the pictures as a raw y4m stream over HTTP, on 127.0.0.1 only. mpv opens that address like a file, seeks included. It now has a repository of its own, under the MIT licence: https://github.com/immuch360/av2-companion
What it is:
With Python 3.9 or later and mpv, unzip the archive of your system from the latest release, clone the repository, then:
python3 av2-companion/tools/feed_ivf.py video.ivf --program av2/immuch360-av2 --playWithout --play it prints the address and the mpv command, for any other player. The README describes the protocol for a player that wants to drive the program itself.
What it is not:
Speed is the real limit. Measured with dav2d alone, in multiples of real time:
| CPU | 1080p30 8-bit | 4K30 8-bit | 1080p30 10-bit | 4K24 10-bit |
|---|---|---|---|---|
| Intel Core i5-1145G7, 4 cores | 4.0x | 1.24x | 1.20x | 0.31x |
| Intel Core i9-13980HX, 24 cores | 7.7x | 0.99x |
8-bit plays up to 4K30 on a recent 4 core laptop. 10-bit is three to four times slower, because the SIMD code of dav2d's loop filters exists in 8 bits only for now, so 10-bit 4K needs a high end processor and is at its limit even there. Below 1.0x the video stalls.
If you only want to check a clip, dav2d's own command line tool can already write y4m to standard output. This program is for players: seeks, and an address they can open without any change to their decoding.
The test streams decode bit for bit like the reference decoder of AVM v1.0.0. Reports on other streams and other CPUs are welcome.
r/AV1 • u/Busy_Connection_8027 • 8d ago
Is there an encoder out there that is free to use that can encode to av2? The compression of av1 it's so good I can compress a whole episode of family Guy and keep same resolution set the compression to 23 epe are around 35 to 60 megabytes and from original dvd vob via hand break the .mkv almost looks if not identical to the same quality as the original DVD
So I wanted to test out the av2 compression if possible
r/AV1 • u/LITUATUI • 15d ago
Hi guys.
It seems that AV1 support in MPEG-2 TS is almost here. I've been waiting for years.
https://github.com/AOMediaCodec/av1-mpeg2-ts#known-implementations
Maybe next year we'll see some TV channels changing their official online broadcasts from AVC to AV1.
Looking forward for the FFmpeg implementation, then I could use Dispatcharr to transcode to AV1 the local streams that I get from DVB tuners with TVHeadend.
r/AV1 • u/maddog107 • 18d ago
I needed to convert about 15 million forum photos to AVIF without tying up the server's CPUs, so I wrote av1gpu, an AV1 still-image encoder that runs entirely on CUDA cores (not NVENC).
Speed vs file size, every setting: https://github.com/maddog107/av1gpu/blob/main/docs/charts/tradeoff-light.svg
On one NVIDIA L4, against the same 16-thread EPYC CPU:
| Encoder | MP/s | Files vs libaom speed 6 |
|---|---|---|
| av1gpu (default) | 116 | −0.1 % |
| av1gpu turbo3 | 212 | +5.4 % |
| libaom speed 6 (16 threads) | 29 | 0 % |
| SVT-AV1 preset 4 / 6 / 9 | 15.5 / 49 / 183 | −2.6 / +2.1 / +9.8 % |
| NVENC AV1 (same L4) | 16 | +29.5 % |
- Quality is scored as BD-rate on SSIMULACRA2 over 100 photos. Scripts and raw results are in the repo.
- av1gpu uses about 0.1 of a CPU core while encoding. The 100 photos went from 160 MB of JPEG to 22.5 MB of AVIF (−86 %).
- Prebuilt Linux binary, BSD-2: https://github.com/maddog107/av1gpu
No alpha channel yet. Happy to benchmark anything else people want to see.
r/AV1 • u/divergent5482520498 • 19d ago
I can't find much information for encoding performance with the latest SVT-AV1 on Apple silicon. Those of you with devices do you mind sharing preset 2 or 4 speed at 1080p or 4k? Especially interested in M4 and M5 devices
Edit: forgot to mention please use up to date plain svt-av1 with CRF 30
r/AV1 • u/stackpointer101 • 20d ago
AV1 HW decoders obviously can't fully decode AV2, because the bit stream changed significantly. But, as far as I understand, quite a few of the general building blocks of AV1 are also present in AV2, maybe with slightly changed parameters.
Are there some significant parts in the AV2 codec that the AV1 HW decoder blocks could accelerate? Could a software decoder like dav2d use these AV1 HW decoder features to lift some of the workload of the CPU? Or will software solutions have to rely 100% on CPU execution, until a real AV2 decoder appears in HW?
r/AV1 • u/SchoolWeak1712 • 24d ago
I recently watched dune on netflix and noticed that the black bars on the top and bottom looked a bit odd. Checked it on my PC again today and there is definitely some grain synthesis applied to the letterbox.
2. image is zoomed in and
3. image is edited for better visibility
Why didn't they cut off the bars before encoding?
r/AV1 • u/beeftendon • 24d ago
I'm looking at reencoding some very grainy source video using svt-av1-tritium, since it has the svt-av1-hdr feature set along with some extra stuff from other encoders like SCD. I also saw that it has an enable-daala parameter and was wondering if it might be helpful for grain preservation in some more challenging cases (e.g. reducing quantization in specific areas within the frame) as an alternative to just cranking down the CRF. Mainly asking since I don't really know the theoretical underpinnings of it, and how it may help/hurt things in the context of also using svt-av1-hdr's grain tune.
r/AV1 • u/better_life_please • 24d ago
I saw a new release of SVT. Is it anything special?
r/AV1 • u/-protonsandneutrons- • 25d ago
OK I lied, this will likely be the last major release of VideoMetricsLab. not v2.0. I will still do little things here and there, but releases will be much slower going forward, for real this time! I don't even know what else to do to improve this app anymore anyways.
v2.1
v2.2
--fps to compare raw video streams (.264, .265, .266, .obu and others), and --size and --pix-fmt (with --fps) for raw .yuv files.Download here
r/AV1 • u/collin3000 • 26d ago
Although CVVDP is the current front runner metric for visual analysis if motion video there is a quirk that I think is significant enough that it warrants community discussion. That is the default handling methodology of video below the screen resolution or below the default standardized display resolution.
With the default handling of video lower than the screen resolution (or standardized display preset) CVVDP assumes and grades the video as if the video is taking up that portion of the screen rather than the full screen. This seems problematic as there is plenty of older content (DVD's, TV shows) that would only be 360p-720p yet someone would likely be viewing full screen on a 1080p or higher display.
Why this matters for psychovisual tuning: When using psychometric tuning and output is scored with traditional CVVDP methodology the perceived viewing angle/pixel size discounts the loss of fine detail that would actually be visible when viewed full screen . Using the AOM media set 270p/360p/720p video encoded viewed at full screen had a significant variation range in score when scaled to full screen.
For example, this is the data on six 360p videos using the standardized FHD display profile. Videos were encoded on preset 5 with CRF 15. The latest SVT-AV1 4.2.0 and SVT-AV1-HDR fork were used.
| Scoring Method | Stock SVT AV1 4.2.0 JOD (3247 kbps) | SVT-AV1-HDR (2931 kbps) | HDR vs Stock bits per JOD difference |
|---|---|---|---|
| Default (Native Size) | 9.883 | 9.894 | -9.83% |
| Fullscreen, no scaler | 9.64 | 9.455 | -7.97% |
| Fullscreen, nearest neighbour | 9.557 | 9.393 | -8.16% |
| Fullscreen, bilinear | 9.67 | 9.588 | -8.96% |
| Fullscreen, bicubic | 9.58 | 9.469 | -8.67% |
| Fullscreen, spline | 9.551 | 9.421 | -8.49% |
| Fullscreen, Lanczos | 9.537 | 9.406 | -8.47% |
Note: A linear formula of JOD per kbps was used for this post rather than extrapolated curves. Since there was not always an overlap for good extrapolation. The full data set contains the extrapolated curve difference
Various scaling methods are presented because of how different video players may upscale the lower resolution video when viewed full screen. The most important part is that when viewed full screen the most favorable scaling methodology (bilinear) drops by 0.213 JOD.
The difference increases with lower video encoding quality. Those same clips at CRF 35 place native size at 9.501 JOD, and full screen bilinear scaled at 8.849. A l0.652 JOD difference. That difference is greater than going from CRF 15 to CRF 35 at the current native methodology.
For people watching lower resolution content at full screen that makes a significant difference in what RF or bitrate setting they may choose when encoding.
CRF 15, Preset 5
| Scoring Method | Stock SVT AV1 4.2.0 JOD (7837 kbps) | SVT-AV1-HDR (10826 kbps) | HDR vs Stock bits per JOD difference |
|---|---|---|---|
| Default (Native Size) | 9.846 | 9.911 | 37.23% |
| Fullscreen, no scaler | 9.734 | 9.84 | 36.65% |
| Fullscreen, bilinear | 9.769 | 9.835 | 37.21% |
| Fullscreen, bicubic | 9.703 | 9.775 | 37.12% |
| Fullscreen, Lanczos | 9.684 | 9.754 | 37.15% |
CRF 25, Preset 5
| Scoring Method | Stock SVT AV1 4.2.0 JOD (3292 kbps) | SVT-AV1-HDR (4195 kbps) | HDR vs Stock bits per JOD difference |
|---|---|---|---|
| Default (Native Size) | 9.75 | 9.81 | 26.65% |
| Fullscreen, no scaler | 9.602 | 9.688 | 26.3% |
| Fullscreen, bilinear | 9.628 | 9.695 | 26.55% |
| Fullscreen, bicubic | 9.534 | 9.607 | 26.46% |
| Fullscreen, Lanczos | 9.508 | 9.58 | 26.47% |
CRF 45 places native size at 9.062 JOD and full screen bilinear scaled at 8.694. That gives a significant 0.368 JOD difference. Worth ~15 CRF steps in decision making.
None of this discounts CVVDP. However I think it warrants community discussion and input. On whether the current method of scoring video that is a lower resolution than the display at it's native resolution should continue to be the standard methodology. Or if full screen scaled should be adopted as a community standard. Especially when considering that the scoring is for people interested in encoding while keeping visual fidelity that they will likely be viewing that video at full screen.
If a change is warranted then the question is; Should full screen be considered no scaler. Or should full screen be considered with a middle-ground default scalar algorithm.
Curious to hear everyone's thoughts.
r/AV1 • u/AccomplishedEye8352 • 28d ago
r/AV1 • u/ExpressPost5048 • Oct 18 '26
I have been ripping and compressing my blu ray collection into the AV1 format for file space savings. Some of them can be massive like a 90% compression.
I'm wondering what is the best hardware encoder for this. I have been using an Intel Lunar Lake CPU and the IGP on it. In handbrake I set it to the highest quality on most things but will set the q between 22 and 26. I have also been encoding the audio into opus stereo. No subtitles saved except for foreign films.
I'm wondering if maybe the nvidia AV1 hardware encoder is better, or if the snapdragon or apple hardware encoders are better. I also wonder about software encoding. If software encoding were 2x as long as hardware encoding that would be okay but it ends up being 10x as long.
So to recap, I've been using an intel Lunar Lake CPU's hardware AV1 encoder to compress my movie collection into AV1. I'm curious if there is a better encoder to use out there that can compress a movie in a reasonable amount of time.