mp4parse-rust
av1-avif
Our great sponsors
| mp4parse-rust | av1-avif | |
|---|---|---|
| 2 | 25 | |
| 395 | 437 | |
| 0.8% | 0.7% | |
| 5.4 | 0.0 | |
| 18 days ago | over 1 year ago | |
| Rust | HTML | |
| Mozilla Public License 2.0 | BSD 2-clause "Simplified" License |
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.
mp4parse-rust
-
H26Forge: Exploiting Vulnerabilities in the H.264 Decoders of iOS, Firefox, VLC [pdf]
The mp4 demuxer is indeed in Rust [0], and runs in the content process (= the process in which the web page is loaded).
We don't have a h264 decoder in our source tree, we use the platform's decoder (because of patents). It's very often in a separate, dedicated process, and when it's not, it's in the GPU process, because when hardware accelerated decoders are used, they're using more or less the same resources as the rendering code.
Those other processes with the tightest sandbox possible (per process type, per platform, etc.), and don't have access to the web page.
On Linux, the platform decoder we're using is `libavcodec` from FFmpeg, but that's still in a separate process with a tight sandbox.
We're also doing something interesting, which is compiling libraries to WASM and then back to native code to get memory safety [1]. This is used when performance isn't critical (unlike codecs, so, e.g. a demuxer that we don't want to rewrite in Rust).
[0]: https://github.com/mozilla/mp4parse-rust/
-
Firefox avif support delayed again until at least version 90 on 29th June 21
Instead of standard lib, Firefox uses a rust-based image parser, and there are problems with the compliance because all avif apps have to implement the following specs:
av1-avif
-
FSF Slams Google over Dropping JPEG-XL in Chrome
The article is about avif not webp. Note the editors for the AOM avif specification don't even include Google https://aomediacodec.github.io/av1-avif/
-
Whistleblowers Take Note: Don’t Trust Cropping Tools
This reminds me of something similar from the guy who implemented AVIF in Firefox. He gives a talk about the implementation [1] where he talks about the CLAP privacy problem. Basically the spec adds a field that allows for cropping of the image, but the binary file would still contain the original. This would lead users to believe some image data was deleted when it really wasn't. I always thought he spent a lot of time and effort on this for little gain, but now I'm starting to think it was worth his effort.
[1]: https://youtu.be/BUkRlfkv2D8?t=2199
And the related GitHub issue: https://github.com/AOMediaCodec/av1-avif/issues/188
-
AVIF images encoded with yuv422 appear black on iOS 16 / MacOS Ventura
So actually the same images I linked above are in the AOMediaCodec repo as well, under Link-U: https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles/Link-U And I see the same issue with the yuv422 images there as well. I'm guessing Apple's AVIF implementation must be incomplete?
- JPEG-XL Sample HDR Photos
- Questions about AVIF metadata for PQ HDR mastering & tonemapping
-
What is AVIF?
Created by Alliance for Open Media and worked on by Netflix, Microsoft, and Google developers, AVIF is open source - you can even weigh in on image processing and spec issues.
- We need to rethink AVIF lossless mode.
-
How can HDR AVIF stills be created?
I've been trying to find a way edit 14bit RAW files (.ARW) to an HDR capable format (HEIF/AVIF). In the process I found out there's an official AVIF encoder (1) by AOM that seems like it should be capable of creating HDR PQ stills.
-
HDR AVIF samples (HDR10 for still images)
Others samples are available here : https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles/Netflix/avif
-
Question: Multiscale AVIF performance?
AVIF can do something that resembles hierarchical JPEG and that could be useful for progressive decoding: you can have multiple layers/scales, where e.g. first a 1:4 image is encoded, then residuals to get to 1:2, then residuals to get to 1:1. Examples of this were recently added to the AVIF spec: https://github.com/AOMediaCodec/av1-avif/pull/134
What are some alternatives?
ImageMagick - 🧙♂️ ImageMagick 7
libavif - libavif - Library for encoding and decoding .avif files
chromium - The official GitHub mirror of the Chromium source
brunsli - Practical JPEG Repacker
webp - webp for the Windows build of ImageMagick
squoosh - Make images smaller using best-in-class codecs, right in the browser.
lepton - Lepton is a tool and file format for losslessly compressing JPEGs by an average of 22%.
jekyll_picture_tag - Easy responsive images for Jekyll.
jpeg-xl - jpeg-xl for the Windows build of ImageMagick
image_compression_comparison - Image Compression Comparison Framework
libjxl - JPEG XL image format reference implementation