On 02.06.2010, at 10:02, [email protected] wrote:
> The reason to normalize to 0..1.0 range each stage is because
> ICC profiles are built to work in in encoded mode. Take for
> example a 16 bits profile. Each stage in LutAtoB goes from 0
> to 0xffff, and stages know nothing about colorspaces. It would
> be very complex for the CMM o understand all the tricks profile
> creator has used and decode to a different range depending on
> the space. So, in order to allow unbounded mode, 16 bits are
> converted to floating point by using a factor of 1/65535.
> With that I keep the profile behavior, increase the precision,
> make 8/16/float conversions easier and allow unbounded mode.
I see. How are you dealing with the new floating point DToBx/BToDx tags?
If I join (create a transform) from a matrix shaper display profile to an BToDx
profile LCMS will use the 0...1.0 normalized encoding for the matrix shaper
profile, then un-normalize to the full PCS encoding and continue evaluation of
BToDx?
Is that it? Or are you normalizing the BToDx MPE's values first.
Best regards
Mark
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Lcms-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lcms-user
