public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Your opinion on jpeg encoders, please
Date: Tue, 12 Jan 2021 11:54:27 -0700	[thread overview]
Message-ID: <CAK2H+edNuiy25GAfY-aGYMce5Acv7Xdc0KNz83xYBV1=Z-iLCg@mail.gmail.com> (raw)
In-Reply-To: <X/OKnhCvbi17X4mJ@kern>

[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]

On Mon, Jan 4, 2021 at 2:38 PM Frank Steinmetzger <Warp_7@gmx.de> wrote:
>
> Hi all,
>
> this is not really a Gentoo-specific question, but some of you know your
way
> around stuff, so here goes.
>
> When I edit photos, I like to shrink and recompress them to save on space,
> but not mangle them too much in the process to lose quality. So for
average
> images I tend to use a quality setting between 80 and 86, very bad shots
> such as defocussed or blurred ones just 70. And for the really good ones
> (crystal sharp, portraits, extraordinary motives etc) 90 and more.
>
> In the far past I’ve been using Gimp, but for some years now mostly
Showfoto
> (the editor from Digikam) due to its more useful photo enhancement
features.
>
> However I noticed that the latter procuces larger files for the same
quality
> setting. So currently, I first save with a very high setting from Showfoto
> and then recompress the whole directory in a one-line-loop using
> imagemagick’s convert. I have the impression that it produces far smaller
> files at the same visual quality.
>
>
> Now I know that one can’t fully compare quality settings of different
> encoders, but it started me wondering: which is really “better”? Or maybe
> just a little more enhanced, or up-to-date from an algorithmic standpoint?
>
> Just because many distros and tools use libjpeg, that doesn’t mean it’s
the
> best one out there. Gimp, showfoto and convert use different encoders,
> because compressing the same PNG with the same JPEG setting does not
result
> in three identical files.
>
> Does any of you have an opinion on that matter?
> Cheers.
>
> --
> Gruß | Greetings | Qapla’
> Please do not share anything from, with or about me on any social network.
>
> What do you call a man with a seagull on his head? – Cliff.

This topic comes up a lot with astrophotography. I took about 150 24M pixel
shots last night. It uses a lot of disk space.

From my reading - which isn't a lot - it seems to be technically superior
to simply downsample the original and then compress with jpeg if you need
to go that far vs using higher jpeg compression ratios on the original.

I have no data to back this up and it probably depends a lot on your source
material so YMMV but it's an option.

HTH,
Mark

[-- Attachment #2: Type: text/html, Size: 2703 bytes --]

      parent reply	other threads:[~2021-01-12 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 21:37 [gentoo-user] Your opinion on jpeg encoders, please Frank Steinmetzger
2021-01-05  2:55 ` Walter Dnes
2021-01-07  2:22 ` [gentoo-user] " Nikos Chantziaras
2021-01-07 17:12   ` antlists
2021-01-11 19:26     ` Frank Steinmetzger
2021-01-12  2:00       ` antlists
2021-01-12  8:24       ` Neil Bothwick
2021-01-12 18:54 ` Mark Knecht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK2H+edNuiy25GAfY-aGYMce5Acv7Xdc0KNz83xYBV1=Z-iLCg@mail.gmail.com' \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox