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

Guetzli: A New Open-Source JPEG Encoder

research.googleblog.com

Post reply on HN
Print view View original

101–110 of 135 posts

Re: Guetzli: A New Open-Source JPEG Encoder

#101

Post by vladdanilov »

alexcroox wrote: post #65
vladdanilov wrote: post #12

I'm working on a similar thing ( http://getoptimage.com ). While Guetzli is still visually better and a bit smaller in file size, it's terribly slow and requires a lot of memory. But it's a great experiment. So much knowledge has been put into it. I believe using a full blown FFT and complex IQA metrics is too much. I have great results with custom quantization matrices, Mozjpeg trellis quantization, and a modificati…

Any plans for a Wordpress plugin like TinyPNG has? We use that currently but TinyPNG's JPG output leads to visible pixilation.

I'm still thinking on the best way to implement it. Right now you can mount an FTP/SFTP folder and process from there. But I might try to bypass the mounting part. Server version is also in the works.

Re: Guetzli: A New Open-Source JPEG Encoder

#102

Post by simooooo »

awalton wrote: post #94
vladdanilov wrote: post #12

I'm working on a similar thing ( http://getoptimage.com ). While Guetzli is still visually better and a bit smaller in file size, it's terribly slow and requires a lot of memory. But it's a great experiment. So much knowledge has been put into it. I believe using a full blown FFT and complex IQA metrics is too much. I have great results with custom quantization matrices, Mozjpeg trellis quantization, and a modificati…

> it's terribly slow and requires a lot of memory. ...and generates a solution that uses far less bandwidth, especially after thousands or millions of hits, which is the real point of the exercise. Cloud computing companies love this. They've got a lot of bored hardware to put to use. It's absolutely no surprise to see solutions like this coming from Google. Spending a dollar of compute time to save $1000 in bandwidt…

Have you noticed a lot of image results from a Google search are actually .webp, probably also for that reason

Re: Guetzli: A New Open-Source JPEG Encoder

#103

Post by simooooo »

awalton wrote: post #94
vladdanilov wrote: post #12

I'm working on a similar thing ( http://getoptimage.com ). While Guetzli is still visually better and a bit smaller in file size, it's terribly slow and requires a lot of memory. But it's a great experiment. So much knowledge has been put into it. I believe using a full blown FFT and complex IQA metrics is too much. I have great results with custom quantization matrices, Mozjpeg trellis quantization, and a modificati…

> it's terribly slow and requires a lot of memory. ...and generates a solution that uses far less bandwidth, especially after thousands or millions of hits, which is the real point of the exercise. Cloud computing companies love this. They've got a lot of bored hardware to put to use. It's absolutely no surprise to see solutions like this coming from Google. Spending a dollar of compute time to save $1000 in bandwidt…

Have you noticed a lot of image results from a Google search are actually .webp, probably also for that reason

Re: Guetzli: A New Open-Source JPEG Encoder

#104

Post by m_mueller »

sschueller wrote: post #41

Lots of Swiss German coming from Google lately. Zöpfli, Brötli and now Guetzli. I'm still hoping for a Google Now that understands Swiss German :)

I'm a bit sad but I guess I could have seen it coming ;-).

https://github.com/muellermichel/guetzli

Re: Guetzli: A New Open-Source JPEG Encoder

#106

Post by robryk »

wildpeaks wrote: post #105

Just tried the precompiled binary from: https://github.com/google/guetzli/releases and I'm getting "Invalid input JPEG file" from a lot of images unfortunately.

Sorry for that. See the following for a likely reason and workaround:

https://github.com/google/guetzli/issues/40#issuecomment-287...

Re: Guetzli: A New Open-Source JPEG Encoder

#107

Post by wildpeaks »

robryk wrote: post #106
wildpeaks wrote: post #105

Just tried the precompiled binary from: https://github.com/google/guetzli/releases and I'm getting "Invalid input JPEG file" from a lot of images unfortunately.

Sorry for that. See the following for a likely reason and workaround: https://github.com/google/guetzli/issues/40#issuecomment-287...

Thanks, I'll give it a try :)

Re: Guetzli: A New Open-Source JPEG Encoder

#108

Post by s3nnyy »

sschueller wrote: post #41

Lots of Swiss German coming from Google lately. Zöpfli, Brötli and now Guetzli. I'm still hoping for a Google Now that understands Swiss German :)

Although Zurich's software engineers are as expensive as those in the Bay area, Google employs 1500 of them and they bought a new building next to the main train station to hire hundreds of new ML / AI experts.

(Full disclosure: I am a programmer and I try to match programmers with Zurich's startups for a living.)

So, if you want to move to Zurich, you find my e-mail address in my HN-handle. Read more about Switzerland in my semi-famous blogpost "8 reasons why I moved to Switzerland to work in tech": https://medium.com/@iwaninzurich/eight-reasons-why-i-moved-t...)

Re: Guetzli: A New Open-Source JPEG Encoder

#110

Post by rurban »

Nice Makefile, jirki. I really have to look into premake which generated it.

But I get a gflags linking error with 2.1 and 2.2 with -DGFLAGS_NAMESPACE=google. This is atrocious. "google::SetUsageMessage(std::__cxx11::basic_string, std::allocator > const&)" Without this it works fine.

Guess I still have some old incompat gflags headers around.

EDIT: The fix on macports with 2.2 installed default into /usr/local is: make CXX=g++-mp-6 verbose=0 LDFLAGS="-L/usr/local/lib -L/opt/local/lib -v" CFLAGS=-I/usr/local/include

i.e. enforce gflags 2.2 over the system 2.1

Post reply on HN