View Single Post
Old 10-15-2019, 04:26 PM   #12
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
Technically, Nickel runs @ 32bpp, so it's happily blitting to the framebuffer in BGRA, and leaving the EPDC/PxP to do the grayscaling, followed by a decimating quantization pass (unless you're on a Mk. 7, in which case it does an ordered dithering pass).

Which means feeding a grayscale image to Qt nets you an implicit conversion to RGB32 behind the scenes .

Note that, as was mentioned earlier, there are probably a number of circumstances where you won't be able to avoid scaling entirely (even if it's for something stupid like a 12 pixels margin or something). Still, you can't go wrong with the native screen's resolution, because at least you can be sure that nothing will ever ask for *larger* than that .

That said, we've pretty much all agreed on the fact that both performance and experience in an image-heavy CB(Z|R)/PDF/(K)ePub was going to be fantastically awful in Nickel anyway, so, meh.

Last edited by NiLuJe; 10-15-2019 at 04:35 PM.
NiLuJe is offline   Reply With Quote