Rc1: Cleaned jpg increased file size.
Moderators: XnTriq, helmut, xnview
Rc1: Cleaned jpg increased file size.
Some jpg increase file size when Clean:Optimize huffman table is unchecked.
http://img64.imageshack.us/img64/3416/13kz1.jpg
http://img64.imageshack.us/img64/7514/22ju1.jpg
XnView 1.82 -
http://img64.imageshack.us/img64/3416/13kz1.jpg
http://img64.imageshack.us/img64/7514/22ju1.jpg
XnView 1.82 -
-
- Posts: 652
- Joined: Tue Nov 23, 2004 10:17 pm
- Location: Poland
-
- Author of XnView
- Posts: 45495
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
Re: Rc1: Cleaned jpg increased file size.
Seems to be correctTaboc wrote:Some jpg increase file size when Clean:Optimize huffman table is unchecked.

Pierre.
-
- XnThusiast
- Posts: 4608
- Joined: Sun Jul 25, 2004 9:08 pm
Re: Rc1: Cleaned jpg increased file size.
So close?xnview wrote:Seems to be correctTaboc wrote:Some jpg increase file size when Clean:Optimize huffman table is unchecked.All other software with a clean feature have this behaviour...
-
- XnThusiast
- Posts: 4441
- Joined: Sun Oct 17, 2004 4:57 am
- Location: Bordeaux, France
Not always…

… that doesn't mean it's normal and logical…Seems to be correct All other softwares with a clean feature have this behaviour…
- I tested with the image below, and got a small gain at size, ~4KB less…
—————

- Please, could you check whether you get the same ?
{ BTW : the caption on the pic tells «I've also MY anti-virus


Claude'
Clo
Last edited by Clo on Sun Jan 15, 2006 12:51 am, edited 1 time in total.
Old user ON SELECTIVE STRIKE till further notice •
-
- Posts: 121
- Joined: Fri Dec 09, 2005 8:28 am
- Location: Munich, Germany
Re: Not always…
I can confirm:Clo wrote:- Please, could you check whether you get the same ?
a) original file 58.191 bytes
b) original file cleaned with all options except optimize -> 58.191 bytes (same size)
c) original file cleaned with all options (incl. optimize) -> 54.259 bytes
d) file c) cleaned with all options except optimize -> 58.191 bytes strange!
I think from the technical point of view (pierre's view?), behaviour b) is ok. But behaviour d) is not realy easy to explain...
-
- XnThusiast
- Posts: 4608
- Joined: Sun Jul 25, 2004 9:08 pm
-
- Author of XnView
- Posts: 45495
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
-
- XnThusiast
- Posts: 1423
- Joined: Thu Dec 23, 2004 7:17 pm
- Location: Paris, France
-
- Author of XnView
- Posts: 45495
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
-
- Posts: 652
- Joined: Tue Nov 23, 2004 10:17 pm
- Location: Poland
OK, I think this solves the puzzle. But is there any need to NOT optimize Huffman tree?xnview wrote:Metadata is removed, but i think that huffmann code is rearranged.Olivier_G wrote:Seems strange that removing data actually increase filesize...
-> can't you actually remove the corresponding metadata space completely ?
X.
-
- XnThusiast
- Posts: 1423
- Joined: Thu Dec 23, 2004 7:17 pm
- Location: Paris, France
More tests:
I converted a TIFF to JPEG (no Huff Optimization) -> image without metadata: 323644 B
I added several IPTC&Comments -> 323977 B
I cleaned those metadata (no Huff Optimize) -> 323644 B
=> back to original size without metadata (optimize Huff gives 320305 B).
It looks fine to me regarding the way metadata are handled.
(and also regarding Huffman table optimization)
Olivier
I converted a TIFF to JPEG (no Huff Optimization) -> image without metadata: 323644 B
I added several IPTC&Comments -> 323977 B
I cleaned those metadata (no Huff Optimize) -> 323644 B
=> back to original size without metadata (optimize Huff gives 320305 B).
It looks fine to me regarding the way metadata are handled.
(and also regarding Huffman table optimization)
Olivier
-
- Posts: 652
- Joined: Tue Nov 23, 2004 10:17 pm
- Location: Poland