[Tool] ChromIQ – a macOS and Windows GUI for ArgyllCMS printer profiling (v3.0.0 beta 10)

[itsab1989]

I just wanted to post you the questions that AI gave me
So is it working as intended now?

Edit: I just released 3.5.10 with improvements in the measure tab. I have a feeling though that the patch consistency settings default is too strict. I mean the user can change it but it might cause confusion.


I'll post the AI text anyway in case it might be useful:

Thanks for the detailed report — I tried to reproduce on my end (Windows, 240-patch RGB chart with a preconditioning
profile, sRGB.icm as -S source) and the build completed cleanly, so I need a bit more info from you to pin this down.

A few things I noticed:

1. The colprof warnings on their own are harmless. Warning - gammap internal: input bounds has changed! is ArgyllCMS's
gamut-mapping optimizer adjusting its working bounds mid-iteration. It's noisy but doesn't normally break the
profile. However, many repetitions of it combined with a profile that iccview.de rejects suggests the underlying .ti3
measurements are off — gammap is reacting to outlier data, not causing it.

2. Your ArgyllCMS lives at CArgyllCMS\bin — that's a manual install location. ChromIQ auto-detects CProgram
Files\ArgyllCMS\bin and %LOCALAPPDATA%\ArgyllCMS\bin, so you must have pointed it there in Preferences. Which version
is it? Run CArgyllCMS\bin\colprof.exe -? and the first line will show the version — I'd like to make sure it matches
ChromIQ's tested 3.5.0.

3. The hang during chart generation with a preconditioning profile is the part I most want to understand. targen -c
<profile> can take a while, but it shouldn't lock up. If the preconditioning .icc is malformed, targen can spin for a
long time trying to invert the CLUT.

To dig in, could you share:

1. The output of CArgyllCMS\bin\colprof.exe -? (just the version line)
2. Where the preconditioning profile came from — a previous ChromIQ run, or imported from somewhere else?
3. The .ti3 file and the preconditioning .icc, attached or zipped
4. The ChromIQ log file (%LOCALAPPDATA%\ChromIQ\logs\chromiq.log or wherever it lands on your system)
5. Your targen settings for that run — patch count, grey steps, good-mode on/off

Once I can see the .ti3 I should be able to tell whether this is a measurement-data issue, a preconditioning-profile
issue, or something in ChromIQ's pipeline staging the file wrong.