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

itsab1989

Fan of Printing
Joined
Feb 11, 2026
Messages
110
Reaction score
44
Points
50
Printer Model
Epson ET 8550, Canon Pro 300
I am glad we got this sorted. New beta 27 with some refinements is out. I you have no further concerns I would release the final once we have implemented the presets you provide(d).
I am honestly not sure anymore: the wants that I have deactivated for now should work with this new setting right? In this case I will just make them active again. And in the ti2 layout editor I added the option to tag saved ti2s as randomized although they are not.

https://github.com/itsab1989/ChromIQ/releases/tag/v3.8.0-beta.29
 
Last edited:

pharmacist

Printer VIP
Platinum Printer Member
Joined
May 29, 2007
Messages
3,118
Reaction score
1,807
Points
333
Location
Ghent, Belgium
Printer Model
SC-900 ET-8550 WF-7840 TS705
Now we know the cause of the problems. I will do some extra testing to be sure and upload some extra presets too. Most probably I will upload special randomized TC9.18 target for which I have the pxf-file.
 

itsab1989

Fan of Printing
Joined
Feb 11, 2026
Messages
110
Reaction score
44
Points
50
Printer Model
Epson ET 8550, Canon Pro 300
Now we know the cause of the problems. I will do some extra testing to be sure and upload some extra presets too. Most probably I will upload special randomized TC9.18 target for which I have the pxf-file.
In the latest release I loosened the restrictions with bi-directional a bit. I force it for i1Pro and give a one-time warning when it is active and a non-ranomized chart is loaded so the user is aware of this.
For the ColorMunki I did not force it but use the Argyll defaults now (neither -B nor -b).

In the ti2 layout editor there is now an option to force-tag a non-randomized chart as randomized so chartread will not disable bi-directional detection for it even if you don't use the argument to force it.
Basically the ti2 tells chartread that it is randomized although it is not (should have no influence on anything else, Claude says that it is only the tag that triggers this behaviour of chartread)
 
Last edited:
Top