Alliance for Open Media codecs

[hajj_3]

Microsoft Edge 121 has just been released. av1 and avif now work by default.

[Barough]

AOM AV1 v3.8.1-290-g0414f4e9ab
Built on February 24, 2024, GCC 13.2.0

https://aomedia.googlesource.com/aom


DL :
https://www.mediafire.com/file/5qhcvuaz26w4h9g

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64: GCC 13.2.0)

AOM v3.8.1-302-g14010c6f0f (https://www.mediafire.com/file/zxz6o0fg0i2v1hq/aom_v3.8.1-302-g14010c6f0f.7z/file)

rav1e 0.7.0 p20240227-g5eaae62e (https://www.mediafire.com/file/xs7wxk9ivz9udzn/rav1e_0.7.0_p20240227-g5eaae62e.7z/file)

dav1d 1.4.0-67-g85a1035 (https://www.mediafire.com/file/qzduyj6h4g1txap/dav1d_1.4.0-67-g85a1035.7z/file)

SVT-AV1 v1.8.0-43-g2bd950a9 (https://www.mediafire.com/file/1o94xnmusfuqcfu/SVT-AV1_v1.8.0-43-g2bd950a9.7z/file)

avif 1.0.4-8db5d51 (https://www.mediafire.com/file/jeyua48g348wy2l/avif_1.0.4-8db5d51.7z/file)
dav1d [dec]:1.4.0-67-g85a1035, aom [enc/dec]:3.8.1-302-g14010c6f0f, rav1e [enc]:0.7.0 (p20240227)

[LigH]

It seems to me that avifenc may support SVT-AV1 as one of several encoders. A recent build v1.0.4 does contain strings with related messages. But I doubt it contains code, and the help output doesn't mention it either. Does anyone know facts?

PS: The repo readme (https://github.com/AOMediaCodec/libavif) suggests that it has to be enabled in CMake options... maybe M-AB-S can do that for the 64-bit version.

PPS: Well, that was simple.

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64: GCC 14.1.0)

AOM v3.9.0-146-g4637f5d7 (https://www.mediafire.com/file/88yih37kbl19zco/aom_v3.9.0-146-g4637f5d7.7z/file)

rav1e 0.7.0 p20240423-1-g1c4fcd8 (https://www.mediafire.com/file/yqh99nyms3t5fwq/rav1e_0.7.0_p20240423-1-g1c4fcd8.7z/file)

dav1d 1.4.1-66-g3623543 (https://www.mediafire.com/file/phu2u316bzqhb1c/dav1d_1.4.1-66-g3623543.7z/file)

SVT-AV1 v2.1.0-bbcff78 (https://www.mediafire.com/file/mfg5c9pswvj2fvj/SVT-AV1_v2.1.0-bbcff78.7z/file)

avif 1.0.4-99c288a (https://www.mediafire.com/file/6wemdr3sg65mhyl/avif_1.0.4-99c288a.7z/file)
Version: 1.0.4 (dav1d [dec]:1.4.1-66-g3623543, aom [enc/dec]:3.9.0-146-g4637f5d7, rav1e [enc]:0.7.0 (p20240423-1-g1c4fcd8), svt [enc]:v2.1.0)
libyuv : available (1887)
Note: SVT-AV1 encoder in avifenc only available in 64-bit build

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64: GCC 14.1.0)

AOM v3.9.1-289-gb90f9011 (https://www.mediafire.com/file/adow5lrvv63x49l/aom_v3.9.1-289-gb90f9011.7z/file)

rav1e 0.7.0 p20240612-2-ge34e772 (https://www.mediafire.com/file/om45wvs3ndaucm0/rav1e_0.7.0_p20240612-2-ge34e772.7z/file)

dav1d 1.4.2-15-g2355eeb (https://www.mediafire.com/file/lrkkmvssr7xkfid/dav1d_1.4.2-15-g2355eeb.7z/file)

SVT-AV1 v2.1.2-52-gb13aec2 (https://www.mediafire.com/file/y4miln5g829aueb/SVT-AV1_v2.1.2-52-gb13aec2.7z/file)

avif 1.0.4-132b02c (https://www.mediafire.com/file/t1y395bwdfancge/avif_1.0.4-132b02c.7z/file)
Version: 1.0.4 (dav1d [dec]:1.4.1-66-g3623543, aom [enc/dec]:3.9.0-146-g4637f5d7, rav1e [enc]:0.7.0 (p20240612-2-ge34e772), svt [enc]:v2.1.0)
libyuv : available (1887)
Note: SVT-AV1 encoder in avifenc only available in 64-bit build

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64: GCC 14.2.0)

AOM v3.10.0-83-g8d4d4d8f (https://www.mediafire.com/file/r8w1opijar0zc0i/aom_v3.10.0-83-g8d4d4d8f.7z/file)

rav1e 0.7.0 p20240612-5-g7ab0de1 (https://www.mediafire.com/file/qc43geq28pu40fd/rav1e_0.7.0_p20240612-5-g7ab0de1.7z/file)

dav1d 1.4.2-54-gdd32cd5 (https://www.mediafire.com/file/5co0qnigzqv9erd/dav1d_1.4.2-54-gdd32cd5.7z/file)

SVT-AV1 v2.2.1-51-gf80d0e5 (https://www.mediafire.com/file/bo00xvq8v0qtl6r/SVT-AV1_v2.2.1-51-gf80d0e5.7z/file)

avif 1.1.1-8aab77e (https://www.mediafire.com/file/do8jyvmr67vteon/avif_1.1.1-8aab77e.7z/file)
Version: 1.1.1 (dav1d [dec]:1.4.2-54-gdd32cd5, aom [enc/dec]:3.10.0-83-g8d4d4d8f, rav1e [enc]:0.7.0 (p20240612-5-g7ab0de1), svt [enc]:v2.2.1-51-gf80d0e5)
libyuv : available (1887)
Note: SVT-AV1 encoder in avifenc only available in 64-bit build

[oibaf]

aom 3.10.0 was recently released:
https://aomedia.googlesource.com/aom/

2024-08-27 v3.10.0

This release includes new codec interfaces, compression efficiency and
perceptual improvements, speedup and memory optimizations and many bug
fixes. This release is ABI compatible with the last release.
The definitions of the internal macros AOM_INLINE and AOM_FORCE_INLINE
have been removed from the public header aom/aom_integer.h.
- New Features
* New codec controls:
* AV1E_SET_AUTO_TILES
* AV1E_GET_HIGH_MOTION_CONTENT_SCREEN_RTC
* AV1E_SET_POSTENCODE_DROP_RTC: Post encode frame drop feature.
* AV1E_SET_MAX_CONSEC_FRAME_DROP_MS_CBR
* New key-value pair for aom_codec_set_option():
* "auto-tiles": equivalent to the new codec control
AV1E_SET_AUTO_TILES.
- Deprecated Features
* Deprecated codec control:
* AV1E_SET_MAX_CONSEC_FRAME_DROP_CBR: Use the new codec control
AV1E_SET_MAX_CONSEC_FRAME_DROP_MS_CBR instead.
* The sframe_mode field in the aom_codec_enc_cfg_t struct is not
implemented.
- Compression Efficiency Improvements
* BD-rate gain of 0.7 - 1.3% (by enabling global motion tool) for
speed 5 and speed 6 with ~5% encode time increase.
* RTC speed 11 video: ~3-5% BD-rate gain for VGA and QVGA.
- Perceptual Quality Improvements
* RTC quality improvements for slide changes and scrolling content.
- Speedup and Memory Optimizations
* RTC screen content speedups:
* ~2x speedup for high motion content for speed 11.
* ~2x speedup on key frame coding for speed >= 10.
* Arm: Significant uplifts in speed in this release (vs v3.9.1) have
come from tuning the various convolutions according to filter size
(doing 8-tap when only 2-tap is required is inefficient) and also
deploying Armv8.6 USMMLA instructions in 6-tap and 12-tap standard
bitdepth convolutions.
* Standard bitdepth RTC:
* speed 5: +5%
* speed 6: +4%
* speed 7: +5%
* speed 8: +4%
* speed 9: +6%
* speed 10: +6%
* Standard bitdepth VoD:
* speed 0: +9%
* speed 1: +12%
* speed 2: +9%
* speed 3: +3%
* speed 4: +3%
* speed 5: -9% (expected due to global motion changes)
* speed 6: -3% (expected due to global motion changes)
* High bitdepth VoD:
* speed 0: +4%
* speed 1: +19%
* speed 2: +23%
* speed 3: +1%
* speed 4: +1%
* speed 5: -8% (expected due to global motion changes)
* speed 6: -3% (expected due to global motion changes)
* Standard bitdepth 2x1 horizontal super-resolution/scaling
encoding: +101%
- Other Improvements
* Reduce bit rate overshoot on slide content.
- Bug Fixes
* rtc: Bug fix for active_maps with sb_size=128.
* b:343429036: rtc: Fix source_sad setting near boundary.
* Fix to QP for temporal enhancement after key frame.
* b:343429192: rtc: Condition QP adjustment on rc->q_1/2_frame > 0.

[oibaf]

Enhancing Screen Sharing with AV1 in Microsoft Teams (https://techcommunity.microsoft.com/t5/microsoft-teams-blog/enhancing-screen-sharing-with-av1-in-microsoft-teams/ba-p/4096056)

It looks like they are using RTC screen content improvements in latest releases of aom.

[hajj_3]

dav1d decoder v1.5.0:

- AArch64: Optimize Armv8.0 NEON for HBD horizontal filters and 6-tap filters
- Power9: Optimized ITX till 16x4.
- Loongarch: numerous optimizations
- RISC-V optimizations for pal, cdef_filter, ipred, mc_blend, mc_bdir, itx
- Allow playing videos in full-screen mode in dav1dplay

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64: GCC 14.2.0)

AOM v3.10.0-186-g2d2f644e (https://www.mediafire.com/file/hvmf71vix5c8293/aom_v3.10.0-186-g2d2f644e.7z/file)

rav1e 0.7.0 p20241015-release (https://www.mediafire.com/file/ckulebxdoq7ma23/rav1e_0.7.0_p20241015-release.7z/file)

dav1d 1.5.0-16-g93f12c1 (https://www.mediafire.com/file/dxs0hq1c7d4i3pc/dav1d_1.5.0-16-g93f12c1.7z/file)

SVT-AV1 v2.3.0-39-gfdcb885 (https://www.mediafire.com/file/hlyuyvchjm6am6f/SVT-AV1_v2.3.0-39-gfdcb885.7z/file)

avif 1.1.1-1cdeff7 (https://www.mediafire.com/file/h0u2ek1ou7llzgy/avif_1.1.1-1cdeff7.7z/file)
dav1d [dec]:1.5.0-16-g93f12c1, aom [enc/dec]:3.10.0-184-g6418c21b, rav1e [enc]:0.7.0 (p20241015), svt [enc]:v2.3.0-29-g8d9f4ff
libyuv : available (1887)
Note: SVT-AV1 encoder in avifenc only available in 64-bit build

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64: GCC 14.2.0)

AOM v3.11.0-120-gdedba6a7 (https://www.mediafire.com/file/hxegdl23jpw4qql/aom_3.11.0-120-gdedba6a7.7z/file)

dav1d 1.5.0-46-gd242c47 (https://www.mediafire.com/file/i9kkffptl2hm78k/dav1d_1.5.0-46-gd242c47.7z/file)

SVT-AV1 v2.3.0-72-g8f1f1b0 (https://www.mediafire.com/file/lasjt9synfgruj9/SVT-AV1_v2.3.0-72-g8f1f1b0.7z/file)

avif 1.1.1-3196438 (https://www.mediafire.com/file/blhvh1zmb59ljcp/avif_1.1.1-3196438.7z/file)
dav1d [dec]:1.5.0-46-gd242c47, aom [enc/dec]:3.11.0-114-g6a1c5562, rav1e [enc]:0.7.0 (p20241015), svt [enc]:v2.3.0-64-g425e4bd
libyuv : available (1887)
Note: SVT-AV1 encoder in avifenc only available in 64-bit build

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64: GCC 14.2.0)

AOM v3.12.0-29-gc5e1e39e (https://www.mediafire.com/file/a2gt8xgt1wo6ljr/aom_v3.12.0-29-gc5e1e39e.7z/file)

rav1e 0.7.0 p20250225 g38879ab (https://www.mediafire.com/file/ay8qp2rkgmv10h6/rav1e_0.7.0-p20250225-g38879ab.7z/file)

dav1d 1.5.1-5-g8d95618 (https://www.mediafire.com/file/7xbzbm0xjw52ju8/dav1d_1.5.1-5-g8d95618.7z/file)

SVT-AV1 v3.0.1-20-g7bc96cc (https://www.mediafire.com/file/uv370sezhhuo1kb/SVT-AV1_v3.0.1-20-g7bc96cc.7z/file)

avif 1.2.1-1d46986 (https://www.mediafire.com/file/9lml9a99jl56qzt/avif_1.2.1-1d46986.7z/file)
dav1d [dec]:1.5.1-5-g8d95618, aom [enc/dec]:3.12.0-29-gc5e1e39e, rav1e [enc]:0.7.0 (p20250225), svt [enc]:v3.0.1-20-g7bc96cc
libyuv : available (1905)
Note: SVT-AV1 encoder in avifenc only available in 64-bit build

[oibaf]

2025-02-10 v3.12.0
This release includes new codec interfaces, compression efficiency and
perceptual improvements, speedup and memory optimizations, and bug
fixes. This release is ABI compatible with the last release.
Five internal functions (aom_free, aom_malloc, aom_wb_bytes_written,
aom_wb_write_bit, aom_wb_write_literal) that were exported by mistake
are no longer exported from the libaom shared library. The removal of
these internal functions from the ABI is a bug fix and does not break
ABI compatibility.
Acknowledgments: The image quality optimizations in the new tuning
mode AOM_TUNE_IQ were originally developed for SVT-AV1-PSY by
Cole Ogaard, Gianni Rosato, Julio Barba, and Zakaria Djebrouni.
- New Features
* New tuning mode AOM_TUNE_IQ (image quality) for the
AOME_SET_TUNING codec control (--tune=iq) in all-intra mode. The
feature detection macro AOM_HAVE_TUNE_IQ, if defined, indicates
that AOM_TUNE_IQ is available. The image quality optimizations in
AOM_TUNE_IQ were developed by using the SSIMULACRA 2 metric for
guidance and validated with subjective visual quality checks.
* New value 6 for the AV1E_SET_DELTAQ_MODE codec control
(--deltaq-mode): use modulation for all intra using Variance
Boost. Variance Boost is a variance adaptive quantization
implementation that modulates qindex depending on the ratio of
low-variance to high-variance 8x8 subblocks within a 64x64
superblock, as well as the actual variance of the subblocks
themselves.
* New value 3 for the AV1E_SET_ENABLE_CDEF codec control
(--enable-cdef): Enable CDEF adaptively based on frame qindex.
* In all-intra mode, the AOME_SET_SHARPNESS codec control now also
sets the loop_filter_sharpness syntax element in the bitstream.
Larger values increasingly reduce how much the filtering can
change the sample values on block edges to favor perceived
sharpness.
* In all-intra mode, the default value of the AV1E_SET_QM_MIN codec
control is decreased to 4, and the default value of the
AV1E_SET_QM_MAX codec control is increased to 10. The default
values in good-quality and realtime modes remain unchanged (5 and
9, respectively).
- Compression Efficiency Improvements
* Tuning mode AOM_TUNE_IQ improves image compression efficiency on
the CLIC dataset by up to 12% for the same SSIMULACRA 2 score, up
to 14% for the same DSSIM score, and up to 17% for the same
Butteraugli score.
* ~3% BD-rate gains for speed 11 VGA camera mode.
* ~5% BD-rate gains for speed 11 on scroll clips screen mode.
- Perceptual Quality Improvements
* Adjust temporal filter strength for better visual quality.
* RTC screen: visual quality improvements for scrolling and for
scene/slide changes.
* RTC camera mode: visual quality improvements for speed 11 VGA.
- Speedup and Memory Optimizations
* Optimize the Arm Neon implementation of the loop filter functions
with an average uplift of 15 - 25% in microbenchmarks.
* Add the CDEF optimization for RISC-V.
* Help the compiler generate better vectorized code for variance
calculation and warped motion in generic CPU builds.
* Make several arrays const.
- Other Improvements
* Binary size reduction: 1 - 2% compared with last release, with
CONFIG_REALTIME_ONLY enabled, CONFIG_AV1_DECODER and
CONFIG_AV1_HIGHBITDEPTH disabled.
* Build: compile source files in parallel under MSVC.
- Bug Fixes
* Fix bug where metadata added with aom_img_add_metadata was lost
when frame scaling was used.
* Bug b:383306740: RTC: Fix to issues with scrolling for screen
content.
* Bug b:382465458: RTC: Fix to artifact for grayscale input.
* Bug b:380247338: RTC: Fix to encode_time spikes on scene/slide
changes.
* RTC: Fix to rate correction factor update for VBR screen mode.
https://groups.google.com/a/aomedia.org/g/av1-discuss/c/nJxECdg-7P8
* Bug b:378401081: RTC: Fix to cyclic refresh update for external RC
(rate control).

[mzso]

Hi!

Is there any notable use of AV1 outside Youtube? (And I guess Netflix, of which I'm not a subscriber of)

[ksec]

Hi!

Is there any notable use of AV1 outside Youtube? (And I guess Netflix, of which I'm not a subscriber of)

I think Twitch was testing it but I dont think it is implemented as default yet. But other than that Not really. Which is despite why AOM supporter have been saying for the past 5 years as if AV1 is *everywhere*.

[Beelzebubu]

Hi!

Is there any notable use of AV1 outside Youtube? (And I guess Netflix, of which I'm not a subscriber of)

Meta has talked about using AV1 (link1 (https://engineering.fb.com/2023/02/21/video-engineering/av1-codec-facebook-instagram-reels/), link2 (https://www.streamingmedia.com/Articles/News/Online-Video-News/Metas-David-Ronca-Talks-Benchmarking-and-Deploying-AV1-in-the-Android-Ecosystem-168126.aspx)).

[mzso]

Oh well, I guess over time it still might become the web video de-facto standard. As HW support improves and SW codecs become more efficient. (At least the situation is not as big of a mess as with JPEG-XL)

[oibaf]

Microsoft Teams: https://techcommunity.microsoft.com/blog/microsoftteamsblog/enhancing-screen-sharing-with-av1-in-microsoft-teams/4096056
Google Meet: https://aomedia.org/av1-adoption-showcase/google-story/
Jitsi Meet: https://jitsi.org/blog/av1-and-more-how-does-jitsi-meet-pick-video-codecs/

[Beelzebubu]

That reminds me, Cisco's WebEx also uses AV1: https://blog.webex.com/engineering/the-av1-video-codec-comes-to-webex/

[nevcairiel]

Discord can stream in AV1 as well, although it being a live-encoding scenario they only use it when HW encoding is available. https://support.discord.com/hc/en-us/articles/12158692510743-Video-Codec-FAQ#h_01GRYP1FMKTKBCHQ198JCPM0Q1

[birdie]

Microsoft Teams: https://techcommunity.microsoft.com/blog/microsoftteamsblog/enhancing-screen-sharing-with-av1-in-microsoft-teams/4096056
Google Meet: https://aomedia.org/av1-adoption-showcase/google-story/
Jitsi Meet: https://jitsi.org/blog/av1-and-more-how-does-jitsi-meet-pick-video-codecs/

Yeah, nice links. Now have you actually confirmed these apps use AV1 encoding?

Because something tells me everything still uses H.264.

[hajj_3]

Yeah, nice links. Now have you actually confirmed these apps use AV1 encoding?

Because something tells me everything still uses H.264.

google meet uses av1: https://webrtchacks.com/the-hidden-av1-gift-in-google-meet/

[birdie]

google meet uses av1: https://webrtchacks.com/the-hidden-av1-gift-in-google-meet/

Someone in 2023 on some hardware confirmed that.

What about you though?

[LigH]

New uploads: (MSYS2; MinGW32 / MinGW64; GCC 15.1.0)

AOM v3.12.1-135-gb9f374fa (https://www.mediafire.com/file/tgnctc7gdtjz6gb/aom_v3.12.1-135-gb9f374fa.7z/file)

rav1e 0.8.0 p20250429 gcda1298 (https://www.mediafire.com/file/p3co5ve8090os7l/rav1e_0.8.0-p20250429-gcda1298.7z/file)

dav1d 1.5.1-5-g8d95618 (https://www.mediafire.com/file/7xbzbm0xjw52ju8/dav1d_1.5.1-5-g8d95618.7z/file)

SVT-AV1 v3.0.2-49-g5def505 (https://www.mediafire.com/file/u7o0t2wuu5shtje/SVT-AV1_v3.0.2-49-g5def505.7z/file)

avif 1.3.0-da9d727 (https://www.mediafire.com/file/ol07jqfejtuvez6/avif_1.3.0-da9d727.7z/file)
dav1d [dec]:1.5.1-5-g8d95618, aom [enc/dec]:3.12.1-135-gb9f374fa, rav1e [enc]:0.8.0 (p20250429), svt [enc]:v3.0.2-49-g5def505
libyuv : available (1905)
Note: SVT-AV1 encoder in avifenc only available in 64-bit build

[benwaggoner]

Someone in 2023 on some hardware confirmed that.
It could be that some very old hardware without the power to encode AV1 falls back to older codecs in some scenarios. That doesn't mean that AV1 isn't used by default or most of the time. Or in everything in 2025.

[oibaf]

Decoding Netflix's AV1 Streams: Here are 10 things I found (https://singhkays.com/blog/netflix-av1-decode/)

[VoodooFX]

Decoding Netflix's AV1 Streams: Here are 10 things I found (https://singhkays.com/blog/netflix-av1-decode/)

It talks about "quality" without actual quality analysis. Mostly about bitrates. Set lower bitrate on any codec - less bitrate - more "quality". :)

For some content, Netflix’s AV1 encodes are so focused on quality that they actually use more data than the HEVC equivalent.

Why not:
"For some content, Netflix’s AV1 encodes are so bad on quality that they actually use more data than the HEVC equivalent."

The Catch (There’s Always a Catch)

AV1 isn’t a magic bullet. It has two major hurdles:
Encoding Cost: AV1 is computationally expensive to encode. This requires a massive, ongoing investment in server infrastructure for any streaming service.
Device Support: Hardware decoding for AV1 is still not ubiquitous. This is a classic chicken-and-egg problem that will take a few more years of device refresh cycles to resolve.

Highly questionable...

[rwill]

Decoding Netflix's AV1 Streams: Here are 10 things I found (https://singhkays.com/blog/netflix-av1-decode/)

This is another one of these cases where someone without real knowledge of video compression and encoding came up with some wrong theories, based on their faulty data points, why AV1 is great.

[VoodooFX]

Another cringe AV1 vs h265: https://www.red5.net/blog/av1-vs-h265

[rwill]

Another cringe AV1 vs h265: https://www.red5.net/blog/av1-vs-h265

"[Picture] An Indian developer migrates from the H.265 video codec to AV1."

And this was the point where I closed the Browser Tab.

[oibaf]

AV1 now powers 30% of Netflix streaming: "On track to become number one"
https://www.flatpanelshd.com/news.php?subaction=showfull&id=1764912460
https://netflixtechblog.com/av1-now-powering-30-of-netflix-streaming-02f592242d80

[benwaggoner]

Another cringe AV1 vs h265: https://www.red5.net/blog/av1-vs-h265
Yeah, that reads like it was written by AI from press releases. The table even gives HEVC as the winner for encoding quality, contradicting the entire premise of the article!

AV1 isn't 30-50% more efficient than HEVC in any world. AV2 might achieve that, sure. But with equivalent tuning effort and encoding time, AV1 average bitrate is more like 15-25% better than HEVC (although is improving as there's more psychovisual tuning headroom in AV1 than the more mature HEVC).

[CruNcher]

Correct also important factor the Broadcast Playout side even if many don't see it yet but as soon as AV2 takes it over it is the end for MPEG as you knew it

https://www.youtube.com/watch?v=PNwPEcc1r3k

"Power to defy the enemy is not in him"

[ksec]

Correct also important factor the Broadcast Playout side even if many don't see it yet but as soon as AV2 takes it over it is the end for MPEG as you knew it

https://www.youtube.com/watch?v=PNwPEcc1r3k

"Power to defy the enemy is not in him"

That is again, assuming they learned from their mistakes.

But they still haven't released it yet.

[hajj_3]

AVIF 1.2.0 was released a week ago: https://aomedia.org/blog%20posts/AV1-Image-File-Format-Specification-Gets-an-Upgrade-with-AVIF/

[Z2697]

Just useless features no one is really gonna use...

I know lossless is "just an option" but they claim 10% size reduction over PNG? That's the best joke I've heard today. (It's often worse than PNG)
Everyone knows AVIF (or any Video-Codec-Based-Image-Format) is BAD at lossless RGB encoding.
Just use JPEG XL FOR F**KS SAKE. (facepalm)

[VoodooFX]

AV1 isn't 30-50% more efficient than HEVC in any world. AV2 might achieve that, sure. But with equivalent tuning effort and encoding time, AV1 average bitrate is more like 15-25% better than HEVC

In what conditions? Grainless 4/8K in synthetic metrics!?
In my subjective conditions [random film with grain in <= HD, "my eyes" metrics] AV1 is negatively better up to ~0% than HEVC.

Does anyone know why AV1 doesn't embed the encoder settings?

[soresu]

Does anyone know why AV1 doesn't embed the encoder settings?

All that embedding stuff is a function of the encoder, not the codec standard itself.

All the major encoders are open source, so if it's not doing that then file a bug to that effect.

[GeoffreyA]

Most encoders don't. We've just become used to x264 and x265 doing it.

[soresu]

Most encoders don't. We've just become used to x264 and x265 doing it.

Aaaaahhh I see, hmmm.

I'll mention it to BlueSwordM and see if he knows anyone who can mention it to somebody on the SVT AV1 team at least.

I've used it a few times now and didn't realise there was no settings recorded with each file.

[VoodooFX]

That would help in the community discussions/tunings as various SVT-AV1 forks use different defaults.

[Z2697]

Is there an equivalent of SEI UDU in AV1/OBU?

[GeoffreyA]

Aaaaahhh I see, hmmm.

I'll mention it to BlueSwordM and see if he knows anyone who can mention it to somebody on the SVT AV1 team at least.

I've used it a few times now and didn't realise there was no settings recorded with each file.

It would be helpful indeed, having that information.

Is there an equivalent of SEI UDU in AV1/OBU?

https://aomediacodec.github.io/av1-spec/av1-spec.pdf

I tried but it's a needle in a haystack. T35 seems to be used for DV.

[nevcairiel]

In general terms, the metadata OBU is similar to the SEI NALU. T-35 is an extensible metadata segment, which also exists in SEI.

[Z2697]

But the User Data Unregistered is basically arbitrary data, AV1's metadata OBU while possible to extend, does not register a similar type. (Register an Unregistered type, heh)

[rwill]

Linked AV1 spec pdf page 134 (doc 122). Table .. [omg, they did not number the table]. Its the metadata_type table.

There it says the metadata_type values 6 to 31 are Unregistered user private, so go for it.

[ksec]

I dont even remember if I said it before, but even Lunar New Year came and no still AV2. I guess the end of year must be on their usual AOM / On Calendar.

Old habits die hard.

[benwaggoner]

I dont even remember if I said it before, but even Lunar New Year came and no still AV2. I guess the end of year must be on their usual AOM / On Calendar.

Old habits die hard.
I keep being reassured that it should be out in 6-8 weeks.

I hear it'll be out in 6-8 weeks.

Ask me again in 6 weeks, and I suspect I'll say the same thing.