12 ms·
Jpegli: A new JPEG coding library
- jauntywundrkind 3y ago[flagged]
- deleted 3y ago[deleted]
- jsnell 3y agoFirst, this is work by the team that co-designed JPEG XL. Second, as far as I can tell this is a JPEG encoding library, producing JPEG files that any existing JPEG decoder will be able to read. Nobody is being asked to support or maintain anything new.
- deleted 3y ago[deleted]
- CharlesW 3y agoNot to mention that it's 35% more efficient than existing encoders, and can support 10+ bits per component encoding while remaining compatible with existing decoders. That's pretty amazing.
- amluto 3y agoIt would still be nice to see a comparison to JPEG XL.
- edflsafoiewq 3y agohttps://giannirosato.com/blog/post/jpegli/ https://giannirosato.com/blog/post/jpegli/ Note that that's from almost a year ago, don't know if anything changed.
- deaddodo 3y agoYeah, this is just that. They took JPEG XL denoising and deartifacting algorithms and front loaded them into a 10-bit JPEG encoder. There's more to it, of course, but it's essentially just an improved encoder versus a new format.
- JyrkiAlakuijala 3y agoNo denoising or deartifacting was used. They are an option for future improvements at low quality JPEG decoding.
- jbverschoor 3y agoThe sourcecode is on jxl's main repo. I'm confused to say the least
- jsnell 3y agoWhat's so confusing about it? This team did a lot of work to create JPEG XL. For whatever reason, Chrome is not agreeing to ship it, which will make it a lot harder for it to be widely adopted. So they're now applying the same techniques to classic JPEG, where the work they did can provide value immediately and not be subject to a pocket veto by Chrome.
- jbverschoor 3y agoThe confusing part is that the code is in the jxl repository. Is it Google's code, JXL's, JXL's people under Google?
- lonjil 3y agoAll the developers involved are part of the JXL team at Google Zürich, as far as I can tell.
- xfalcox 3y agoDoes anyone have compiled this to WASM? I'm currently using MozJPEG via WASM for a project and would love to test replacing it by Jpegli.
- simonw 3y agoA WASM demo of this would be fantastic, would make it much easier for people to try it out. Maybe a fork of https://squoosh.app/ https://squoosh.app/ ? The code for that is https://github.com/GoogleChromeLabs/squoosh https://github.com/GoogleChromeLabs/squoosh
- jeffbee 3y agoJust for my own edification, why would there be any trouble compiling portable high-level libraries to target WASM?
- tedunangst 3y agoMaybe it uses threads.
- cactusplant7374 3y ago> These heuristics are much faster than a similar approach originally used in guetzli. I liked guetzli but it's way too slow to use in production. Glad there is an alternative.
- theanonymousone 3y agoIs that from Google Zürich?
- JyrkiAlakuijala 3y agoYes!
- veselin 3y agoWhen I saw the name, I knew immediately this is Jyrki's work.
- 082349872349872 3y agoI'm waiting for huaraJPEG...
- actionfromafar 3y agowhat is that?
- mensi 3y agoa much ruder but just as stereotypically Swiss German thing as the "-li" suffix ;)
- thaliaarchi 3y agoI’ve never heard of a Jpegli bread, but Zöpfli and Brötli sure are yummy :)
- JyrkiAlakuijala 3y agoI thought clarity was more important. Otherwise it would be called ... Pumpernikkeli.
- p0nce 3y agoWonder how it compares to guetzli, which is good albeit slow (by Google also!).
- JyrkiAlakuijala 3y agoI believe guetzli is slightly more robust around quality 94, but jpegli likely better at or equal at lower qualities like below 85. Jpegli is likely about 1000x faster and still good.
- p0nce 3y agoI'm using quality 98, but I have only a few encode to ship, so I can live with the encode times :)
- ronjouch 3y agoThat's my experience, yes. Just tested it on a 750kB 1080p image with detailed areas and areas with gradients. Highly unscientific, N=1 results: - Guetzli at q=84 (the minimum allowed by Guetzli) takes 47s and produces a 403kB image. - Jpegli at q=84 takes 73ms (MILLIseconds) and produces a mostly-indistinguishable 418kB image. "Mostly" because: A. it's possible to find areas with subtle color gradients where Guetzli does a better job at keeping it smooth over a large area. B. "Little specks" show a bit more "typical JPG color-mush artifacting" around the speck with Jpegli than Guetzli, which stays remarkably close to the original Also, compared to the usual encoder I'm used to (e.g. the one in GIMP, libjpeg maybe?), Jpegli seems to degrade pretty well going into lower qualities (q=80, q=70, q=60). Qualities lower than q=84 are not even allowed by Guetzli (unless you do a custom build). I'm immediately switching my "smallify jpg" Nautilus script from Guetzli to Jpegli. The dog-slowness of Guetzli used to be tolerable when there was no close contender, but now it feels unjustified in comparison to the instant darn excellent result of Jpegli.
- JyrkiAlakuijala 3y agoThank 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.
- Waterluvian 3y agoThis is the kind of realm I'm fascinated by: taking an existing chunk of something, respecting the established interfaces (ie. not asking everyone to support yet another format), and seeing if you can squeeze out an objectively better implementation. It's such a delicious kind of performance gain because it's pretty much a "free lunch" with a very comfortable upgrade story.
- terrelln 3y agoI agree, this is a very exciting direction. We shouldn’t let existing formats stifle innovation, but there is a lot of value in back porting modern techniques to existing encoders.
- kloch 3y ago> 10+ bits. Jpegli can be encoded with 10+ bits per component. If you are making a new image/video codec in 2024 please don't just give us 2 measly extra bits of DR. Support up to 16 bit unsigned integer and floating point options. Sheesh.
- Retr0id 3y agoIt's not a new codec, it's a new encoder/decoder for JPEG.
- whywhywhywhy 3y agoThis should have been in a H1 tag at the top of the page. Had to dig into a paragraph to find out Google wasn’t about to launch another image format supported in only a scattering of apps yet served as Image Search results.
- Retr0id 3y agoIt is. (well, h3 actually) > Introducing Jpegli: A New JPEG Coding Library
- JyrkiAlakuijala 3y agoI 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.
- Timon3 3y agoFrom their Github: > Support for 16-bit unsigned and 32-bit floating point input buffers. "10+" means 10 bits or more.
- johnisgood 3y agoWould not ">10" be a better way to denote that?
- littlestymaar 3y agoWhy is it written in C++, when Google made Wuffs[1] for this exact purpose? [1]: https://github.com/google/wuffs https://github.com/google/wuffs
- ramrunner0xff 3y agothis is a valid question why is it being downvoted?
- SunlitCat 3y agoMaybe because the hailing for yet another "safe" language starts to feel kinda repetitive? Java, C#, Go, Rust, Python, modern C++ with smartpointer,... I mean a concepts for handling files in a safe way are an awesome (and really needed) thing, but inventing a whole new programming language around a single task (even if it's just a transpiler to c)?
- vinkelhake 3y agoOne of the advantages with wuffs is that it compiles to C and wuffs-the-library is distributed as C code that is easy to integrate with an existing C or C++ project without having to incorporate new toolchains.
- littlestymaar 3y ago> Maybe because the hailing for yet another "safe" language starts to feel kinda repetitive? Ah yeah, because the endless stream of exploits and “new CVE allows for zero-click RCE, please update ASAP” doesn't feel repetitive? > I mean a concepts for handling files in a safe way are an awesome (and really needed) thing, but inventing a whole new programming language around a single task (even if it's just a transpiler to c)? It's a “single task” in the same way “writing compilers” is a single task. And like we're happy that LLVM IR exists, having a language dedicated to writing codecs (of which there are dozens) is a worthwhile goal, especially since they are both security critical and have stringent performance needs for which existing languages (be it managed languages or Rust) aren't good enough.
- simonw 3y ago> High quality results. When images are compressed or decompressed through Jpegli, more precise and psychovisually effective computations are performed and images will look clearer and have fewer observable artifacts. Does anyone have a link to any example images that illustrate this improvement? I guess the examples would need to be encoded in some other lossless image format so I can reliably view them on my computer.
- n2d4 3y agoYou can find them in the mucped23.zip file linked here (encoded as PNG): https://github.com/google-research/google-research/tree/master/mucped23#results https://github.com/google-research/google-research/tree/mast...
- simonw 3y agoThanks - I downloaded that zip file (460MB!) and extracted one of the examples into a Gist: https://gist.github.com/simonw/5a8054f18f9ea3c560b628b16b00f32e https://gist.github.com/simonw/5a8054f18f9ea3c560b628b16b00f... Here's an original: https://gist.githubusercontent.com/simonw/5a8054f18f9ea3c560b628b16b00f32e/raw/4dba2c12cde6b9d1f5afccff36fccc2ad57fcbb7/originals-1624487.png https://gist.githubusercontent.com/simonw/5a8054f18f9ea3c560... And the jpegli-q95- version: https://gist.githubusercontent.com/simonw/5a8054f18f9ea3c560b628b16b00f32e/raw/4dba2c12cde6b9d1f5afccff36fccc2ad57fcbb7/jpegli-q95-yuv444-1624487.png https://gist.githubusercontent.com/simonw/5a8054f18f9ea3c560... And the same thing with mozjpeg-a95 https://gist.githubusercontent.com/simonw/5a8054f18f9ea3c560b628b16b00f32e/raw/4dba2c12cde6b9d1f5afccff36fccc2ad57fcbb7/mozjpeg-q95-yuv444-1624487.png https://gist.githubusercontent.com/simonw/5a8054f18f9ea3c560...
- tedunangst 3y agoWhat are the file sizes for those two?
- edflsafoiewq 3y agoEdit: I'm dumb.
- kaladin-jasnah 3y agoI wonder if Google will make a JPEG library with https://github.com/google/wuffs https://github.com/google/wuffs at some point.
- greenavocado 3y agoGoogle has a direct conflict of interest: the AVIF team.
- deleted 3y ago[deleted]
- jeffbee 3y agoDid you mean other than the jpeg decode that is already in wuffs?
- lxgr 3y agoThey'll do literally anything rather than implementing JPEG XL over AVIF in Chrome, huh? I mean, of course this is still valuable (JPEG-only consumers will probably be around for decades, just like MP3-only players), and I realize Google is a large company, but man, the optics on this...
- whywhywhywhy 3y agoIf you do creative work countless tools just don’t support webp, AVIF or HEIF. It’s so prominent running into files you can’t open in your tools that I have a right click convert to PNG context menu
- jiggawatts 3y agoThey don’t support it because Chromium doesn’t. Because Chromium doesn’t support it, Electron doesn’t. Because Electron doesn’t, Teams and other modern web apps and web sites don’t either, etc… If Google just added JPEG XL support instead then it would be… a supported alternative to JPEG. You’re saying working in that is a waste of time because… it’s not supported.
- n2d4 3y agoChromium does support WebP and AVIF, yet parent's tools don't.
- The_Colonel 3y agoMaybe because WebP and AVIF are actually not that great image formats. WebP has been critiqued as a very mediocre improvement over JPEG all the way since its introduction. These formats are in Chromium because of Google politics, not because of their technical merit.
- deleted 3y ago[deleted]
- modeless 3y ago
- jbverschoor 3y agoGoogle sure did a shitty job of explaining the whole situation. JpegXL was kicked out. This thing is added, but the repo and code seems to be from jxl. I'm very confused.
- JyrkiAlakuijala 3y agoIt was just easiest to develop in libjxl repo. All test workers etc. are already setup there. This was done by a very small team...
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- tambourine_man 3y agoIs there an easy way for us to install and test it?
- aendruk 3y agonixpkgs unstable (i.e. 24.05) has it at ${libjxl}/bin/cjpegli
- miragecraft 3y agoI'm currently using it via XL Converter. https://codepoems.eu/xl-converter/ https://codepoems.eu/xl-converter/
- ronjouch 3y agoIn Arch it's packaged in libjxl as /usr/bin/{c,d}jpegli . See https://archlinux.org/packages/extra/x86_64/libjxl/ https://archlinux.org/packages/extra/x86_64/libjxl/ , section "Package Contents" at the bottom.
- ctz 3y agoFrom the people who bought you WebP CVE-2023-41064/CVE-2023-4863...
- vanderZwan 3y agoNo, these are not the WebP people. These are Google's JXL people.
- JyrkiAlakuijala 3y agoI designed WebP lossless and implemented the first encoder for it. Zoltan who did most of the implementation work for jpegli wrote the first decoder.
- vanderZwan 3y agoOk well, in that case I'll label you two as the Renaissance men of image formats
- JyrkiAlakuijala 3y agoHaha. Thank you!
- asicsarecool 3y agoAwesome google. Disable zooming on mobile so I can't see the graph detail. You guys should up your web game
- politelemon 3y agoMany sites do this out of a misguided notion of what web development is. FWIW Firefox mobile lets you override zooming on a site.
- pandemic_region 3y ago> FWIW Firefox mobile lets you override zooming on a site. What in heavens name and why is this not a default option? Thankee Sai!
- modeless 3y agoChrome also has an option for this and it's great
- _carbyau_ 3y agoHaving just searched a little for this, to turn this on you need about:config. Apparently about:config is still not available on Firefox Mobile main release it seems. Supposedly available on Dev/Beta/Nightly or similar - unverified statement though. Annoying.
- therealmarv 3y agooh, probably we will get it soon in ImageOptim then https://imageoptim.com/ https://imageoptim.com/
- vladstudio 3y agoThanks in advance!
- mgraczyk 3y ago> Jpegli can be encoded with 10+ bits per component. How are the extra bits encoded? Is this the JPEG_R/"Ultra HDR" format, or has Google come up with yet another metadata solution? Something else altogether? Ultra HDR: https://developer.android.com/media/platform/hdr-image-format https://developer.android.com/media/platform/hdr-image-forma...
- lonjil 3y agoIt's regular old JPEG1. I don't know the details, but it turns out that "8 bit" JPEG actually has enough precision in the format to squeeze out another 2.5 bits, as long as both the encoder and the decoder use high precision math.
- actionfromafar 3y agoWow, this is the first time I heard about that. I wonder if Lightroom uses high precision math.
- donatzsky 3y agoThis has nothing to do with Ultra HDR. It's "simply" a better JPEG encoder. Ultra HDR is a standard SDR JPEG + a gain map that allows the construction of an HDR version. Specifically it's an implementation of Adobe's Gain Map specification, with some extra (seemingly pointless) Google bits. Adobe gain Map: https://helpx.adobe.com/camera-raw/using/gain-map.html https://helpx.adobe.com/camera-raw/using/gain-map.html
- mgraczyk 3y agoThanks, I was on the team that did Ultra HDR at Google so I was curious if it was being used here. Didn't see anything in the code though so that makes sense.
- donatzsky 3y agoSomething I've been wondering about with the Ultra HDR format, is why did you add the Google GContainer? As far as I can tell, it doesn't do anything that the MPF part doesn't already.
- lars_thomas 3y agoSorry for perhaps missing it but it states "It provides both a fully interoperable encoder and decoder complying with the original JPEG standard". Does that mean that jpegli-encoded images can be decoded by all jpeg decoders? But it will not have the same quality?
- lonjil 3y agoJpegli encoded images decode just fine with any JPEG decoder, and will still be of great quality. All the tests were done with libjpeg-turbo as the decoder. Using Jpegli for decoding gives you a bit better quality and potentially higher bit depth.
- 01HNNWZ0MV43FF 3y agoSort of like the quality vs. speed settings on libx264, I suppose jpegli aims to push the Pareto boundary on both quality and speed without changing the decode spec
- lars_thomas 3y agoThanks, sounds great! Not sure if you are part of the research team but a follow up question nevertheless. Learning from JpegXL, what would it take to develop another widely supported image format? Would the research stage already need to be carried out as a multi-corporate effort?
- JyrkiAlakuijala 3y agoMulti-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.
- lonjil 3y ago
- edent 3y agoI'd love to know what "Paradigms of Intelligence" means in this context.
- larodi 3y agoI would've loved to see side-by-side comparison... after all we talk visuals here, right? So as this old saying goes: a hand to touch, an eye to see. Not underestimating the value in this, but the presentation is very weak.
- pizlonator 3y agoVery interesting that new projects like this still use C++, not something like Rust.
- mkl 3y agoWhen your aim is maximum adoption and compatibility with existing C++ software, C++ or C are the best choice. When you're building on an existing C++ codebase, switching language and doing a complete rewrite is very rarely sensible.
- LeoNatan25 3y ago> 10+ bits. Jpegli can be encoded with 10+ bits per component. Traditional JPEG coding solutions offer only 8 bit per component dynamics causing visible banding artifacts in slow gradients. Jpegli's 10+ bits coding happens in the original 8-bit formalism and the resulting images are fully interoperable with 8-bit viewers. 10+ bit dynamics are available as an API extension and application code changes are needed to benefit from it. So, instead of supporting JPEG XL, this is the nonsense they come up with? Lock-in over a JPEG overlay?
- spider-mario 3y agoThis is from the same team as JPEG XL, and there is no lock-in or overlay. It’s just exploiting the existing mechanics better by not doing unnecessary truncation. The new APIs are only required because the existing APIs receive and return 8-bit buffers.
- aendruk 3y agoLooks like it’s not very competitive at low bitrates. I have a project that currently encodes images with MozJPEG at quality 60 and just tried switching it to Jpegli. When tuned to produce comparable file sizes (--distance=4.0) the Jpegli images are consistently worse.
- ruuda 3y agoWhat is your use case for degrading image quality that much? At quality level 80 the artifacts are already significant.
- aendruk 3y agoThumbnails at a high pixel density. I just want them up fast. Any quality that can be squeezed out of it is a bonus.
- lonjil 3y agoI recently noticed that all the thumbnails on my computer are PNG, which I thought was funny.
- londons_explore 3y agoJPEG has a fixed macroblock size (16x16 pixels), which negatively affects high resolution low bitrate images. If you must use JPEG, I suspect you might get better visual quality by halving the resolution and upsampling on the client. By doing so, you are effectively setting the lower and right halves of the DCT to zero (losing all high resolution info), but get to have 32x32 pixel macroblocks which lets you better make use of low frequency spacial patterns.
- egorfine 3y agoOh, that's interesting. I typically serve thumbnails at 2x resolution and heavily compressed. Should I try to instead compress them less but serve at 0.5x resolution?
- publius_0xf3 3y agoCan we just get rid of lossy image compression, please? It's so unpleasant looking at pictures on social media and watching them degrade over time as they are constantly reposted. What will these pictures look like a century from now?
- adamzochowski 3y agoPlease, keep lossy compression. Web is unusable already with websites too big as it is. What should happen: websites/applications shouldn't recompress images if they already deliver good pixel bitrate. Websites/applicates shouldn't recompress images just to add own watermarks.
- npteljes 3y agoIt's not the social network's job to preserve image quality. That would be mixing up the concerns.
- account42 3y agoIt's not the factory's job to preserve air quality. That would be mixing up concerns. It's not the fisherman's job to preserve ecosystem quality. That would be mixing up concerns.
- account42 3y agoThe problem here is not lossy image compression, but lossy re-compression.
- underlines 3y agoJPEGLI = A small JPEG The suffix -li is used in Swiss German dialects. It forms a diminutive of the root word, by adding -li to the end of the root word to convey the smallness of the object and to convey a sense of intimacy or endearment. This obviously comes out of Google Zürich. Other notable Google projects using Swiss German: https://github.com/google/gipfeli https://github.com/google/gipfeli high-speed compression Gipfeli = Croissant https://github.com/google/guetzli https://github.com/google/guetzli perceptual JPEG encoder Guetzli = Cookie https://github.com/weggli-rs/weggli https://github.com/weggli-rs/weggli semantic search tool Weggli = Bread roll https://github.com/google/brotli https://github.com/google/brotli lossless compression Brötli = Small bread
- billyhoffman 3y agoGoogle Zürich also did Zopfli, a DEFLATE-compliant compressor that gets better ratios than gzip by taking longer to compress. Apparently Zopfli = small sweet breat https://en.wikipedia.org/wiki/Zopfli https://en.wikipedia.org/wiki/Zopfli
- codetrotter 3y agoThey should do XZli next :D And write it in Rust
- JyrkiAlakuijala 3y agoBrotli:11 gets within 0.6 % of LZMA density but decodes 3–5x faster.
- codetrotter 3y agoYeah. But it seems to be most widely used in web browsers. I’ve never seen a .tar.br file, but I frequently download .tar.xz files. And therefore, a Rust implementation by Google of xz compression and decompression would be most welcome :)
- tialaramex 3y ago
- jug 3y agoTheir claims about Jpegli seem to make WebP obsolete regarding lossy encoding? Similar compression estimates as WebP versus JPEG are brought up. Hell, I question if AVIF is even worth it with Jpegli. It's obviously "better" (higher compression) but wait! It's 1) a crappy, limited image format for anything but basic use with obvious video keyframe roots and 2) terribly slow to encode AND 3) decode due to not having any streaming decoders. To decode, you first need to download the entire AVIF to even begin decoding it, which makes it worse than even JPEG/MozJPEG in many cases despite their larger sizes. Yes, this has been benchmarked. JPEG XL would've still been worth it though because it's just covering so much more ground than JPEG/Jpegli and it has a streaming decoder like a sensible format geared for Internet use, as well as progressive decoding support for mobile networks. But without that one? Why not just stick with JPEG's then.
- lonjil 3y ago> Their claims about Jpegli seem to make WebP obsolete regarding lossy encoding? Similar compression estimates as WebP versus JPEG are brought up. I believe Jpegli beats WebP for medium to high quality compression. I would guess that more than half of all WebP images on the net would definitely be smaller as Jpegli-encoded JPEGs of similar quality. And note that Jpegli is actually worse than MozJPEG and libjpeg-turbo at medium-low qualities. Something like libjpeg-turbo q75 is the crossover point I believe. > Hell, I question if AVIF is even worth it with Jpegli. According to another test [1], for large (like 10+ Mpix) photographs compressed with high quality, Jpegli wins over AVIF. But AVIF seems to win for "web size" images. Though, as for point 2 in your next paragraph, Jpegli is indeed much faster than AVIF. > JPEG XL would've still been worth it though because it's just covering so much more ground than JPEG/Jpegli and it has a streaming decoder like a sensible format geared for Internet use, as well as progressive decoding support for mobile networks. Indeed. At a minimum, JXL gives you another 20% size reduction just from the better entropy coding. [1] https://cloudinary.com/blog/jpeg-xl-and-the-pareto-front https://cloudinary.com/blog/jpeg-xl-and-the-pareto-front
- ksec 3y ago> I would guess that more than half of all WebP images on the net would definitely be smaller as Jpegli-encoded JPEGs of similar quality. That was what I expected a long time ago but it turns out to be a false assumption. According to Google with data from Chrome. 80%+ of images on the web are bpp 1.0+.
- udkl 3y ago[flagged]
- batch12 3y agoIt's April 3rd, confirmed
- Dylan16807 3y agoAre you asking this just because you saw the word "compression" from google, or is there a better connection I'm missing.
- atdt 3y agoWhen using Jpegli as a drop-in replacement for for libjpeg-turbo (i.e., with the same input bit-map and quality setting), will the output produced by Jpegli be smaller, more beautiful, or both? Are the space savings the result of the Jpegli encoder being able to generate comparable or better-looking images at lower quality settings? I'd like to understand whether capitalizing on the space efficiency requires any modification the caller code.
- pizza 3y agoI think the main benefit is a better decorrelation transform so the compression is higher at the same quality parameter. So you could choose whether you want better accuracy for the same quality parameter, or lower the quality parameter and get better fidelity than you would have otherwise. Probably to get both most of the time, just use JPEGXL
- JyrkiAlakuijala 3y agoThe output will be smaller after replacing libjpeg-turbo or mozjpeg with jpegli. You don't need to do any code changes.
- djha-skin 3y ago[flagged]
- Mr_Minderbinder 3y agoIt would help if the authors explained how exactly they used the Elo rating system to evaluate quality, since this seems like a non-standard and rather unusual use case for this. I am guessing that if an image is rated better than another that counts as a "win"? Finally, writing "ELO" instead of "Elo" is incorrect (this is just one of my pet peeves but indulge me nevertheless). This is some guy's name not an abbreviation, nor a prog rock band from the 70's! You would not write "ELO's" rating system for the same reason you wouldn't write "DIJKSTRA's" algorithm.
- summerlight 3y agohttps://github.com/google-research/google-research/blob/master/mucped23/compute_elo.ipynb https://github.com/google-research/google-research/blob/mast... Looks like this is the implementation.
- bArray 3y ago> In order to quantify Jpegli's image quality improvement we enlisted the help of crowdsourcing raters to compare pairs of images from Cloudinary Image Dataset '22, encoded using three codecs: Jpegli, libjpeg-turbo and MozJPEG, at several bitrates. Looking further [1]: > It consists in requiring a choice between two different distortions of the same image, and computes an Elo ranking (an estimate of the probability of each method being considered higher quality by the raters) of distortions based on that. Compared to traditional Opinion Score methods, it avoids requiring test subjects to calibrate their scores. This seems like a bad way to evaluate image quality. Humans can tend towards liking more highly saturated colours, which would be a distortion of the original image. If it was just a simple kernel that turned any image into a GIF cartoon, and then I had it rated by cartoon enthusiasts, I'm sure I could prove GIF is better than JPEG. I think that to produce something more fair, it would need to be "Given the following raw image, which of the following two images appears to better represent the above image?" The allowed answers should be "A", "B" and "unsure". ELO would likely be less appropriate. I would also like to see an analysis regarding which images were most influential in deciding which approach is better and why. Is it colour related, artefact related, information frequency related? I'm sure they could gain some deeper insight into why one method is favoured over the other. [1] https://github.com/google-research/google-research/blob/master/mucped23/README.md https://github.com/google-research/google-research/blob/mast...
- Permik 3y agoOne other thing to control for is the subpixel layout of their display which is almost always forgotten in these studies.
- bArray 3y agoI did think about this - but then I thought the variation in displays/monitors and people would enhance the experiment.
- zond 3y agoThe next sentence says "The test subject is able to flip between the two distortions, and has the original image available on the side for comparison at all times.", which indicates that the subjects weren't shown only the distortions.
- jauntywundrkind 3y agoFeels like I'm quite wrong when I said (and got flagged for saying), "Gonna cause quite the firestorm, creating something new everyone will be expected to support and maintain, after Google balked at bringing in jpegxl because they would have to support it." I still really find the messaging here to be awful. There's tons of comments asking how this related to JXL. @JyrkAlakuijala chimes in in https://news.ycombinator.com/item?id=39921484 https://news.ycombinator.com/item?id=39921484 that yes it uses JXL techniques, but also it's just using that repo because it had infrastructure which was easy to get started with (absolutely cannot argue with that). I'm not sure what my ask is, but this felt like a really chaotic release. It's unclear how much good from JPEG XL got chopped off. I'm glad for the iteration, this just seemed really chaotic & unexpected, & NIMBY-istic.
- JyrkiAlakuijala 3y agoI 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 3y agoI 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.