View Single Post
Old 11-20-2012, 12:04 PM   #182
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Released ScreenSavers 0.6.N!

With a few tweaks to the ImageMagick processing settings*, meaning we get prettier covers .

(If you want to invalidate your current cover cache, delete all the cover_*.png files in the linkss/cover_cache folder before applying this update ).

[*]: Always use the Lanczos filter when resizing (I read the doc wrong, I thought the default were Lanczos when upscaling, Mitchell when downscaling [because it made sense to me, Lanczos generates sharper images than Mitchell], but it's the other way around. Since Mitchell is blurrier than Lanczos, we were getting slightly blurry images when upscaling).
And since Lanczos is sharper, it has a tendency to make JPEG artifacts stand out, so I caved, and added a dithering step (FloydSteinberg, 16 colors), which actually helps in more cases than that (every time, really ), and we end up with smaller filesizes, so, win-win .
The only downside is a longer processing time, but since we're already eating ~10s of CPU time, what's 5s more? .

Last edited by NiLuJe; 11-20-2012 at 12:12 PM.
NiLuJe is offline   Reply With Quote