Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pik – a new lossy image format for the internet

github.com

Post reply on HN
Print view View original

111–120 of 151 posts

Re: Pik – a new lossy image format for the internet

#112

Post by rwmj »

mattnewton wrote: post #100
cjensen wrote: post #95

HEIF 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.

http://www.libjpeg-turbo.org/ uses some CPU vectorization features already. (If you're using Linux, most likely you're already using it since most Linux distros switched over a long time ago).

Re: Pik – a new lossy image format for the internet

#113

Post by polishTar »

polk wrote: post #36
stepik777 wrote: post #27

Earlier quoted context omitted.

How could Google own something written and supported in the authors' free time?

If you work at Google everything you make, even in your spare time, belongs to them. That's how the contracts work, unfortunately.

This is not true, and employees are explicitly told that this is not true.

There is an internal process to have google release any copyright they may hold on any project you produce on your own time without using corp resources. All it requires is going through a standard and a (mostly) boilerplate legal review.

Re: Pik – a new lossy image format for the internet

#114

Post by TD-Linux »

I 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 format rather than applying Butteraugli to WebP?

Re: Pik – a new lossy image format for the internet

#115

Post by pbhjpbhj »

Ajedi32 wrote: post #105
s0me0ne wrote: post #96

Now if APNG would gather some steam, high quality animated fully alpha transparent images would be nice. Gif's 256 color and 1 level transparency is ok, but to do better work we need something like APNG, although not sure how well it compresses.

Pretty sure APNG is supported now in all browsers except Edge and IE. So not quite there yet, but we're getting close.

>except Edge and IE //

Any ideas why?

Re: Pik – a new lossy image format for the internet

#116

Post by ac29 »

Ajedi32 wrote: post #105
s0me0ne wrote: post #96

Now if APNG would gather some steam, high quality animated fully alpha transparent images would be nice. Gif's 256 color and 1 level transparency is ok, but to do better work we need something like APNG, although not sure how well it compresses.

Pretty sure APNG is supported now in all browsers except Edge and IE. So not quite there yet, but we're getting close.

Doesn't work in Chrome for Android either: https://caniuse.com/#search=apng.

Re: Pik – a new lossy image format for the internet

#118

Post by pbhjpbhj »

lowkeyokay wrote: post #59
BurningFrog wrote: post #21

Earlier quoted context omitted.

And it's not actually called "Google Pik". Just "Pik".

Certaintly will cause a few laughs in Denmark... (hint: Google translate)

http://en.bab.la/dictionary/danish-english/pik "cock/dick/penis"
Post reply on HN