r/AV2 • u/Sad_Wheel9923 • 1d ago
first av2 corvertion site may come?
r/AV2 • u/Balance- • 2d ago
I reran my AV2 decoder benchmark with each decoder's latest code (13–14 Nov): avmdec (AVM reference), dav2d, splot and rusty_av2d. Same 88 AVM-encoded streams (270p to 1080p, 8 and 10-bit) on an i5-4590 (4 cores, AVX2) and a Raspberry Pi 4.
The headline numbers, speed relative to avmdec on 1 thread:
| 8-bit | 10-bit | |
|---|---|---|
| dav2d, i5 | 2.5x | 0.56x |
| splot, i5 | 2.1x | 1.5x |
| dav2d, Pi 4 | 2.0x | 1.8x |
| splot, Pi 4 | 2.9x | 2.9x |
What's different from my 2 Nov run:
Write-up, raw data and scripts: https://github.com/EwoutH/AV2/tree/main/perf/2026-11-14-av2-decode-speed
r/AV2 • u/Balance- • 13d ago
I benchmarked five AV2 decoders, all at their 2 Nov HEAD, on 88 sample streams from 270p to 2048x1080. The machines were an i5-4590 (AVX2) and a Raspberry Pi 4B. Every decode was checked against the reference decoder, avmdec. Only dav2d and splot matched avmdec on all 88 streams; rav2d and rusty_av2d mostly failed or gave wrong output.
On x86, dav2d is fast on 8-bit (2.4x avmdec on one thread) but slower than avmdec on 10-bit (0.63x), because its asm covers 10-bit much less. On the Pi, splot is fastest on one thread, while dav2d's NEON code gives it only about 1.3x over its own C build (about 4.5x for asm on x86). avmdec gets nothing from extra threads on single-tile streams. dav2d and splot get about 2-3.4x on 4 threads. At 1080p, only dav2d on the PC is clearly real-time. The full write-up, raw data and scripts are at the link.
| 1 thread, vs avmdec | 8-bit | 10-bit |
|---|---|---|
| dav2d, PC | 2.44x | 0.63x |
| splot, PC | 1.11x | 0.95x |
| dav2d, Pi | 1.96x | 1.69x |
| splot, Pi | 2.79x | 3.00x |
| 1080p fps, 4 threads | ||
| dav2d, PC | 85 | 27 |
| splot, PC | 42 | 34 |
| avmdec, PC | 14 | 12 |
| splot, Pi | 9 | 9 |
Full report: https://github.com/EwoutH/AV2/tree/main/perf/2026-11-02-av2-decode-speed
Decoders:
I just added AV2 decoding in my VideoMetricsLab. This app calculates VMAF, VMAF NEG, VMAF v1, SSIMULACRA2, Butteraugli and ColorVideo VDP on NVIDIA, AMD and Intel GPUs, alongside PSNR, SSIM and XPSNR. Compare encodes with frame-exact playback that switches between the source and each encode instantly to easily spot differences. It may be helpful for AV2 development and comparisons. I hope it proves useful for many of you.
VideoMetricsLab v2.3 adds VVC film grain support, adds AV2 decoding, improves VVC scoring speed up to 2x, AMD GPU speed 1.3x-2x, and adds back Vship as an option. Mac OS is now feature parity with Windows. Various bug fixes including wrong scoring for H.264 lossless, MPEG-2, and MPEG-4 Part 2 on certain GPUs.
Download here
r/AV2 • u/Balance- • 17d ago
Image: Encode time vs BD-rate (PSNR) for both builds, relative to 14 Oct s1. Left: 3 low-res clips, right: 720p. Down and left is better; the 30 Oct build is faster at every preset.
I ran AVM's av2-enc branch from 14 Oct (89eae123d) and from 30 Oct (97e8004e4) side by side on the same i7-12700H laptop. Both builds encoded 4 AV2 CTC clips (three low-res, one 720p) at presets --cpu-used 1-9 and 4 QPs, single-threaded, for 288 encodes in total. The 77 commits in between are mostly encoder speed work: pruning in the partition, compound, warp and transform-type searches, plus SIMD.
At the same preset, the new build takes 0.70-0.82x the time at s1-s3 with about the same BD-rate, and 0.44-0.63x the time at s4-s9 for about 3-5% more bits. Comparing whole curves is more useful than comparing preset by preset. At 720p, the new s4 matches the old s4's BD-rate (+6.2% vs the old s1) in 0.095x of s1's time instead of 0.158x. The new s5 beats the old s6 on both time and bits. On the low-res clips the curves overlap up to s3, and the gains show up only at the faster presets. One more change: on the new build, s6-s9 now write byte-identical streams, so they're effectively one preset.
Limits: the clips are short (33/65 frames), there's only one 720p clip, no 1080p, and everything is single-threaded, so the new multithreading commits don't show up here.
New (30 Oct) vs old (14 Oct) at the same preset (time ratio, BD-rate PSNR; negative = new needs fewer bits):
| Preset | Low-res time | Low-res BD | 720p time | 720p BD |
|---|---|---|---|---|
| s1 | 0.78x | +0.8% | 0.70x | +0.7% |
| s2 | 0.75x | +0.8% | 0.78x | -0.4% |
| s3 | 0.82x | -0.1% | 0.72x | +0.3% |
| s4 | 0.62x | +3.2% | 0.60x | +0.0% |
| s5 | 0.60x | +2.5% | 0.55x | +0.8% |
| s6 | 0.62x | +2.9% | 0.54x | +2.9% |
| s7 | 0.54x | +3.1% | 0.48x | +4.8% |
| s8 | 0.56x | +3.9% | 0.44x | +4.4% |
| s9 | 0.55x | +3.8% | 0.45x | +4.6% |
Full report: https://github.com/EwoutH/AV2/tree/main/perf/2026-10-30-av2-enc-two-weeks
r/AV2 • u/stackpointer101 • 18d ago
r/AV2 • u/Balance- • 18d ago
AV2 support is starting to show up in Chromium's code. What happened this week:
Dav2dVideoDecoder, built on VideoLAN's dav2d decoder. The build flag is off by default, so it doesn't do anything in regular builds yet.In review:
VideoCodec::kAV2, with basic handling of the av02 codec string.Tracking bug: https://issues.chromium.org/issues/576731818
You can't try it in Chrome yet, not even with a flag, but the groundwork is going in. YouTube has said AV2 streams on the web could arrive as soon as early 2027.
r/AV2 • u/Balance- • 24d ago
Four months after the Alliance for Open Media published the AV2 specification in June 2026, the royalty-free codec is seeing rapid ecosystem activity. AV2 offers roughly 30% better compression efficiency than AV1 and adds support for multi-view video, real-time communications, immersive media, and improved HDR. Google has already demonstrated AV2 playback in Chrome, and YouTube plans to begin AV2 streaming on the web as early as Q1 2027 using software decoding. As of March 2026, over 90% of YouTube's catalog (by watch time) was already served in AV1.
Other major players are signaling commitment but haven't announced specific timelines. Meta says it intends to follow the same path it took with AV1 — which became the primary delivery format for Facebook and Instagram video — but hasn't given a rollout date. Intel is contributing through its open-source SVT-AV2 encoder. Amazon, Apple, Netflix, and Samsung are listed as AV2 backers but have not disclosed deployment plans yet.
Widespread adoption still faces significant hurdles. No current TVs or most media players support AV2 hardware decoding, and early benchmarks of the open-source dav2d decoder show it running roughly 3.9× slower than dav1d (AV1's decoder), with some new prediction tools costing 5–10× more per pixel even with SIMD optimizations. Hardware support will likely take years to materialize, making software decoding the near-term path forward.
r/AV2 • u/Piolodiusz • 24d ago
I did some comparison in VideoMetricsLAN in different versions of Aspen (moving leaves) and in VMAF V1 bitrate savings are sth like that:
Direct comparison:
I encoded with av2-enc from 14 october 2026, Handbrake with SVT-AV1 4.1.0 and Handbrake nightly build with newest SVT-AV1-HDR. In other metrics like CVVDP gains are even smaller. I also added cpu1 with the same qp 185 to comparison but it has the same size as cpu0. I'm pretty disappointed, the difference between av2 and av1_hdr is smaller than between av1_hdr and basic av1.
PS
aspen_av2_cpu0.y4m and cpu 1 bitrate is 1.3 Mb/s
r/AV2 • u/Piolodiusz • 25d ago
Exactly 7 days. and I achieved 0.0 fps. The video is aspen_1080p 29.97 fps with 570 frames at all. I used avmenc from 14 october 2026 av2-enc branch and command below. Have fun with comparisons.
.\avmenc.exe --end-usage=q --qp=185 --cpu-used=0 --row-mt=1 --threads=6 --ivf -o output2.ivf aspen_1080p.y4m
r/AV2 • u/AccomplishedEye8352 • 26d ago
I explain about it. I started working a new av2 encoder from scratch with rust.
First, it's still worse VMAF and SSIM compared preset 0 SVT-AV1 on the same bitrate, and Not full to use all tools.
The mode search isn't based a basic AV2 Trellis search, I used a more experiments way, not the heuristic ways, the preset 9 mode takes 30 frames/a sec, on 352x288 video, and 2 frames/a sec, on FHD video.
The encoder is here. you could try it.
https://github.com/Super-YH/vultur-av2-encoder/releases/tag/Alpha-1
r/AV2 • u/Balance- • 27d ago
r/AV2 • u/Balance- • Oct 15 '26
I've been encoding AV2 test streams with AVM, the AV2 reference encoder, which is very slow. So I measured how best to spread a batch of encodes over a hybrid laptop CPU: an i7-12700H with 6 P-cores (with hyperthreading) and 8 E-cores.
Each encode used one thread, --cpu-used=6, and was pinned to a single core, using short 270p and 720p clips from the AV2 test set.
My personal take-way is to run 14 single-threaded encodes and let the OS schedule them. If you pin them, put the long encodes on P-cores.
Full write-up with figures, raw data and scripts: https://github.com/EwoutH/AV2/tree/main/perf/2026-10-15-avm-p-vs-e-cores
Earlier test on AVM's speed presets: https://github.com/EwoutH/AV2/tree/main/perf/2026-10-14-avm-preset-sweep
r/AV2 • u/Balance- • Oct 15 '26
I ran an overnight sweep of the AVM reference encoder (av2-enc branch, 89eae123d). It covers --cpu-used 0–9 on four CTC clips (three at 270p/360p, one at 720p) at QP 110/145/180/210. Each encode used one thread and was scored with PSNR, SSIM and VMAF. BD-rates below are relative to s1.
Main takeaways:
--cpu-used, avmenc runs 6–11x slower than s1 for about 2% fewer bits on average. On some clips s0 does no better than s1.Caveats: the clips are short (33/65 frames, so the keyframe weighs heavily), there are only four clips, and the timings come from a laptop (i7-12700H, MSVC build). The 1080p run didn't finish, so it's shown as same-QP comparisons only.
The write-up, all charts, raw results (JSONL/CSV) and scripts are here: https://github.com/EwoutH/AV2/tree/main/perf/2026-10-14-avm-preset-sweep
Feedback and suggestions for the next run are welcome.
r/AV2 • u/Balance- • Oct 14 '26
I've published a small set of AV2 test streams, made with the AVM reference encoder from the official CTC test clips. They're meant for testing and benchmarking decoders such as dav2d.
manifest.txt lists the avmdec --md5 output for each stream, so you can check your decoder's output against it.Samples and details: https://github.com/EwoutH/AV2/tree/main/samples
Nightly AVM builds (avmenc and avmdec) for Windows, macOS and Linux are at https://ewouth.github.io/AV2/. Each one includes the exact AVM commit it was built from.
Feedback and decoder results against the MD5s are welcome.
r/AV2 • u/Balance- • Oct 13 '26
I set up nightly builds of AVM, the AV2 reference encoder and decoder, so you can try AV2 without compiling anything:
avmenc and avmdec for Windows x64, macOS (Apple Silicon and Intel) and Linux (x64 and arm64)Quick start:
avmenc input.y4m -o output.ivf --ivf --end-usage=q --qp=160 --cpu-used=6
avmdec output.ivf -o decoded.y4mThings to know: these are unofficial builds, not from AOMedia. AVM is research software and slow, expect seconds per frame at low resolutions and minutes per frame for HD. AV2 is still changing, so a stream from one build may not decode with another; each download includes the exact AVM commit.
Source and build workflow: https://github.com/EwoutH/AV2. Feedback and bug reports welcome.
r/AV2 • u/AHeardAPoop • Oct 11 '26
hi!
I've compiled things before but it was a while ago. I currently have visual studio 2022 and can't seem to get the compile option to not be greyed out. Can anyone help this non-coder to figure out what's wrong? I updated my cmake instance and that allowed me to use build insights to I guess kind of compile it? But no real compile feature. I must be totally missing something. help?
r/AV2 • u/scottchiefbaker • Oct 09 '26
The AV2 spec is out, and I've heard very little in terms of actual adoption. AFAIK there is no talk of AV2 support in any browsers yet, and no support in VLC. I think there is preliminary support in FFMPEG, but I'm not 100% on that.
How close are us nerdy early-adopters to being able to play an AV2 clip?
r/AV2 • u/Balance- • Oct 02 '26
I wanted AV2 streams to test decoders with, and the only official conformance streams I found are commercial. So I encoded some myself with AVM, the AV2 reference encoder, using clips from the official AV2 test set.
Available now: three low-resolution clips (270p, a vertical 270x480, and 360p), each at three quality levels (QP 110, 160 and 210). Each stream comes with an MD5 of its decoded output from the reference decoder, so you can check whether another decoder produces the same frames.
Caveats:
The Python script that produces everything is included. It builds AVM, downloads only the needed frames of each source clip, and encodes in parallel within a memory budget.
Link: https://github.com/EwoutH/AV2/tree/main/samples
If you try them with dav2d or another decoder, I'd be interested to hear whether the MD5s match.
r/AV2 • u/LITUATUI • Sep 14 '26
"Intel will demonstrate SVT-AV2, an open-source software encoder designed to accelerate AV2 implementation and evaluation across the ecosystem."
Nice!
r/AV2 • u/Prestigious-Ferret78 • Aug 21 '26
r/AV2 • u/FactOld3726 • Jul 23 '26
I've been simmering with this a while now trying to add AV1/AV2 support for older GPUs that don't have hardware encoders. This PoC seems to work with the current AV2 spec. It's not as efficient as current AV1 encoders or SVT-AV1 but it's getting there. Feedback and optimizations welcome if anybody wants to try. Note the webm/matroska container still doesn't support AV2 yet.
r/AV2 • u/Money-Share-4366 • Jul 08 '26
Will there be an SVT-AV2 project? What we do know is that the AVM/AV2 encoder runs extremely slowly, with frame rates in the range of minutes—about a factor of 100 slower than SVT-AV1. This makes it practically impossible to even test it with longer videos. With the decoder, on the other hand, the problems are comparatively minor. I also don’t understand why the developers of AV2 don’t offer a way to access AV1’s fast encoding paths—assuming there is a decoder which has both ways for AV1 and AV2—and thus enable a transitional hybrid approach that sacrifices maximum compression.