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

[itsab1989]

Edit:
@pharmacist
Whenever I mentioned you in the release notes on GitHub it automatically linked to the GitHub account of a user with the same username you have here. In case this is actually you I would kindly ask that if you find any issues in your testing on the weekend or want to suggest a feature it would be nice if you did this on GitHub. When you open an issue there you should be presented with with a template for bug reporting. For me this is a convenience thing because I can simply copy the link to the issue someone created into Claude Code and without me giving much further instructions it tries to solve this. It can even automatically ask the user (in my name though) for further information or testing which is pretty handy.

 

[itsab1989]

@pharmacist
It just came to my mind that my app would not cover all possible error, warning and info messages from the Argyll apps. So I let Claude read the source code of Argyll to figure out which kind of messages it could give the user, recognize them and present the user with a pop up window instead.

While doing so i figured that some instruments don’t support all of the options that chartread, colprof and maybe profcheck provide. If you choose one of those options you should now be presentet with a pop up window.

But I remembered that yesterday I inplemented a condition for the bi-directional strip recognition in chartread that depends on the instrument that is mentioned in the ti2 file. I think I could do a similar thing for those options. If the ti2 or (for colprof) the ti3 file is for a Colormunki it could just grey out and ignore those options to avoid wrong input completely. I would just have to know which options are not suited for that device.

Godd idea? Bad idea?

 

[pharmacist]

Actually it is chartread that decides whether or not you want mono or bidirectional reading: You might remember the fact that I have made i1Pro targets BUT reading with my Colormunki: it will throw an error that the layout is made for i1pro, but you can perfectly read with the Colormunki and vice-versa. The bidirectional reading can be disabled with an argument in chartread.exe

 

[Alan G]

Once you get going with an i1 Pro, bidirectional reading can save you a few seconds on each pass which adds up to maybe 90 seconds on a letter size patch set. I'm so used to bidirectional reading that I ended up with a horrible profile when I realized that I had it disabled in the new app.

 

[itsab1989]

I know, I know… sorry for that

@pharmacist
I think the chartread message you are referring to is more or less just an info and will let you do the measurement anyway.
But what I mean is when you load a ti2 file into the measure tab - there are for example those options for D50, D65 and so on - this have no effect or will give an error message when used in combination with a Colormunki.
I could make it so that when a ti2 file for a Colormunki is loaded in this tab those options would be greyed out and ignored. That way the user would see before starting the measurement that those are not suited for his device. Would save the user reading the error message…
And the same for the ti3 files in the build profile tab. Some options throw an error message when the measurement data was created with the colormunki. I would just grey them out when such a ti3 file is loaded.
I am just not sure what those options are.