HNHacker News
TopNewBestAskShowJobs

JyrkiAlakuijala

1,179 karma · joined June 29, 2016

submissionscomments
JyrkiAlakuijala··on Why JPEG XL ignoring bit depth is genius (and why AVIF can't pull it off)
The original JPEG XL requirements were relational colors, where colors are an issue external to the codec. I was able to sufficiently convince the rest of the jpeg committee that we can achieve similar interoperability with absolute color, and particularly my xyb color space, and the absolute color storage giving us more opportunity to psychovisual optimization. Also, I was behind not having 8, 10, 12 bit modes, but just a single mode, and always yuv444 — to simplify operation and creating less confusion and less hard additional quality boundaries. Some of this "beauty" such as no yuv420 we needed to backtrack from for adding the lossless jpeg1 recompression support.
JyrkiAlakuijala··on Philips announces digital pathology scanner with native DICOM JPEG XL output
Seeing JPEG XL integrated into the DICOM standard was a particularly proud moment for me as the manager of the effort at Google.

It felt like closing a major circle in my career, because I spent the first 16 years of my career in the medical industry, working on Neurosurgical Robots (Oulu Neuronavigator System), and one of the first tools I built was an ACR-NEMA 1.0 parser, ACR-NEMA being the direct predecessor to DICOM, and then continuing on radiation treatment planning systems with plenty of DICOM work within them. To now contribute back to that very standard is incredibly rewarding.

JyrkiAlakuijala··on Consider using Zstandard and/or LZ4 instead of Deflate
zstd compresses less, so you wait a bit more for your data
JyrkiAlakuijala··on Consider using Zstandard and/or LZ4 instead of Deflate
except DNG, ProRAW, DICOM, GDAL, TIFF, Apple's and Microsoft's operating systems, Linux distros, and Windows support JPEG XL

otherwise the same

JyrkiAlakuijala··on Consider using Zstandard and/or LZ4 instead of Deflate
PNG with ZStandard or Brotli is much worse than WebP lossless.
JyrkiAlakuijala··on The JPEG XL Image Coding History, Features, Coding Tools, Design Rationale
Thank you. I agree with the sentiment that WebP lossless has stand the test of time better than WebP lossy. In some comparisons even Jpegli is more attractive from compression density point view than WebP lossy.

Disclaimer: I am the designer of WebP lossless and Jpegli.

JyrkiAlakuijala··on The JPEG XL Image Coding History, Features, Coding Tools, Design Rationale
> killed off

my guesswork is that JPEG XL will likely outlive Chrome by 100+ years

JyrkiAlakuijala··on Compression of Spectral Images Using Spectral JPEG XL
Lossy compression can be megabytes vs. tens or hundreds of megabytes per image kind of question, i.e., worth all the sweat it brings.
JyrkiAlakuijala··on Compression of Spectral Images Using Spectral JPEG XL
ZSTD/Tiff is quite far from JPEG XL in compression density. There are many technical reasons why this is the case.
JyrkiAlakuijala··on Compression of Spectral Images Using Spectral JPEG XL
I believe JPEG XL allows different scaling per layer, including decent default interpolation.

But usually exotic things are easier to engineer if you do them outside of the container, then you don't need to figure out how the standard works.

JyrkiAlakuijala··on JPEG XL: What It Is and Why You Should Care (2024)
While DNG uses JPEG XL internally for great compression, its implementation sacrifices some of JPEG XL's inherent advantages. For instance, JPEG XL's progressive rendering and preview capabilities are lost within the DNG container. Additionally, JPEG XL's lack of frame boundaries (it has consistent filtering defined over all frame/tile boundaries -- being the only image codec that gets this right!!), is negated when used in DNG's tiled structure. This tiling introduces frame boundary artifacts at lower quality levels, similar to how other codecs behave in tiled contexts. Although these are minor issues, a pure JPEG XL implementation would offer superior progressive display, previewing, and artifact-free compression compared to the DNG-wrapped version.
JyrkiAlakuijala··on How JPEG XL compares to other image codecs
Thank you for such a kind praise for Jpegli! This made my day.
JyrkiAlakuijala··on How JPEG XL compares to other image codecs
JPEG XL is seeing strong industrial adoption where image quality matters: professional and prosumer image acquisition (as a replacement, with huge benefits, of traditional raw imaging in iPhone 16 Pro) and processing and storage reduction with Digital Negative, ProRAW and medical imaging with DICOM. Clinics with archiving and telemedicine needs benefit massively.
JyrkiAlakuijala··on How JPEG XL compares to other image codecs
MozJPEG encoding times are not that great but decoding is still fast.

I believe with Jpegli you can have faster encoding than with MozJPEG.

JyrkiAlakuijala··on DICOM Medical Image Standard Chooses JPEG XL as a Payload Codec [pdf]
Thank you! This news gave me goosebumps-of-delight for three hours or so :-D
JyrkiAlakuijala··on DICOM Medical Image Standard Chooses JPEG XL as a Payload Codec [pdf]
DICOM 2024d version published today uses JPEG XL for coding images. It supports JPEG XL completely: lossless, JPEG1 recompression and lossy, including multichannel. This can reduce archiving costs, speed up operation, improve image quality and telemedicine latencies substantially.
JyrkiAlakuijala··on Why Apple Uses JPEG XL in the iPhone 16 and What It Means for Your Photos
Use Jpegli for now. You can get half the benefits of JPEG XL with it.
JyrkiAlakuijala··on Why Apple Uses JPEG XL in the iPhone 16 and What It Means for Your Photos
They might have some things like DCTs and colorspace transforms accelerated.
JyrkiAlakuijala··on Why Apple Uses JPEG XL in the iPhone 16 and What It Means for Your Photos
I will buy an iphone if it supports jpeg xl, and exactly because of that reason. ProRAW or DNG on top of jpeg xl, I wouldn't buy yet...
JyrkiAlakuijala··on Why Apple Uses JPEG XL in the iPhone 16 and What It Means for Your Photos
Agreed. At camera quality jpeg xl is far ahead in quality. Apple's last announcement is about camera quality, close to lossless kind of lossy. In this domain jpeg xl does not have real competition. AVIF and HEIC don't even support more than 12 bits of dynamics, and become slow when quality is increased.
JyrkiAlakuijala··on Why Apple Uses JPEG XL in the iPhone 16 and What It Means for Your Photos
I don't know, but my guesswork is that the DNG/ProRAW/JXL support comes with compatibility challenges. Limiting the size of the launch to well-informed photography prosumers and professionals will help to iron out the compatibility challenges — rather than make all confused consumers face these challenges at once.

I don't think that hardware support plays a role here. The fastest encoding modes of JPEG XL are ridiculously fast on software, and Apple's CPUs seem powerful enough.

JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
My take on this is that junior engineers optimize for the cpu as it is easy to measure, senior engineers for the user experienced latency as it matters more.

Users know that their time is valuable. If your website is fast, they will explore it, and came back soon.

JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
Could it be improved by having a wrapper for simple uses?
JyrkiAlakuijala··on Mozilla Is Interested in a Rust JPEG-XL Decoder for Firefox
https://news.ycombinator.com/item?id=41443336 has more comments
JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
https://news.ycombinator.com/item?id=41443336 has more comments
JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
Personally, I'm on the edge on this one. I think both viewpoints are valid.

One way to think of Highway is that it is portable multi-platform SIMD intrinsics for C++. While we developed it originally as a part of JPEG XL, it has long ago graduated into a general-purpose library that has various uses, including the recent Gemma.cpp ML launch. Other modern highway uses include: Audio, Browsers, Computational biology, Computer graphics, Cryptography, Grok JPEG 2000, JPEGenc, Jpegli, OpenHTJ2K, Image processing, Image viewers, Information retrieval, Machine learning, Numpy, and Robotics... (copied from: https://github.com/google/highway)

I derived the name from the CityHash, FarmHash, and then HighwayHash series, and considered that Highway would link this library to its roots in the HighwayHash (of course much is also based on Jan's previous work with SIMD). Notably, I resisted using the -li naming here :-D

JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
great analysis and summary of the JPEG XL benefits!
JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
I believe that there are already several decoder implementations that pass the ISO conformance test for JPEG XL. I don't remember which one's exactly but I believe at least both jxl-oxide and libjxl do.
JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
and that 38 kloc includes the encoder, psychovisual model, etc. etc. that are not needed for the decoder

current decoder is around 20 kloc

JyrkiAlakuijala··on Firefox will consider a Rust implementation of JPEG-XL
I believe that analysis is unfair or imprecise

libjxl decoder is 3-5x smaller in binary and 10x smaller in specification text size than an avif decoder

← PreviousPage 2 of 13Next →