Announcement

Collapse
No announcement yet.

FFmpeg Lands AVIF Muxer For This Image Format Based On AV1

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Quackdoc
    replied
    Originally posted by linuxgeex View Post

    Wow. Shocked that I didn't see this before. FF/Chrome have been avoiding MPEG-LA going on 10 years so I would simply never have believed they'd adopt this mux format. I've been using .avif in gimp for 2 years, exporting to WebP, and I'll keep doing that, but it's nice to know that in another 3ish years I can probably start shipping .avif images for the web.
    well there is a few things wrong with this, primarily being that mp4 is just a container (a highly mediocre one but still) so mpeg-la doesn't really hold any power to do anything.

    secondly mp4 is well supported in firefox and chrome

    lastly if you are doing stills, you will want jxl, avif will still be better for animations, but jxl is what you want for stills, much better then avif and is also getting rapid support.

    Leave a comment:


  • linuxgeex
    replied
    Wow. Shocked that I didn't see this before. FF/Chrome have been avoiding MPEG-LA going on 10 years so I would simply never have believed they'd adopt this mux format. I've been using .avif in gimp for 2 years, exporting to WebP, and I'll keep doing that, but it's nice to know that in another 3ish years I can probably start shipping .avif images for the web.
    Last edited by linuxgeex; 03 June 2022, 07:46 PM.

    Leave a comment:


  • blip256
    replied
    There are CDNs like Cloudflare for example that support automatic transparent conversion to WebP too.
    and Cloudflare Images converts to AVIF if the browser supports that [1].
    [1] https://blog.cloudflare.com/images-avif-blur-bundle/

    Leave a comment:


  • brad0
    replied
    Originally posted by Spacefish View Post
    webp is used more than you think. a lot of websites nowerday use webp if the browser supports it as this saves bandwidth and loading time. As almost all users have a browser which supports it nowerdays, there is no real reason to not use it.
    Essentially of the "relevant" browser only IE11 does not support it, which has a market share of ~0,5%. So 99,5% of users have support for it.

    On June 15 2022 microsoft will further "disable" IE11 on all windows machines, so it will redirect to edge (chromium based) automatically. So we will have like ~99,8% support.
    There are CDNs like Cloudflare for example that support automatic transparent conversion to WebP too.

    Leave a comment:


  • Spacefish
    replied
    Originally posted by brucethemoose View Post
    I think the biggest roadblock to AVIF/JXL/whatever is going to be habit and familiarity. Kinda like how transcoding to mp3 is still popular, and some apps *still* default to it, even though there is basically no reason to do it.


    Webp is basically AVIF's predecessor, but it faced a similar issue. No one is going to use it if it wont embed in discord or facebook or imgur or whatever, if their camera doesn't encode it, and if their apps still default to making jpegs.
    webp is used more than you think. a lot of websites nowerday use webp if the browser supports it as this saves bandwidth and loading time. As almost all users have a browser which supports it nowerdays, there is no real reason to not use it.
    Essentially of the "relevant" browser only IE11 does not support it, which has a market share of ~0,5%. So 99,5% of users have support for it.

    On June 15 2022 microsoft will further "disable" IE11 on all windows machines, so it will redirect to edge (chromium based) automatically. So we will have like ~99,8% support.

    Leave a comment:


  • brucethemoose
    replied
    I think the biggest roadblock to AVIF/JXL/whatever is going to be habit and familiarity. Kinda like how transcoding to mp3 is still popular, and some apps *still* default to it, even though there is basically no reason to do it.


    Webp is basically AVIF's predecessor, but it faced a similar issue. No one is going to use it if it wont embed in discord or facebook or imgur or whatever, if their camera doesn't encode it, and if their apps still default to making jpegs.
    Last edited by brucethemoose; 13 May 2022, 05:53 PM.

    Leave a comment:


  • brad0
    replied
    Originally posted by linuxgeex View Post
    This isn't going to get adopted, because mov/mp4 are controlled by MPEG-LA and they want nothing to do with AV1. So it will be a bastardised standard, so it will never be adopted by W3C, Firefox, Chrome, and that will kill it dead. Sigh.
    Yet it's adopted and supported by all mentioned.

    Leave a comment:


  • Quackdoc
    replied
    well, still no animation support, but at least chrome has that too.

    Leave a comment:


  • numacross
    replied
    Originally posted by linuxgeex View Post
    This isn't going to get adopted, because mov/mp4 are controlled by MPEG-LA and they want nothing to do with AV1. So it will be a bastardised standard, so it will never be adopted by W3C, Firefox, Chrome, and that will kill it dead. Sigh.
    But... Firefox supports it since 93 and Chrome supports it since 85.

    Leave a comment:


  • blip256
    replied
    In response to Blogs -- AVIF is already supported by Firefox and Chrome [1]. W3C doesn't need to do anything since the picture element already supports it (image/avif) and enables specifying a backup like jpeg for browsers that don't support image/avif.
    [1] https://caniuse.com/avif

    Leave a comment:

Working...
X