• fuckwit_mcbumcrumble@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    50
    arrow-down
    1
    ·
    3 days ago

    Lossless compression doesn’t really do well for pictures of real life. For screenshots it’s ideal, but for complex images PNGs are just wayyyy to big for the virtually non noticeable difference.

    A high quality JPG is going to look good. What doesn’t look good is when it gets resized, recompressed, screenshotted, recompressed again 50 times.

      • The_Decryptor@aussie.zone
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        3 days ago

        I found quite a lot of AVIF encoders lied about their lossless encoding modes, and instead used the normal lossy mode at a very high quality setting. I eventually found one that did true lossless and I don’t think it ever managed to produce a file smaller than the input.

        Turns out, that’s a well known issue with the format. It’s just another case where Google’s marketing makes AVIF out to be fantastic, but in reality it’s actually quite mediocre.

        • lars@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          They lied about the lossiness?! I can’t begin to exclaim loudly enough about how anxious this makes me.

          • The_Decryptor@aussie.zone
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 days ago

            The funny thing is, I knew something was off because Windows was generating correct thumbnails for the output files, and at that time the OS provided thumbnailer was incapable of generating correct thumbnails for anything but the simplest baseline files.

            (Might be better now, idk, not running Windows now)

            That’s how I knew the last encoder was producing something different, even before checking the output file size, the thumbnail was bogus.

            • lars@lemmy.sdf.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 days ago

              This story is a nightmare and I’m not sure if it’s better or worse now knowing that it was ancient ICO files that tipped you off.

              Open question to you or the world: for every lossless compression I ever perform, is the only way to verify lossless compression to generate before and after bitmaps or XCFs and that unless the before-bitmap and after-bitmap are identical files, then lossy compression has occurred?

              • The_Decryptor@aussie.zone
                link
                fedilink
                English
                arrow-up
                2
                ·
                14 hours ago

                Pretty much, you can use something like ImageMagick’s compare tool to quickly check if the round trip produced any differences.

                It can be a bit muddled because even if the encoding is lossless, the decoding might not be (e.g. subtle differences between using non-SIMD vs. SIMD decoding), and it’s not like you can just check the file hashes since e.g. PNG has like 4 different interchangeable ways to specify a colour space. So I’d say it’s lossless if the resulting images differ by no more than +/- 1 bit error per pixel (e.g. 127 becoming 128 is probably fine, becoming 130 isn’t)

                • lars@lemmy.sdf.org
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  7 hours ago

                  Hey wow! Thank you!!

                  This explains a lot—including, likely, your username. Cheers!

      • morrowind@lemmy.ml
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 days ago

        jxl is a much better format, for a multitude of reasons beyond the article, but it doesn’t have much adoption yet. On the chromium team (the most important platform, unfortunately), someone seems to be actively power tripping and blocking it

        • Gregor@gregtech.eu
          link
          fedilink
          English
          arrow-up
          4
          ·
          2 days ago

          Yeah Google is trying to keep control of their image format and they are abusing their monopoly to do so

    • kernelle@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      5
      ·
      3 days ago

      I know compression has a lot of upsides, but I’ve genuinely hated it ever since broadband was a thing. Quality over quantity all the way. My websites have always used dynamic resizing, providing the resolution in a parameter, resulting in lightning fast load times, and quality when you need it.

      The way things are shared on the internet is with screenshots and social media, been like that for at least 15 years. JPG is just slowly deep frying the internet.