libjxl VS jxl-winthumb

> Regarding JPEG XL's mobile support, it makes sense it would see limited development if the company that manages one of the biggest mobile players has been the greatest restriction on their success. The lack of support also disincentivises manufacturers to prioritise support.

There was literally no involvement from any hardware vendor in the standardization of JPEG XL. It went from a Call for Proposals in Sept 2018 to Committee Draft in Aug 2019 with very little time for industry feedback. Contrast this with AV1 which had involvement from hardware vendors Intel, NVIDIA, Arm, AMD, Broadcom, Amlogic from the beginning as well as companies who ship media on hardware at scale such as Cisco, Netflix, Samsung and yes Google. These companies reviewed and provided significant feedback on the format that made it suitable for hardware implementation.

https://news.ycombinator.com/threads?id=JyrkiAlakuijala is a lead on the project and a Google employee, and active in JPEG XL development https://github.com/libjxl/libjxl/commits?author=jyrkialakuij...

https://github.com/libjxl/libjxl/blob/main/doc/format_overvi... is a pretty detailed but good overview. The highlights are variable size DCT (up to 128x128), ANS entropy prediction, and chroma from luminance prediction. https://github.com/libjxl/libjxl/blob/main/doc/encode_effort... also gives a good breakdown of features by effort level.

For JPEG XL, refer to its format overview [1]. In short its lossless mode uses a combination of multiple techniques: the rANS coding with an alias table, LZ77, reversible color transforms, a general vector quantization that subsumes palettes, a modified Haar transform and a learnable meta-adaptive decision tree for context modelling.

One good thing about JPEG XL is that its lossy mode also largely uses the same tool, with a major addition of specialized quantization and context modelling for low- and high-frequenty components.

[1] https://github.com/libjxl/libjxl/blob/main/doc/format_overvi...

The cjxl source is here. If you spot any reason why -x strip=exif may not work, tell me.

The problem is that the instructions for actually running the WASM file are not that clear... the docs the author mentions shows how to compile to WASM, which is easy enough, but then here's the instructions to make that actually work in the browser:

https://github.com/libjxl/libjxl/blob/main/tools/wasm_demo/R...

Yeah, you need some mysterious Python script, a JS service worker at runtime, choose whether you want the WASM or WASM_SIMD target, use a browser that supports Threads and SIMD if you chose that, make sure to serve everything with the appropriate custom HTTP headers... just reading that, I can see that to get this stuff working on non-browser WASM targets would likely require expertise in WASM, which is the point of the OP. WASM's UX is just not there yet.

https://github.com/libjxl/libjxl#usage

> Specifically for JPEG files, the default cjxl behavior is to apply lossless recompression and the default djxl behavior is to reconstruct the original JPEG file (when the extension of the output file is .jpg).

I mean compiling a bleeding edge kicad, inkscape or jpeg-xl is easy. But will probably trash your system if you already have an older version installed.

But you look at your image viewer that could have the lossless indicator? (and there is an issue open to add this indicator to the jxl files)

https://github.com/libjxl/libjxl/issues/432

> usually the filename and an image preview are the only pieces of information you get about an image no matter where you are

that's obviously false, it entirely depends on "where you are"

> ignorant of the literal entire world not doing this

The entire world is ignorant enough to not know that png is lossless

Also, don't hide behind the entire world, this conversation is about you "i don't look at dialogs before i download, save, or pick a file from a directory listing"

> fail to understand how windows explorer is not relevant when you can't just set the image viewer for save/open dialogs on windows, that's just not a thing that's possible to do

(by the way, it'd be entierly possible to add metadata even in Windows Explorer when this https://github.com/saschanaz/jxl-winthumb/issues/26 is added)

but you're not forced to just the save/open dialogs of the default file manager. You can even use a more convenient workflow of navigating in your file manager and making the open dialog switch there, and within your file manager you would have more info vs WinExplorer

jxl-winthumb provides WIC capabilities. It could do with some increased google-ability though

Currently, JPEG XL can be enabled in Chromium, Firefox, and Opera browsers, but has no other browser support. JPEG XL is supposed to remain royalty free. You can grab the encoder and decoder off Github and chat with other JPEG XL enthusiasts on Reddit and Discord. You can install JPEG XL utilities on Mac using homebrew and on Windows. Tools like GIMP and ImageMagick are beginning to support it.

What is JPEGXL The image coding system JPEG XL (ISO / IEC 18181) is particularly suitable for responsive conditions on the Internet, so that content from a variety of contraceptives can be viewed with pleasure. In addition, it reinforces some of the strategies that have worked by changing the old JPEG program. The JPEG XL workflow is tension-free and loss-free and a good program for powerless network applications. It is expected to perform better than current power lines and will largely replace it from now on. JPEG XL provides transmission with the most important features: st High risk of poor image compression. ✓ Best image compression without data loss. dis Gradual separation enc JPEG encryption without loss. for is designed for intuitive and tidy graphics. Fast programming for coding and interpretation. help Complete help for Wide Access and HDR. • Make the reference giver more tangible. Software Free software, open source and incompetent thanks to jpegxl.info" text = "jpegxl.info" for excellent collection! Windows JXL Support There are several ways to enable JPEG XL Assist in Windows. Unfortunately, Windows does not yet offer any neighborhood help. You can download modules created by monitors or use an external image monitor. Windows thumbnail update: now supports WIC decoding! JXL logs can be viewed using Windows Photo Viewer or other monitors with WIC experience. With the Windows File Explorer JXL-Winthumb module you can display thumbnails of JPEG XL documents (* .jxl). Install Microsoft Visual C Redistributable for Visual Studio 2019 if not currently available. Download the latest DLL report from the development page. Open the terminal window as a boss. Go to your registry where the DLL report was found. Type reg regsvr32 jxl_winthumb.dll and press Enter. Get support for JXL Windows thumbnails here: https://github.com/saschanaz/jxl-winthumb External image viewer In addition to these modules and tricks, you can also use an external image viewer to view JXL reports aids, for example nomacs PhotoQT XnView MP ImageGlass JPEGXL WIC This method is not intended for the end customer, as it does not specify openness and presence. JPEG XL WIC Provides the Windows Imaging Components (WIC) implementation for a JPEG XL image layout. Causes Windows to clearly see the relationship between the JPEG XL report and the use of the JPEG XL codec in image management. With this new development, viewing photos is essentially the same speed as using Windows Explorer, Microsoft Photo Viewer, or Microsoft Photos. JPEG XL WIC in production, similar to the JPEG XL codec. The aim is to use the JPEG XL codec in Windows with a focus on HDR / WCG image recognition. Download the JPEG XL WIC here: https://github.com/mirillis/jpegxl-wic

Thank you so much! jxl-winthumb sounds like it'll work for the time being; looking forward to eventual support in browsera and Paint.NET

Releases · saschanaz/jxl-winthumb (github.com)