[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSOC - Distance Fields
From: |
Werner LEMBERG |
Subject: |
Re: GSOC - Distance Fields |
Date: |
Thu, 04 Jun 2020 07:08:59 +0200 (CEST) |
> > I think we do want a 8bit representation at least, and possible a
> > higher one.
>
> Currently I am using 32bit floats, but since freetype doesn't use
> floats I am thinking of using 32bit 16.16 fixed point instead.
I think this is the right choice for intermediate computations.
Alexei gave some hints how to use 16.16 stuff.
> The problem with 16.16 is that most of the bits in the integer part
> will not be used because I am normalizing the values between [-1.0,
> 1.0] before outputting the data.
This doesn't cause any problems.
> The whole fixed point thing is pretty new to me, so any suggestions
> will be greatly helpful.
The only remaining question is how to represent the final output data.
8bit? 16bit?
Werner
- Re: GSOC - Distance Fields, Jim Van Verth, 2020/06/03
- Re: GSOC - Distance Fields, Jim Van Verth, 2020/06/04
- Re: GSOC - Distance Fields, Behdad Esfahbod, 2020/06/04
- Re: GSOC - Distance Fields, Alexei Podtelezhnikov, 2020/06/04
- Re: GSOC - Distance Fields, Jim Van Verth, 2020/06/04
- Re: GSOC - Distance Fields, Behdad Esfahbod, 2020/06/04
- Re: GSOC - Distance Fields, Behdad Esfahbod, 2020/06/04
- Re: GSOC - Distance Fields, Alexei Podtelezhnikov, 2020/06/04
- Re: GSOC - Distance Fields, Werner LEMBERG, 2020/06/04