|
2021-01-27 03:24:09
|
Hi everyone – this discord was created on Monday January 25th 2021, so unless you are reading this in the relatively distant future, it doesn't exist for a long time yet. Suggestions on how to improve it can be made in <#804008033595162635>. Feel free to invite anyone interested in image compression!
|
|
2021-01-27 03:25:14
|
Pointers to JPEG XL related info are collected here: https://sneyers.info/jxl/
(please let me know if you want to add something there)
|
|
2021-01-28 08:36:08
|
Last week, at the 90th JPEG meeting, it was decided to advance JPEG XL to the FDIS stage: the FDIS text has been approved by the committee and is now submitted to ISO for the final ballot in the national bodies (ANSI, DIN, etc).
|
|
2021-01-28 08:36:19
|
Updated white paper on JPEG XL: http://ds.jpeg.org/whitepapers/jpeg-xl-whitepaper.pdf
|
|
2021-01-28 08:39:18
|
JPEG is also sending out a bunch of liaison letters to other standardization organizations to inform them that JPEG XL is now ready for adoption.
|
|
2021-01-28 08:42:40
|
Here is the current standardization schedule for JPEG XL, dates are YY/MM. Part 1 is of course the most important one because it defines the codec itself.
|
|
2021-01-29 08:08:18
|
libjxl 0.3 released! https://gitlab.com/wg1/jpeg-xl/-/releases#v0.3
|
|
2021-02-22 03:41:10
|
https://cloudinary.com/blog/time_for_next_gen_codecs_to_dethrone_jpeg
|
|
2021-06-02 11:03:47
|
(copying what <@604964375924834314> posted in <#803574970180829194>)
hey all, we are collecting data for the decision to have JPEG XL on by default in Chrome and we would need your help. Could you please share images or descriptions of use cases where JPEG XL does better or worse than AVIF? either here on Discord, in a GitHub issue, or using this form: https://forms.gle/rnKJt5RWq5tvdXueA
|
|
2021-08-27 09:02:00
|
There is a jxl art competition going on in <#824000991891554375> . It might be a bit hard to find because it is in a thread, which I don't think you can see by default if you haven't participated in it. To see the thread, you have to go to the channel and click on the "threads" button. There are 3 days left to submit your entries, 4 days left to vote. The winner gets the <@&878598897793114122> role!
|
|
2021-08-31 10:42:22
|
Time to vote! Check the entries in <#878599623843913728> and add a <:BlobYay:806132268186861619> emoji to the one(s) you like the most.
|
|
2021-09-18 08:09:35
|
About 10 days left to submit one or more <#824000991891554375> entries for the September 2021 compo. Categories are <#882173948534603806>, <#882174149374672896> and <#882174448478863370> .
|
|
2021-11-02 07:19:42
|
The October <#824000991891554375> compo has been extended until the end of November. Submit your entries in the <#899346138266746890> and in the <#899346548796841994> threads! (you may have to look in the archived threads since discord auto-archives threads after inactivity)
|
|
2021-12-15 10:21:11
|
ISO/IEC 18181-1 FDIS has been approved! That means the International Standard is now "under publication" (stage 60.00), that is, ISO/CS is processing the final document which is scheduled to be published on 2022-01-07 (if there are no delays).
|
|
2022-03-31 12:51:27
|
ISO/IEC 18181-1 finally is an official, published IS: https://www.iso.org/standard/77977.html
|
|
2022-04-23 05:59:20
|
ffmpeg now supports jxl! https://git.videolan.org/?p=ffmpeg.git;a=commit;h=0008c159562b877700cd9b7c96f941de4ee69af5
|
|
2023-04-21 01:04:17
|
The CID22 dataset is finally (partially) released: https://cloudinary.com/labs/cid22
|
|
2025-11-22 08:01:47
|
> Since JPEG XL was last evaluated, Safari has shipped support and Firefox has updated their position. We also continue to see developer signals for this in bug upvotes, Interop proposals, and survey data. There was also a recent announcement that JPEG XL will be added to PDF.
>
> Given these positive signals, we would welcome contributions to integrate a performant and memory-safe JPEG XL decoder in Chromium. In order to enable it by default in Chromium we would need a commitment to long-term maintenance. With those and our usual launch criteria met, we would ship it in Chrome.
>
> Rick (on behalf of Chrome ATLs)
https://groups.google.com/a/chromium.org/g/blink-dev/c/WjCKcBw219k/m/NmOyvMCCBAAJ
|