Re^2: Batch image editing

The problem with converting to a common format and back again is that for lossy compression schemes (i.e. JPEG), you will lose image quality each time you do this. It's very much like the old "generation problem" with analouge audio recordings: the more copies you make, the more loss you have, and the poorer the quality.

Your first run or two is fine, but after a few runs, you will likely notice some image degradation.

Larry Wall is Yoda: there is no try{}
The Code that can be seen is not the true Code

Comment on Re^2: Batch image editing

Replies are listed 'Best First'.
Re^3: lossless formats (Batch image editing) by Anonymous Monk on Aug 13, 2008 at 01:02 UTC
That is true, except that it has nothing to do with converting to a common format. If you have a jpg, and open it in gimp, make some changes, and then save it again, your image quality will degrade. The only solution is to always store your images in a lossless format, and only consider jpgs to be the "end result." Much like a programmer would never delete the source code after compiling, don't delete the original RAW, or TIFF, or whatever after creating a jpg.	[reply]

Replies are listed 'Best First'.

Re^3: lossless formats (Batch image editing)
by Anonymous Monk on Aug 13, 2008 at 01:02 UTC

That is true, except that it has nothing to do with converting to a common format. If you have a jpg, and open it in gimp, make some changes, and then save it again, your image quality will degrade. The only solution is to always store your images in a lossless format, and only consider jpgs to be the "end result." Much like a programmer would never delete the source code after compiling, don't delete the original RAW, or TIFF, or whatever after creating a jpg.

[reply]