Announcement

Collapse
No announcement yet.

Mozilla Firefox Appears Ready To Enable AVIF Image Handling Support By Default

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

  • birdie
    replied
    Originally posted by juarezr View Post
    There wasn't a wave of adoption except from Google and virtually no hardware encoding/decoding.
    VP9 is now universally supported unlike AV1 whose support is laaaaaaacking.

    Leave a comment:


  • shmerl
    replied
    Originally posted by arzeth View Post
    Code:
    avifenc -j 12 -s 0 --min 0....63 --max 0....63 test.jpg test.avif
    Trying that on Debian testing:

    Code:
    [FONT=monospace][COLOR=#000000]avifenc test.png test.avif [/COLOR]
    Successfully loaded: test.png
    AVIF to be written: (Lossy)
    * Resolution     : 1436x1029
    * Bit Depth      : 8
    * Format         : YUV444
    * Alpha          : Present
    * Range          : Full
    * Color Primaries: 1
    * Transfer Char. : 13
    * Matrix Coeffs. : 6
    * ICC Profile    : Absent (0 bytes)
    * XMP Metadata   : Absent (0 bytes)
    * EXIF Metadata  : Absent (0 bytes)
    * Transformations: None
    Encoding with AV1 codec '(null)' speed [8], color QP [0 (Lossless) <-> 10 (High)], alpha QP [0 (Lossless) <-> 0 (Lossless)], tileRowsLog2 [0], tileColsLog2 [0], 1 worker thread(s), please wait...
    ERROR: Failed to encode image: No codec available[/FONT]
    What is missing?

    Leave a comment:


  • AmericanLocomotive
    replied
    Originally posted by cl333r View Post

    Google doesn't have to support WebP across all of its products, just the most important ones. I didn't even know anyone uses Google Slides, are you also using Google+?
    The G-Suite for Education is being used by almost 100 million students globally, and Google Slides is a huge component of that. Never mind the 5+ million businesses who use G-Suite as part of their daily activities.

    WebP isn't supported on ANY G-Suite product: Docs, Slides, Sheets, Drawings, Jamboard, etc... It's absurd that Google is pushing its successor when they've only barely implemented into their own web products.

    Leave a comment:


  • bug77
    replied
    Originally posted by uid313 View Post
    You can produce AVIF images with GIMP, since version 2.10.22 (blog post).
    Not the most widespread source, but ok, asked and answered. Fwiw Darktable also seems to support it.

    Originally posted by szymon_g View Post
    and what's wrong with G+, exactly?
    G+ has been closed for a while. He was implying Google Slides is also a deserted project. I don't do many spreadsheets, but I have long moved all my office needs to Google's online suite.

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by bofh80
    the file sizes are pretty shocking.

    Leave a comment:


  • raun0
    replied
    I have thought is that going to be accelrated with the gpu av1 decoder or CPU only? There will be sense with very large ( photo set ) or multilayer photos. Or will be the edit format always be something else?

    Leave a comment:


  • juarezr
    replied
    Originally posted by birdie View Post
    That's weird. They dragged on with WebP support for five years before finally enabling it, now with AV1F they are almost rushing.
    Originally posted by AmericanLocomotive View Post
    Google doesn't even support WebP across all of their own products yet. You can't import WebP images into Google Slides, for example.
    There some differences for Mozilla acceptance between WebP and AVIF:
    1. WebP was a Google lonely project while AV1 derived AVIF included broad participation from codec researchers, hardware companies and content providers.
    2. With AV1 Mozilla/Xiph.org are on board since [Alliance for Open Media](http://aomedia.org/) inception jointly with Google and Cisco.
    3. They did have a sit in the member's pool for defining the governance of AOM and for the AV1 codec.
    4. They could contribute with source code like parts of code imported from Daala video codec.
    5. They could integrate algorithms developed from they research on Daala like [Non-binary Arithmetic Coding](https://tools.ietf.org/html/draft-te...02#section-2.1), [Deringing Filter/CDEF](https://hacks.mozilla.org/2018/06/av...cement-filter/) and [Chroma from Luma](https://docs.google.com/presentation...it?usp=sharing)
    6. They could contribute with AV1 video quality [requirements](https://tools.ietf.org/html/draft-mo...c-requirements) and [evaluation](https://datatracker.ietf.org/doc/rfc8761/) and also with software [infrastructure](https://arewecompressedyet.com).
    Also the codec advantages for WebP was smaller when compared with AVIF:
    1. WebP quality and compression gap wasn't big enough when compared with jpeg. Webp suffered from the success of jpeg.
    2. WebP patent defense scenario was not clear as compared with the AOM strong patent pool.
    3. There wasn't a wave of adoption except from Google and virtually no hardware encoding/decoding.

    Leave a comment:


  • szymon_g
    replied
    Originally posted by cl333r View Post
    are you also using Google+?
    and what's wrong with G+, exactly?

    Leave a comment:


  • cl333r
    replied
    Originally posted by AmericanLocomotive View Post
    Google doesn't even support WebP across all of their own products yet. You can't import WebP images into Google Slides, for example.
    Google doesn't have to support WebP across all of its products, just the most important ones. I didn't even know anyone uses Google Slides, are you also using Google+?

    Leave a comment:


  • brad0
    replied
    Originally posted by birdie View Post
    That's weird. They dragged on with WebP support for five years before finally enabling it, now with AV1F they are almost rushing.
    Mozilla Corp wouldn't know how to rush anything. It's slow as molasses with them.

    Leave a comment:

Working...
X