View Single Post
Old 04-08-2009, 11:53 AM   #5
nrapallo
GuteBook/Mobi2IMP Creator
nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.nrapallo ought to be getting tired of karma fortunes by now.
 
nrapallo's Avatar
 
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
Quote:
Originally Posted by pruss
You could also reduce the compression accuracy of the jpeg files. I've just posted a new version of explode with a --jpeg-quality=xxx switch (untested). I noticed that the previous version always set the quality to 100 (!). If you set it to 85 or so, you might find a nice improvement, unless of course your further conversion tools themselves reduce the jpeg quality.
Actually, I was thinking of using instead (in place) .gif images with 256-colors (yields about 50% filesize savings) and will see if using a 16-color/grayscale .gif will reduce this any further. Worth a shot!

However, I will also try your new --jpeg-quality switch. "Whatever works best" is my motto...

Thanks again!
nrapallo is offline   Reply With Quote