Re: Custom scanner profiles
Re: Custom scanner profiles
- Subject: Re: Custom scanner profiles
- From: Clemens Beisch <email@hidden>
- Date: Thu, 16 Dec 2004 23:55:39 +0100
If you like, you can send me your ICCs and I convert them to 8bit.
It's not a high level solution, but if it works :-)
Best regards,
Clemens Beisch
Am 16.12.2004 um 23:13 schrieb David Wollmann:
I've been looking at my Trident scanner profile issue a little
further. This is my problem, if I choose one of my custom made scanner
profiles in Trident and then activate the L*a*b* correction tool, it
has a check box in it's pallet, once I update the preview then I see
about 20 points of excess yellow. If I go back to the ColorSync Tab in
Trident and choose a different profile, say the one supplied by
Howtek, then the yellow is removed from the preview again and the
final scan.
I have limited tools for looking at these profiles. When I look at the
white point settings they are similar to the supplied Howtek profile.
So I don't think that is a problem, plus the custom profile will work
fine as long as I don't turn on the L*a*b* correction tool in Trident.
The one difference that I can see is that the supplied Howtek profile
for Trident has an A2B0 table that is 8 bit and my new profile has an
A2B0 table that is 16 bit. In doing further testing I noticed that a
supplied Ektacolor input profile that is 16 bit also gives me a strong
unwanted base tint but yet a Kodak DCS 16 bit input profile will not
have the excess base tint.
The difference in these profiles with 16 bit A2B0 tables is the number
of grid points. My custom profile has 33 grid points, the Ektacolor
has 32 and the DCS profile has 16 grid points, which is the only one
that does not have the excess base tint when the L*a*b* correction
tool is activated.
Is the A2B0 table used for the preview, or just for the conversion
from source to my working space color in Photoshop?
I have other input profiles that are 8 bit with grid points above 16
and they preview fine. It appears that a profile with an A2B0 16 bit
table with grid points above 16 will not work properly with Trident
3.5.5. when using the L*a*b* correction tool.
Would a profile with a 16 bit A2B0 table with grid points above 16
necessarily cause this odd preview behavior?
David.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
**************************************************************
Thalkirchner Strasse 107, D-81371 München, Germany
phone: +49 (0)89 7213769, email@hidden
**************************************************************
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden