RE: Photoshop 6/7 problems with OptiCAL Monitor profiles
RE: Photoshop 6/7 problems with OptiCAL Monitor profiles
- Subject: RE: Photoshop 6/7 problems with OptiCAL Monitor profiles
- From: "Bob Chase" <email@hidden>
- Date: Thu, 13 Feb 2003 18:56:12 -0500
C David,
In a message dated 2/13/03 2:22 PM, email@hidden writes:
>
As I recall, that was *me* you demonstrated that to at PhotoPlus...
Hmmm, wish I'd known! I appreciate all the assistance you provide to the
readers of this list, including me.
>
Are the info pallet numbers of some significance to you? I ignored that
part
>
entirely in my testing, as all I'm interested in is the profile's own tags,
>
and Photoshop's reading of them.
Yes, they had been important anyway, because those info palette numbers are
what OptiCAL is representing to me as the Phosphors profiling results. If
they're meaningless, inaccurate, or misleading, why present them? They also
matched the formerly available .ams file numbers and "File->Print
Information..." numbers. They just never corresponded to the profile
primaries values displayed in PS (unless I built the profile using the .ams
output file.) Maybe OptiCAL is incorrectly translating these numbers in the
process of creating their profiles? It seems at least one set of values or
the other is off, requiring some form of corroboration to determine which,
and ColorVision to determine why.
>
Again, if this happens due to the math in the info palette, and has no
>
effect on the profile tags and Photoshop's use of the profile, then its not
a
>
functional problem, rather a reporting inconvenience...
The key question remains; which side of the equation contains the error? If
it's only a "reporting inconvenience" it should be fixed. On the other
hand, if there's nothing wrong with the profile structure, but it contains
an inaccurate hand-off of values during its build, then there's a worse
problem. I don't have the means to make that determination. I only have
what I observe through the interfaces of OptiCAL and Photoshop, and what
ColorVision's tech support tells me.
>
Have you considered that it might be your DTP92 that is the factor here?
I don't think my DTP92 could be a factor. As mentioned previously, at
PhotoPlus, and with ColorVision tech support's own observations on this
issue, that wasn't involved. It's only measuring, OptiCAL is applying - so
I don't think the DTP92 could cause differences between Info Palette numbers
and PS interpretation.
>
>>ColorVision tech support said that the issue was seen with any ICC
profile,
>
>>not just profiles created by ColorVision.
>
Hard to know, since no other application's profiles can be read in the
>
OptiCAL info window...
Agreed; my understanding that the profile values themselves weren't handed
off properly to Photoshop was based on ColorVision tech support's own
statements to me. I'm just relaying their observations which were made
using a Mac utility of which I don't have a corresponding Windows tool. (Do
you know of any profile-reading utility for Windows that won't break a
modest budget?)
Per a ColorVision Tech Support statement to me:
----------------------------
Begin quote
"We have looked at this issue in the past. For some reason the values that
Photoshop displays differ from the values from the Profile. If you compare
the values displayed in the Information Window with the values that are
actually in the ICC profile you will find that they are the same. The values
that Photoshop displays are different from the values that are in the
profile."
End quote
----------------------------
Another ColorVision tech support statement to me:
----------------------------
Begin quote
"The issue of Photoshop displaying values in the Custom Color Settings
window that differ from the actual values in the ICC profile is not specific
to ICC profiles created by ColorVision. This happens with any ICC profile.
Interestingly, if the ICC profile has a whitepoint value of 5000K then
Photoshop displays the RGB values directly from the profile. If the ICC
profile has a whitepoint value of 6500K then the Photoshop RGB values can
vary from the values in the profile by as much as .019 in my testing. And if
the ICC profile has a whitepoint value of 9300K then the Photoshop RGB
values can vary by as much as .075 (using one of the standard profiles
included with windows "Trinitron Monitor G22 D93")!
This might be worth a question to Adobe to ask them what is going on here."
End quote
----------------------------
I'm a big ColorVision fan. I have great results with OptiCAL (using
workarounds), and Profiler Pro (also with some issues that I can work
around, and that were acknowledged to me by David Miller, who wrote a good
chunk of the code - another story.) Their products are very reasonably
priced, they have generous upgrade policies, and their tech support is very
responsive. I just wish they'd plug the few holes, because as we all know,
one break at any point in the color management process can cause a lot of
frustration.
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.