HNHacker News
TopNewBestAskShowJobs

JyrkiAlakuijala

1,179 karma · joined June 29, 2016

submissionscomments
JyrkiAlakuijala··on Computational Life: How self-replicating programs emerge from simple interaction
Zilog Z80: The reports of my death are greatly exaggerated. I'm actually creating life nowadays.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I was very careful not to overstate WebP lossless quality. I compressed the originals with zopflipng and pngcrush before stating figures (-26 %).

If I had just used the internet quality images, WebP lossless would have improved size by -42 %.

Yet another 'marketing textbook' way to overstate -42 % is to turn it into 'loading speed': 1/(1-0.42) = 72 % faster.

None of this was made for the lossless and the most conservative estimate was shown. I didn't do any hacking or cherry picking to produce the number and I had several internal verification approaches to be correct.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I don't think that is accurate. Brotli was added first to Firefox. It took 9 months longer for Chrome. Brotli has many other uses than content encoding in the web.
JyrkiAlakuijala··on Implementation of Google's Griffin Architecture – RNN LLM
Fun fact -- gemma.cpp uses highway, an amazing high performance computation library originally developed in the JPEG XL effort.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Thank you! This is comforting to know!
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
MozJPEG not being more precise than Jpegli at mid or lower qualities also matches with our experiments, both internal uncontrolled experiments and the rater study we published.

There was an earlier version which was not very good at medium or low quality, but Zoltan fixed that about six months ago.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I got this wrong. We actually did the implementation in the libjxl/libjxl repo. There is no physical reuse of the jpeg xl code, however.

It would have been clearer to make it its own repo.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I think technically it is it's own github repo, just under libjxl user. I could be mistaken, I'm still learning git and GitHub.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
JPEGinen or JPEGli in Finnish
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Haha. Thank you!
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
It's not a new JPEG++. It creates old JPEGs, fully 100% compatible.

(Of course JXL is better still.)

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I don't see any downsides with Jpegli. Your Linux distro admin exchanges the lib for you, you never need to think about it, only get smaller and more beautiful files. If you use commercial software (Apple, Adobe, mobile phone cameras, Microsoft, ...) hopefully they migrate by themselves.

If they don't, literally nothing happens.

I fail to see a major downside. Perhaps open up your thinking on this?

Yes, Chrome published data.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
It can be a question when your uncle's/daughter's/etc phone is full of photos and they asks for advice on how to make more space.

It can be a question of if the photo fits as an email attachment etc.

'Zillions' of seconds of aggregate latency waiting time is spent each day on waiting for web sites to load. Back-of-the-envelope calculations can suggest that the value of reducing waiting time can be in hundreds of billions over the whole time of the deployment. Bandwidth cost to users and energy use may also be significant factors.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I tried to reach to their devrel person Jen Simmons here: https://twitter.com/jyzg/status/1763141558042243470

I didn't follow up and I don't know if she read it or understood the proposal.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
The main idea why Ultra HDR is done like that is that the content creator (photographer) can control the local tone mapping. I think.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
What happens if you recompress them losslessly manually to JPEG XL?
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
That would give additional savings.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
You can always use JPEG XL lossless JPEG1 recompression to get some savings in the high end quality, too — if you trust the quality decision heuristics in jpegli/guetzli/other jpeg encoder more than the JPEG XL encoder itself.

We also provide a ~7000 lines-of-code libjxl-tiny that is more similar to jpeg encoders in complexity and coding approach, and a great starting point for building a hardware encoder.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I decided to call it 10.5 bits based on rather fuzzy theoretical analysis and a small amount of practical experiments with using jpegli in HDR use where more bits is good to have. My thinking is that in the slowest smoothest gradients (where banding would otherwise be visible) it is only three quantization decisions that generate error: (0,0), (0,1) and (1, 0) coefficient. Others are close to zero. I consider these as adding stochastic variables that have uniform error. On the average they start to behave a bit like a Gaussian distribution, but each block samples those distributions 64 times so there are going to be some more and some less lucky pixels. If we consider that every block would have one maximally unlucky corner pixel which would get all three wrong.

log(4096/3)/log(2) = 10.41

So, very handwavy analysis.

Experimentally it seems to roughly hold.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Thank you for such a well-informed report!

With guetzli I added manually overprovisioning for slow smooth gradients. If you have an example where guetzli is better with gradients you could post an issue with a sample image. That would help us to potentially fix it for jpegli, too.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
The output will be smaller after replacing libjpeg-turbo or mozjpeg with jpegli. You don't need to do any code changes.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Moritz, the author of that improvement, implemented the same for jpegli.

I believe the standard does not specify what the intermediate progressive renderings should look like.

I developed that interpolation mechanism originally for Pik, and Moritz was able to formulate it directly in the DCT space so that we don't need to go into pixels for the smoothing to happen, but he computed it using a few of the low frequency DCT coefficients.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I believe that they should be roughly the same in a photography corpus density at quality 60. Consider filing an issue if some image is worse with jpegli.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Brotli:11 gets within 0.6 % of LZMA density but decodes 3–5x faster.
JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Ultra HDR can have two jpegs inside, one for the usual image and another for the gain-map.

Hypothetically, both jpegs can be created with jpegli.

Hypothetically, both Ultra HDR jpegs can be decoded with jpegli.

In theory jpegli would remove the 8 bit striping that would otherwise be present in Ultra HDR.

I am not aware of jpegli-based Ultra HDR implementations.

A personal preference for me would be a single Jpegli JPEG and very fast great local tone mapping (HDR source, tone mapping to SDR). Some industry experts are excited about Ultra HDR, but I consider it is likely too complicated to get right in editing software and automated image processing pipelines.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Multi-corporate effort would likely need to start by first agreeing what is image quality.

Image quality folks are more cautious and tradition-centric than codec devs, so quite an initial effort would be needed to use something as advanced and risky as butteraugli, ssimulacra or XYB. With traditional objective metrics it would be very difficult to make a competing format as they would start with a 10–15 % disadvantage.

So, I think it is not easy and would need substantial investment.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
Through non-standard API extensions you can provide a 16 bit data buffer to jpegli.

The data is carefully encoded in the dct-coefficients. They are 12 bits so in some situations you can get even 12 bit precision. Quantization errors however sum up and worst case is about 7 bits. Luckily it occurs only in the most noisy environments and in smooth slopes we can get 10.5 bits or so.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I consider codec to mean a pair of encoder and decoder programs.

I don't consider it to necessarily mean a new data format.

One data format can be implemented by multiple codecs.

Semantics and nomenclature within our field is likely underdeveloped and the use of these terms varies.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
I thought clarity was more important.

Otherwise it would be called ... Pumpernikkeli.

JyrkiAlakuijala··on Jpegli: A new JPEG coding library
It is approximately correct. The rendering is standards compliant without pixel perfection and most decoders make different compromises and render slightly different pixels.
← PreviousPage 3 of 13Next →