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

[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.

Edit: I have prepared the latest release for this feature. When you create or load a file in the measure / build profile / check & refine tab it now says in the output the instrument it detected. I can build on that later and use it as a condition for adjustments.

 

[pharmacist]

Despite having the argyllcms usb drivers installed, the software does not recognize my eye one Pro/i1Pro2 device: to be corrected: it should automatically load the argyllCMS drivers.

Loading existing target, still cosmetic error page 1/2 and 2/2 (same), because it fits on a single sheet of A4

I tried both i1Pro1 and the i1Pro2 with the -a0.95 setting: no problem at all. The markers are shown with green arrows and move accordingly when a row has been read..

Feedback will continue.

 

[itsab1989]

View attachment 18647

Despite having the argyllcms usb drivers installed, the software does not recognize my eye one Pro/i1Pro2 device: to be corrected: it should automatically load the argyllCMS drivers.

Loading existing target, still cosmetic error page 1/2 and 2/2 (same), because it fits on a single sheet of A4

View attachment 18648

I tried both i1Pro1 and the i1Pro2 with the -a0.95 setting: no problem at all. The markers are shown with green arrows and move accordingly when a row has been read..

Feedback will continue.

The USB thing will be tricky for me because I do not have an i1Pro myself. For the i1Studio it should hopefully work. The detection failed in the beginning but Claude then did something to detect the device I had connected. So hopefully this is better. But I‘ll try.

Can you tell me the exact settings you used for you chart or attach the ti2 file? I can never reproduce that issue with the two pages on my machine.

Edit: May it be that you loaded this chart instead of creating it? Claude found a bug that it fixed for creating new charts but not for loading already created one. Also working on the driver install issue.

Edit2: try 3.7.24

Edit3: wait for 3.7.26 please

 

[pharmacist]

I am getting problems with working with a target that uses data from a preconditioning profile.

For sake of ease I am using the standard guided workflow (don't limit strip length). The first step creating the initial profile is no problem. Now afterwards you get the ability to use this profile as an preconditioning profile to look up the neutral axis for which a new set (again: 576) will be generated. Now after this the scanning does no longer show the scanning markers (green arrows that move along towards the next row when the previous has been read succesfully). Now after reading this secondary target and I try to produce the final optimized target an error message that the target can not be created....

Also when choosing the dark mode: there is no longer a choice between guided and manual: only manual:

Also the same for the light theme:

To restore the guided/manual choice I have to choose the restore factory defaults

Manual loading ti2 file for scanning: the green markers are GONE.....

The computer says NOOOO (ti2 file based on data from preconditioning profile):

 

[Alan G]

@pharmacist - I wonder if something gets broken with the constant versions. One of the problems with the installations is that the zip files are not versioned and if you don't change something, it will just overwrite a previous version when you unzip it. I did a quick profile the other day that used a one page precondition profile to create a final profile using a two page patch set. I had no issues at all running targen under the GUI. I got a rather nice profile. This weekend I plan to try again using a higher one page patch set to see if the i1 Pro will read it and then use that one for a final profile with a 3 page set created from that.

 

[itsab1989]

@pharmacist
I see you had selected the option to enable calibration option in the settings. In this mode it is intentional that the guided mode disappears. For one I think that if a user really wants to calibrate his printer I think he should be comfortable using the manual modes and on the other hand I needed the space for new modules in the new tab 4.

For the highlighter issue: would there be a way for you to send me the exact files you used for measurement so I can try it on my own machine. That way it would be much easier to figure out what is going wrong.

For the build failure: it is just a guess but windows sometimes has issues with very long file names. That of course should not get in the way but needs fixing. Please have a look into the log files or send them to me so I can check (or maybe for testing try to give the ti3 file a shorter name and load it again). Otherwise it is just guessing on my side.

Edit: In your screenshot I have noticed that the long file name messed up the button layout in the measure tab. Also worth fixing I think.

Edit 2: it says the colprof issue is because of the „.icm“ in the folder and file name. Working on a fix for this. For the highlighter I would still need the files I guess