Help with GamutVision/ColorSync for i1Pro generated profile

[Robert Ardill]

Hi,

I have a printer profile that I generated using i1Profiler and an i1Pro2 which is totally weird when looked at using GamutVision  The Relative Colorimetric, Saturation and Absolute Colorimetric intents seem fine, but the Perceptual looks insane:





Doing a soft-proof in Photoshop using Perceptual seems OK, so I'm wondering if this is a problem with GamutVision.  I would really appreciate someone checking this profile on ColorSync (I don't have it).  Here is the profile:

http://www.irelandupclose.com/customer/LL/HPZ3100-Ilford-Gloss-2040Patches-Defaults-LargeTables-v4-i1Profiler.icm

Many thanks!

Robert

[Jeff-Grant]

Is this what you want? It looks fine to my untrained eyes.

[howardm]

it's a version4 profile.  I wonder if Gamutvision has a problem w/ them like so much other software does.  Can you
back up a step in i1Profiler and generate a version2 profile and see?

[Jeff-Grant]

Without wishing to confuse the issue, I just mapped it against my 3880 IGFS profile. The IGFS is the wireframe.

[digitaldog]

Doing a soft-proof in Photoshop using Perceptual seems OK, so I'm wondering if this is a problem with GamutVision.

Might be. I'd prefer to see how ColorThink shows this. See: http://www.colorwiki.com/wiki/Color_Management_Myths_26-28#Myth_26

Update: looks fine in ColorThink although there's a somewhat odd dip and bump in greens but nothing that looks anything like GamutVision. I think it's confused.

[Robert Ardill]

it's a version4 profile.  I wonder if Gamutvision has a problem w/ them like so much other software does.  Can you
back up a step in i1Profiler and generate a version2 profile and see?

Many thanks to all of you!  I apologize ... I should have tried the V2 profile. GamutVision doesn't seem to be able to handle perceptual mappings in V4.  The other intents are all fine.  The last release of GamutVision was in 2009, so it's not so surprising it has problems with V4.

Cheers,

Robert

[digitaldog]

GamutVision doesn't seem to be able to handle perceptual mappings in V4.  The other intents are all fine.

I'm not even sure why it's showing you differences based on RI. ColorThink is doing this correctly IMHO as explained below. It's the only gamut viewer I'm aware of (at least on Mac) that is doing this correctly. Not the CS utility, not X-rite's offerings.

The ONLY way to show the actual gamut of the device is to use the Absolute Colorimetric intent when calculating. This pulls the white down to paper-white and shades it accordingly. None of the methods of viewing profiles in the ColorSync Utility allow this.

[Robert Ardill]

I'm not even sure why it's showing you differences based on RI. ColorThink is doing this correctly IMHO as explained below. It's the only gamut viewer I'm aware of (at least on Mac) that is doing this correctly. Not the CS utility, not X-rite's offerings.

I don't know ColorThink at all so I can't comment on what it does. 

GamutVision allows you to view the gamut in a number of different ways (and also density response curves and other things).  If you want to see the gamut as it is, you need to either select the profile as an Input profile, or if it's selected as an Output profile the Rendering Intent should be None (in which case you can see the full gamuts of the both profiles at the same time, which is useful for comparing gamuts).

The reason for being able to select a rendering intent is that it will show the mapping from Input to Output.  So if the Input is Adobe RGB and the Output is a printer profile, the different RIs will show the gamut clipping, direction of the clipping, direction of the shifting of colors etc. Swapping Input and Output shows the reverse process.  All very useful.

I would be surprised if GamutVision is doing things wrong, seeing as how Imatest is pretty big in this business, but then software is software and bugs are always possible.

Robert

[digitaldog]

I don't know ColorThink at all so I can't comment on what it does. 

Just read the URL I provide about how the gamut viewer should use an Absolute Colorimetric intent and why.