Originally posted by juarezr
View Post
Announcement
Collapse
No announcement yet.
Mozilla Firefox Appears Ready To Enable AVIF Image Handling Support By Default
Collapse
X
-
Originally posted by arzeth View PostCode:avifenc -j 12 -s 0 --min 0....63 --max 0....63 test.jpg test.avif
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]
Leave a comment:
-
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+?
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.
- Likes 4
Leave a comment:
-
Originally posted by szymon_g View Postand what's wrong with G+, exactly?
Leave a comment:
-
Originally posted by bofh80found a great write up here
https://jakearchibald.com/2020/avif-has-landed/
- Likes 1
Leave a comment:
-
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:
-
Originally posted by birdie View PostThat'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 PostGoogle doesn't even support WebP across all of their own products yet. You can't import WebP images into Google Slides, for example.- WebP was a Google lonely project while AV1 derived AVIF included broad participation from codec researchers, hardware companies and content providers.
- With AV1 Mozilla/Xiph.org are on board since [Alliance for Open Media](http://aomedia.org/) inception jointly with Google and Cisco.
- They did have a sit in the member's pool for defining the governance of AOM and for the AV1 codec.
- They could contribute with source code like parts of code imported from Daala video codec.
- 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)
- 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).
- WebP quality and compression gap wasn't big enough when compared with jpeg. Webp suffered from the success of jpeg.
- WebP patent defense scenario was not clear as compared with the AOM strong patent pool.
- There wasn't a wave of adoption except from Google and virtually no hardware encoding/decoding.
- Likes 6
Leave a comment:
-
Originally posted by AmericanLocomotive View PostGoogle doesn't even support WebP across all of their own products yet. You can't import WebP images into Google Slides, for example.
- Likes 1
Leave a comment:
Leave a comment: