Hi Anurag, The rasterizer code (including SIMD) has been integrated into the FreeType > and seems to be working fine, > > Comparison images: dense and smooth renderer (outlines and dots disabled) >
This is a really nice progress indeed. The images look almost identical. Can also look at some more challenging fonts with very fine curves, eg, Windows' KUNSTLER.TTF. We need to make sure that both rasterizers are tuned to similar quality. > The performance is comparable (sometimes better) to the smooth renderer > for small font sizes, however it is several times slower for larger sizes > This is really quite stunning. I look forward to further progress. Can you confirm that straight line drawing still takes most of the time with the dense rastrerizer? > I am thinking of working on the “Direct rendering mode” next. Any pointers > regarding that would be appreciated. > I am not sure about this one. The whole point of direct mode is to leave the canvas allocation to the client. The dense rasterizer defeats this purpose. > And just for reference > > List of bugs I have encountered: > 1. Ftgrid produces weird output and crashes at large sizes(~170ppem) > > 2. The inverted bitmap pitch causes rendering differences (can be seen in > the “Q” letter of the ftview output) > Hmm. Is this only when Q is on the last row? That would be an ftview bug then. I do not see any problems with parentheses? Is this 2.12.1 demos? 3. Ftgrid crashes when selecting monochrome output Do you think this is also a pitch sign bug? 4. [TODO] lcd rendering needs to be implemented This is either three interlaced bitmaps after shifts, or 3x resolution with filtering. You should be able to copy this from smooth. Best, Alexei
