News for hackers. Stuff that matters.
Re:Opera embraces Google's open source JPEG killer by DarkShikari on Wednesday April 13, 2011 @09:24AM (#2442063)
Advantages:

Theoretically better compression than JPEG (but ... so was JPEG-2000).

Disadvantages:

The encoder actually loses to JPEG in many tests and almost everything it encodes looks like a blurry mess.

No support for any color format besides 4:2:0.

Almost no support in image editing applications.

An order of magnitude slower than JPEG.

Somehow I don't think this is much of a "JPEG killer". Its technology is 10 years out of date, entirely copy-pasted from H.264, and its featureset isn't even close to equalling JPEG's, let alone adding new features that people wanted.

Re:Opera embraces Google's open source JPEG killer by ZeroGravitas on Wednesday April 13, 2011 @09:42AM (#2442134)
When you say the encoder loses to JPEG and is blurry, are you talking about the new re-written encoder they released a month ago, or the old one that was just the WebM encoder?

Release note:

https://groups.google.com/a/webmproject.org/group/webp-discu...

Re:Opera embraces Google's open source JPEG killer by DarkShikari on Wednesday April 13, 2011 @09:48AM (#2442154)
Skal's new encoder on its slower modes does seem to do a good bit better. Its approach is quite slow compared to the regular VP8 encoder (which was already slow), though.

The code is actually rather interesting to read -- it basically uses K-means for a large portion of the encoding process, which is applicable in this case because of VP8's non-adaptive arithmetic coder. I've never seen an encoder done quite this way before.

Re:Opera embraces Google's open source JPEG killer by usertm on Wednesday April 13, 2011 @11:20AM (#2442632)
I guess they'll use in their Turbo technology which is really great for mobile phones. Apart from North America and Europe, the rest of the world is still dealing with limited bandwidth caps and slow speed of GPRS/EDGE.
Re:Opera embraces Google's open source JPEG killer by liuliu on Wednesday April 13, 2011 @11:39AM (#2442737)
I never understand why JPEG XR (http://en.wikipedia.org/wiki/JPEG_XR) didn't take off. It seems that Microsoft really has some management problem to push things forward or they simply don't care that much about it after all.
Re:Opera embraces Google's open source JPEG killer by wladimir on Wednesday April 13, 2011 @09:32AM (#2442095)
Compression is slower. But it isn't entirely clear to me whether decompression is slower than JPEG too. That's the thing that matters.

I cannot find any comparison, but that's because WEBP is a very bad name for searching on google: it gets shortened to 'web'.

Re:Opera embraces Google's open source JPEG killer by DarkShikari on Wednesday April 13, 2011 @09:37AM (#2442117)
Decompression is dramatically slower due to VP8's arithmetic coding.
Re:Opera embraces Google's open source JPEG killer by ZeroGravitas on Thursday April 14, 2011 @05:15AM (#2446174)
Surely for images served over the web the key measurement is the speed gain due to smaller filesize minus the loss due to extra decompression time. It is after all a project hosted under Google's speed project.

http://code.google.com/speed/webp/

Which elsewhere claims that 99 human years are wasted due to uncompressed web content each day.

http://code.google.com/speed/articles/use-compression.html

Opera certainly seem to think they can compress and decompress the WebP image on-the-fly and still come out ahead speed-wise compared with the original (at a cost of quality) and their old JPEG system (with improved quality), at least over low-bandwith connections.

Re:Opera embraces Google's open source JPEG killer by JacobAldridge on Wednesday April 13, 2011 @10:22AM (#2442313)
Try +WEBP - The + tells Google to ignore what it thinks and just listen to you, the user, dammit.
Re:Opera embraces Google's open source JPEG killer by benmccann on Wednesday April 13, 2011 @12:04PM (#2442869)
Yes, or put it in quotes.
Re:Opera embraces Google's open source JPEG killer by JacobAldridge on Tuesday April 26, 2011 @11:07AM (#2485510)
Adding this way after the discssion in case it appears in future searches - the quotes don't really help with words that can be split into other words.

My great-grandfather's surname is Aland. I did some searching on him recently - a search for "Aland" also returns results for "Al and" and "a land", neither of which are relevant. Using the + prevents that.