Support AVIF (AV1 Image FIle Format)

[jansol]

Spec at https://aomediacodec.github.io/av1-avif/

Since there is already a PR for FLIF support, it probably makes sense to have at least a tracking issue for AVIF as well.

[kornelski]

For AVIF encoding, have a look at https://github.com/kornelski/cavif-rs (https://docs.rs/ravif)

It's a 100% pure Rust integration with rav1e.

[197g]

I tried using the encoder with the bindings and imagemagick thinks the produced file is not valid:

$ cargo run --example convert --features=avif -- tests/reference/tiff/testsuite/mandrill.tiff.694c777d.png mandrill.avif
$ file mandrill.avif
mandrill.avif: ISO Media
$ convert -verbose mandrill.avif mandrill.jpeg
convert: Invalid input: No 'hdlr' box `mandrill.avif' @ error/heic.c/IsHeifSuccess/136.
convert: no images defined `mandrill.jpeg' @ error/convert.c/ConvertImageCommand/3285

I believe this refers to this statement in the specification.
There are no mentions of pict in avif-serialize. Are there any reference, roundtrip or self-tests to execute?

[kornelski]

avif-serialize is verified to be compatible with libavif (Chrome) and mp4parse (Firefox).

I do not support AVIF-sequence format in avif-serialize (hdlr is for marking video/audio tracks), only AVIF still images. These are two different flavors of MP4.

[est31]

Should this be reopened? There is no decoding support yet.

[foresterre]

@kornelski

I'm not always experiencing success with encoding AVIF in https://github.com/foresterre/sic which uses the latest https://github.com/image-rs/image (at time of writing v0.23.10) using the current implementation. Or, I am not sure whether it works or not, because Firefox seems unable to decode the resulting files (Firefox 81, x64 on Ubuntu):

with about:config:

If I disable use-dav1d I get the same results.

I've made a minimal example using the image crate which can be found here: https://github.com/foresterre/avifexample/blob/main/src/main.rs#L24

I used the wh1616.png sample file: avif_samples.zip (includes my .avif results).

Is this the above usage for the minimal example correct or did I miss something?

If there is something I can do to help (further), please let me know!

Hoping this is an OK place to place to ask about this 😅, I'm a bit unsure whether to post here, since I did use the image crate, however, I also experience difficulties when using your cli tool with cavif wh1616.png, and the image crate doesn't really do much magic in between as far as I a aware... I used cavif 0.6.2, latest version, installed from crates.io

[est31]

@foresterre chrome opens the avif files you attached just fine. In firefox I can reproduce the errors. Maybe avif support is not ready yet in Firefox? You could try filing a Firefox bug.

[kornelski]

This is expected. Implementation in Firefox is still very incomplete and does not support alpha channel. I'm waiting for this to be merged:

mozilla/mp4parse-rust#239

[kleisauke]

avif-serialize is verified to be compatible with libavif (Chrome) and mp4parse (Firefox).

I do not support AVIF-sequence format in avif-serialize (hdlr is for marking video/audio tracks), only AVIF still images. These are two different flavors of MP4.

Note that not including the hdlr-box could break future strict decoding modes in libavif and libheif. See AOMediaCodec/libavif#407 and strukturag/libheif#371.

For example, checking a cavif-rs encoded AVIF image against ComplianceWarden currently results in this error:

[Rule #2] Error: 'hdlr' not found in MetaBox
[heif] 1 error(s).
[heif] 0 warning(s).

Specification description: HEIF - ISO/IEC 23008-12 - First edition 2017-12

Involved rules descriptions:

[heif][Rule #2] Section 6.2
The handler type for the MetaBox shall be 'pict'.
[isobmff] No errors.