Quote:
Originally Posted by stumped
lets say you improve the compression by 10% and save an amazing 30kb per book
what could you possibly use that for ?
|
10% more books.
Quote:
Originally Posted by j.p.s
It is very common for compression algorithms that squeeze out a bit more compression at the cost of a lot of CPU to have decompressors that use little or no additional CPU.
|
Yep, or just being much more intelligent with the parameters it's choosing.
Like with PNG compression, there are a million valid ways to compress.
Zopfli is an alternative very CPU-heavy algorithm Google came up with, but resulted in a smaller PNG (~3-8%) by selecting better parameters.
Takes the same exact amount of resources to decompress it though.
I gave some examples way back in 2013:
https://www.mobileread.com/forums/sh...45#post2499645
(Since then, ScriptPNG has been superseded by pingo.)
Quote:
Originally Posted by Sekkei
Sadly my Voyage has only 4GB and I like manga, I even recompress them manually to a per page ~180KB High-res low-color PNG, but as you can imagine, there is not space left if you want to carry your favorite manga saga on the go :/
|
Manga? PNGs?!!? Then definitely run it through pingo and you'll probably save a hell of a lot of space. At least 3-8%, but depending on the complexity and if the publisher compressed previously, you may even save more.
If they're B&W/grayscale/<256-colors, you could also convert it to Indexed images for you and save A TON of space. (In the example linked above, my chart went from 143.1 KB -> 44.5 KB.)