Re: [Lcms-user] Null values for input or output profiles and ARGB

[<ma...@li...>]

Hi,

Humm... a single profile has really no sense at all.

You cannot apply a single profile to RGB data. A transform needs two =20
profiles at least. E.g. "convert data from the RGB space A to RGB space =
B"
But if you only specify a profile then to what space B is supposed to=20
be converted the RGB data A?

All you could do with  a profile alone would be to convert data  to XYZ =
or Lab,=20
depending on PCS. In such case, you could use cmsCreateXYZProfile() or=20
cmsCreateLabProfile() for output profile. Internally, lcms is doing a =
PCS=20
exportation when  any of these profiles are found.

Regarding TYPE_ARGB_8, it works fine to me...?

Please give a try on the latest beta of lcms. It has a Delphi sample =
dealing=20
with that: http://www.littlecms.com/ver110.htm If it doesn't work, then =
we=20
could try to see what is going wrong.

Regards,
Mart=ED Maria
The little cms project
http://www.littlecms.com
ma...@li...
=20

----- Original Message -----=20
  From: Jon Hopkins=20
  To: 'lcm...@li...'=20
  Sent: Friday, February 28, 2003 11:44 AM
  Subject: [Lcms-user] Null values for input or output profiles and ARGB


  Hi,

  =20

  Is there anyway that I can use a null value for an input or output =
profiles so that I can just use say a scanner profile, or just the =
monitor profile?

  The other question I have is that the ARGB option I wanted for =
Graphics 32 in Delphi does not work correctly. I have used the suggested =
constant

  , TYPE_ARGB_8, to do this, as well as other combinations using =
SWAPFIRST_SH, DOSWAP_SH etc and none work.=20

  The library uses a 32-bit value with Alpha as the MSB and Blue as the =
LSB, is there a reason why this should not work?

  =20

  Thanks,

  =20

  Jon