-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support AVIF #508
Comments
I've written pure-rust encoder: And a decoder that uses libaom: |
What's the binary size of the decoder and encoder?
…On Fri, Sep 11, 2020, 8:03 AM Kornel ***@***.***> wrote:
I've written pure-rust encoder:
https://lib.rs/crates/cavif
And a decoder that uses libaom:
https://lib.rs/crates/aom-decode
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2LH4PTSHDMBZVB4EMXD3SFIU4JANCNFSM4RHKIB3A>
.
|
cavif is pretty lean. I've replaced libavif with basically one big
|
I'm hesitant to triple the size of Imageflow to add avif support.
…On Fri, Sep 11, 2020, 1:44 PM Kornel ***@***.***> wrote:
cavif is pretty lean. I've replaced libavif with basically one big struct.
It's 100% pure Rust. Includes rav1e. Executable is 1.7MB, gzips to 500KB.
aom-decode is fatter — 7MB — since it pulls in all of libaom. I haven't
looked at trimming it down. Maybe dav1d would be smaller, but it needs
meson and ninja to build, and I'm not a fan.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2LHZ67D23RYDNUWJTAZLSFJ4YDANCNFSM4RHKIB3A>
.
|
I get that decoding brings in large dependencies, but you could support encoding only. Encoding can be done in pure Rust and rav1e is pretty lean. I've released my encoder as a library: https://docs.rs/ravif |
I will consider it then.
…On Mon, Sep 14, 2020, 6:17 AM Kornel ***@***.***> wrote:
I get that decoding brings in large dependencies, but you could support
encoding only. Encoding can be done in pure Rust and rav1e is pretty lean.
I've released my encoder as a library: https://docs.rs/ravif
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2LH2FHVXFOKTY2JYD37LSFYCWFANCNFSM4RHKIB3A>
.
|
Any progress on this? I would be very interested since AVIF support is at around 70% https://caniuse.com/avif and I believe it's really good. |
I'm really hoping iOS adds support for AVIF. Safari gets much of its speed
by delegating image processing to the OS and its incredible hardware
integration, so stuff lands much more slowly there.
I would like to add this, but I have a lot going on right now, so I can't
offer a timeline.
…On Thu, Jan 6, 2022 at 12:26 AM iJungleboy ***@***.***> wrote:
Any progress on this? I would be very interested since AVIF support is at
around 70% https://caniuse.com/avif and I believe it's really good.
—
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2LH4CO3E3ZHH3RCF4MFDUUU7ZPANCNFSM4RHKIB3A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
No problem - and thanks for your more-than-amazing work! |
Support for this would be great with Safari soon to be supporting. https://www.coywolf.news/webmaster/safari-now-supports-avif-in-macos-ventura-and-ios-16/ |
@lilith AVIF support now? |
It's planned. It will be slow, though, no getting around that.
…On Wed, Nov 23, 2022, 11:54 PM ZZ ***@***.***> wrote:
@lilith <https://github.com/lilith> AVIF support now?
—
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2LH543LGRFUSJHSHJBYLWJ4GJVANCNFSM4RHKIB3A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
AVIF support is around 93% now, and I've seen some adoption by the public as well. Is there an estimated timeline for when ImageFlow will support it? Also there was some (old) discussion about supporting an encoder but not a decoder. Is that still under consideration? The decoder is as important to me as the encoder. |
It is still under consideration; it's orders of magnitude slower to encode,
however, so I'm currently focusing on bolstering caching and ahead-of-time
cache priming.
The decoder is also more security-critical surface area... and this format
will singlehandled double the binary size of the product and affect
scale-up times accordingly.
This week I'm adding aarch64 support for apple/win/linix.
…On Thu, Aug 22, 2024, 2:55 PM Levi Carter ***@***.***> wrote:
AVIF support is around 93% now, and I've seen some adoption by the public
as well. Is there an estimated timeline for when ImageFlow will support it?
Also there was some (old) discussion about supporting an encoder but not a
decoder. Is that still under consideration? The decoder is as important to
me as the encoder.
—
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2LHY2333GVJ3N6IXL3VTZSZF43AVCNFSM6AAAAABM65H7IGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBVGYYTSNBZGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Proper caching is definitely required to compress AVIF properly. However, if you'd like something implementable sooner, then ravif/rav1e at the fastest encoding setting takes only about as long as encoding WebP, and is still a bit better than WebP. |
@tvatavuk this may be interesting for you as you were experimenting with ARM/Windows... |
Supported aarch64 in source. But publishing is a problem since github
windows arm runners lack git, pwsh, bash, and everything.
…On Thu, Aug 29, 2024, 10:41 PM iJungleboy ***@***.***> wrote:
aarch64
@tvatavuk <https://github.com/tvatavuk> this may be interesting for you
as you were experimenting with ARM/Windows...
—
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2LH6QHY7EMQR3S6PUHADZT7ZXZAVCNFSM6AAAAABM65H7IGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGAZDMMBQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks @lilith (and @iJungleboy) for making it possible to use Imageflow on Windows 11 ARM64. 😊 I did a small proof of concept and manually built Still, this is a build of the latest development version of This is a great step forward! 🚀 |
I'd like to submit a proposal for a future feature to consider.
https://netflixtechblog.com/avif-for-next-generation-image-coding-b1d75675fe4
Format comparison:
https://jakearchibald.com/2020/avif-has-landed/
The text was updated successfully, but these errors were encountered: