Not gonna comment on the image format itself since I'm not very familiar with image compression, but from a code aesthetics point of view this project makes me a bit sad. It's a half-hearted modern C++ attempt and everything is in one directory. At least we don't have to dig it out of the Chromium repo, I guess.
Pik – a new lossy image format for the internet
131–140 of 151 posts
Re: Pik – a new lossy image format for the internet
#132Good thing Denmark is a small market as it means Dick in Danish.
I strongly feel the most popular image/video formats are dependent on how they sound when people speak them.
Re: Pik – a new lossy image format for the internet
#133HEIF already exists as a standard [1] with comparable compression [2]. What does Pik hope to do better? (And please don't say "patent free" unless you are certain Pik will not infringe on those same patents) [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_For... [2] https://nokiatech.github.io/heif/technical.html
Maybe "The software currently requires an AVX2 and FMA capable CPU, e.g. Haswell." holds the secret? Some kind of experimental test bed for using CPU vector instructions to speed up compression/decompression? Disclaimer: I have no idea what I am talking about. For all I know possible use of these instructions is already a feature of HEIF and that statement is irrelevant.
> I have no idea what I'm talking about.
That's okay, you're on "hacker news". 1 in 20 have.
Re: Pik – a new lossy image format for the internet
#134[deleted]
Re: Pik – a new lossy image format for the internet
#135Good thing Denmark is a small market as it means Dick in Danish.
I have a bone to pik with you.
Just thought of the Teledyne Waterpik brand. What did they ever do with that in Denmark? According to this FB post:
https://www.facebook.com/JstTht/posts/134568413284684?_fb_no...
Quote:
Waterpik uses another name in Denmark. "Pik" is the common Danish word for male genitals. Most Danes can easily translate "water" to the danish word "vand". And "vandpik" is a term for the morning erection. "And you put that thing in your mouth?!?!"
Re: Pik – a new lossy image format for the internet
#136Good thing Denmark is a small market as it means Dick in Danish.
Flemish dude here. it's a dialect word for dick
Re: Pik – a new lossy image format for the internet
#137> New lossy image format gives 55 % less bytes than jpeg with the same butteraugli score. It's the most serious attempt to date to make an open source replacement for JPEG which misses a lot of advances in data/image compression. I hope it stops the spreading of HEIF plagued by patents.
I'm not certain, but I think HEIF itself is royalty-free.
HEIF is just an image container format. The current implementation of HEIF supports JPEG, H.264, and H.265. So, yes, if you use H.264 or H.265 inside HEIF then you have all of those attendant patent licensing issues. But if you use JPEG inside HEIF or if someone implements support for VP8 or VP9 or eventually AV1 then I think you should be able to use HEIF royalty-free.
The GitHub repository is at: https://github.com/nokiatech/heif
The "License Grant" section of LICENSE.TXT sounds like it grants a royalty-free patent license to the HEIF format itself, exclusive of any codec patent licenses as you'd expect. So I think once VP9 or AV1 support is added HEIF may be a nice container format for images.
Re: Pik – a new lossy image format for the internet
#138> New lossy image format gives 55 % less bytes than jpeg with the same butteraugli score. It's the most serious attempt to date to make an open source replacement for JPEG which misses a lot of advances in data/image compression. I hope it stops the spreading of HEIF plagued by patents.
I had high hopes for FLIF. What I think is great is that the client can control how much data is downloaded. This is great for responsive use. Unfortunately the license is holding back implementations.
How so? The FLIF reference implementation is Apache 2.0 licensed for the decoder, how does that hold back implementations?
Re: Pik – a new lossy image format for the internet
#139I noticed this project is missing quite a few features common to modern image codecs, such as variable transform sizes, deblocking, or intra prediction. Of course, it's a work in progress, so those things could still be to come. Have you considered using Daala's lapped transforms? They work with variable block sizes and are quite effective for still images. Also, was there anything that motivated doing a custom image…
We have tried a large variety of approaches for the integral transform, but we were not impressed with the density/complexity/quality/decoding speed compromise -- at high image quality. We believe that we can only add a certain amount of complexity in this kind of format, and we try to keep our complexity budget targeted on solving the high-quality-high-decoding-speed image compression as well as possible.
Re: Pik – a new lossy image format for the internet
#140At the first glance it looks like it uses all the basic building blocks of JPEG, but with everything upgraded to the next level. It uses the same 8x8 DCT blocks, but with adaptive quantization. Like JPEG it also codes DC separately, but with 8 predictors instead of 1, etc. It's like a combination the Guetzli JPEG encoder and Lepton JPEG recompressor.
Yes, PIK is like guetzli + lepton, but decodes 2-3x faster and compresses 20 % more.