public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: antlists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Your opinion on jpeg encoders, please
Date: Thu, 7 Jan 2021 17:12:07 +0000	[thread overview]
Message-ID: <93bee44a-f976-194a-7c24-f5c7daf95c22@youngman.org.uk> (raw)
In-Reply-To: <rt5ra0$5a0$1@ciao.gmane.io>

On 07/01/2021 02:22, Nikos Chantziaras wrote:
> On 04/01/2021 23:37, Frank Steinmetzger wrote:
>> 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.

> You lose some extra quality when doing this due to recompression. What 
> you should do is save in a lossless format (like png or bmp) and then 
> convert that to jpg.
> 
If you're doing that (which I recommend), I set my camera to "raw + 
jpeg", and then dump the raw files to DVD. That way, it doesn't matter 
what happens to the jpegs as you can always re-create them.

If you've only got jpegs (why are you using a rubbish camera :-) then 
just dump the original jpegs to DVD - that's why what Google do is so 
bad - they compress it to upload it from your Android phone, and then 
delete the original! AND THAT'S THE DEFAULT !!!

Cheers,
Wol


  reply	other threads:[~2021-01-07 17:12 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 [this message]
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 ` [gentoo-user] " Mark Knecht

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=93bee44a-f976-194a-7c24-f5c7daf95c22@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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