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

[itsab1989]

Finger crossed: succesfully read the optimized target (with the previous profiles as preconditioning):

View attachment 18662

I really hope it is working. You have a really good hand for finding bugs by the way
It stresses me out everytime but I think we have fixed a good number already

But if you want to do pre-conditioning please update the app first. I see you are at 3.7.27 and the fixes were implemented later. Sorry for pushing so many updates btw.

 

[pharmacist]

Yes it works:

Now I have to see softproofing in PS using the initial profile (upper print) and the optimized profile (lower print):

Maybe a bit distorted, because the real world result here is way more neutral in the greys for the optimized profile (using the preconditioning method). The standard profile has a greenish glow (Epson ET-18100 NO grey ink only CcMmYK inks).

 

[pharmacist]

I am impressed. What I am actually doing now is a deluxe version of the Colormunki/i1Studio 50 + 50 patch method, but now I am using 336 patches for the initial profile/target and from the first reading it generates and estimates the neutral axis for which it generates new measure points to extrapolate and determine the final true neutral axis and corrects for the greys to be printed finally as good as possible to be truely neutral.

 

[Alan G]

I am impressed. What I am actually doing now is a deluxe version of the Colormunki/i1Studio 50 + 50 patch method, but now I am using 336 patches for the initial profile/target and from the first reading it generates and estimates the neutral axis for which it generates new measure points to extrapolate and determine the final true neutral axis and corrects for the greys to be printed finally as good as possible to be truely neutral.

What do you use for the final targen command? I just printed a 506 patch set for my i1 Pro and will measure it tomorrow. I plan to do a three page patc set for the final profile (1518 patches) assuming I have no problems reading the one page at the 0.95 scale.

 

[pharmacist]

The preconditioning function in the manual option does not work. I tried 64 neutral steps in manual, but it does not appear in the targen window:

In the guided mode:

There is -n33 (neutral steps, I believe Sebastian uses this amount as standard). Unfortunately it not available in the manual mode, despite it I choosed -n64:

@itsab1989 :

I have discovered that the scanning of rows it does give an error when I reread the same row again: it presumes it is the next row, despite it has totally different patch layout. In command mode I often get the image: you have probably read row Y rather than X, do you want to proceed ? Is this known to you ? Not in the case with ChromeIQ: it just proceed when the right amount of patches is read, even if the row patch layout is totally different from the expected color values.

 

[itsab1989]

@pharmacist
Neutral axis steps bug (hopefully) fixed in 3.7.32.
For the other bug: in the measure tab warnings are suppressed by default. Enable them

 

[pharmacist]

Thanks for the update. I did not see the warning tab

 

[Alan G]

I can confirm @pharmacist finding. It also did not work in the manual mode for me either. If I drop down to the basic mode, it does work and scales up the number of near neutrals based on the total number of patches.

EDIT: sorry I replied to a bug that was just fixed. I'll download the new version.

 

[itsab1989]

Nevermind. Believe me I am sorry that things like this continue to happen. I honestly thought that the targen and printtarg logic would be the easiest part of the whole app because it basically only passes the argument through to Argyll. But once you add some conditions into it it gets more and more complex and things can start to break. I am happy for every bug that I find myself before you do so I can fix it. Hopefully this works now and nothing else is broken...

@crenedecotret
I was thinking about your preconditioning approach and how you do it. But I don't know if I got it right. What I think you do is the following:
You make a regular profiling run from start to beginning - create a target with say 500 patches, print, measure, build the profile. You then save the measurement data from the ti3 file.
On your refinement run with the preconditioning profile you do the same steps again and when the measurement is finished you merge the measurement data from the first ti3 file and the second one into one ti3 file and build the profile from that afterwards. Would this be correct?
If yes that would be something I think I could implement as well but would require more testing again. because everythiing you add could potentially break other things. I would need to find conditions for this to work so it does not interfere with any other parts of the app.
My first idea would be to make this an optional choice in the settings window like the ChromIQ clipborder. Something like "ChromIQ pre-conditioning process (idea of you)". So we could leave this optional until it is fully fleshed out.
I would then bind it somehow to enabling the pre-conditioning profile options in the create chart tabs module.
Instead of only adding the "pre_" prefix to the icc profile it would also save the content of the ti3 file into a txt
file maybe with a "good" name so I can tell the app to not delete like the other files it when the user clicks create profile again. And when the measurement is done I would then make this text file the condition that would trigger the merging process. So this data would then be added to the ti3 before it is handed over to the build profile tab / colprof. Would this be correct? Does this make sense?

Edit:
I just read the description of your process in your other thread and I am lacking the knowledge to fully understand what and how you do it