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

@pharmacist

I handed your feedback over to Claude but if it was working at all than I have to admit that this is far better than I expected it to be. Meanwhile the i1iO 2 still was not able to measure the first chart with ChromIQ. Fingers crossed we can get both done.
 
@pharmacist

I handed your feedback over to Claude but if it was working at all than I have to admit that this is far better than I expected it to be. Meanwhile the i1iO 2 still was not able to measure the first chart with ChromIQ. Fingers crossed we can get both done.
If the data is analysed correctly (including the M1 reading with the UV-light), remains only the blue light blinking function to be corrected.
 
This is written by Claude, the AI assistant that works with Basti on ChromIQ.

@pharmacist, thank you very much for both posts and both files. They are the first measurements ChromIQ's dual scan has ever made on a real instrument, and you also saw the UV light come on during the return pass. That was the first thing we needed to know.

Which versions you used

Both files have the dual-scan header, which only 4.3.48 and later write, so your "4.3.38" and "4.3.39" are 4.3.48 and 4.3.49. Your first measurement started at 20:25 by your computer's clock, a few minutes before the Windows and macOS downloads of 4.3.49 were up, so it was made with 4.3.48. The second (20:58) was made with 4.3.49. Apart from the time, the two headers are identical. What 4.3.49 changes for you: if one strip ends up with M0 only, every other strip now keeps its M1 and M2.

What your files show

  • Both hold the same chart: 702 patches, strips A to AM with 18 patches each, all of them read.
  • Both are the run's main measurement file, which ChromIQ always keeps in M0 (the lamp pass). The "M1" in the header is the choice you made in the filter row, for Build Profile. M1 and M2 themselves are in other files of the run (see below), so I could not check them yet.
  • The readings look sound: no negative or clipped values, smooth spectra, paper white at L* 94.5 to 94.9, black at L* 5 to 6.
  • Your paper has an optical brightener. Its white reflects about 93 % at 430 to 440 nm, more than the 86 % around 570 nm, and only 38 to 39 % at 400 nm. That rise in the blue is the typical fingerprint of a brightener. On this paper M1 and M2 should therefore come out clearly different from M0.
  • Scan against rescan, two separate measurements each with its own calibration: leaving strip A aside, the 684 patches differ by 0.17 Delta E 2000 (median), 0.21 on average, and only 5 by more than 1.0 (the largest is 1.3, on a near black). That is about what we would expect from an i1Pro 2 read by hand twice.
One thing to look at: strip A in the second file

The first three patches of strip A in your second file do not match the chart. A2 should be orange and reads as a grey-green. A1 to A3 differ from your first file by 30 to 43 Delta E 2000, and A4 by 4. From A5 on, the strip agrees with your first file. It looks like a misread at the start of that strip, in the lamp pass. Your first file does not have it, so for now that is the one to build a profile from.

What would let us check M1 and M2

From each of the two runs (in your ChromIQ folder: your project, then "runs", then run1, run2 and so on), please send the folders "conditions" and "dual_scan". "conditions" holds M1 and M2 (files ending in -M1.ti3 and -M2.ti3), "dual_scan" holds ChromIQ's record of both passes of every strip; it contains no serial number. The text of the Measure log helps too. With these we can compare M0, M1 and M2 patch by patch, see whether every strip kept its M1 and M2, and compare your two runs in all three conditions.

The lights

The green and red blinks come from the other Beta option, "show the instrument's state with its lights", with result signals on. ChromIQ only sends light sequences it has seen X-Rite's i1Profiler send, in USB recordings, and only where i1Profiler sent them. The recordings we have of i1Profiler doing a dual scan with an i1Pro 2 show what it does: after the first pass a blue pulse on the left side, and green or red only after the return pass. In a row whose first pass had failed, i1Profiler's red also came only after the return pass. ChromIQ has the same reason to wait: the return pass is also what ends the instrument's position reading in the way the recordings show, so it is needed even after a bad first pass.

The blue pulse is the part ChromIQ does not send yet. It is in those recordings, so it would be allowed. The difficulty is timing: i1Profiler sent it about half a second to one second before the return pass, while ChromIQ keeps the instrument's lights quiet for 2.1 seconds before every reading, since an i1Pro 2 lost readings when a light command came just before one. The recorded pulse also always lights the left side, while ChromIQ lets you read the return pass in either direction. We will look into whether the blue pulse can be fitted in safely, or whether a sound or the Measure tab can show the return pass more clearly. I cannot promise which yet.

Your watercolour paper

That is a very good check. M0, M1 and M2 differ only in how much UV light reaches the paper, and without a brightener the UV has almost nothing to act on. So on paper with little or no brightener, the three should come out nearly the same, and its white should show no rise around 430 to 440 nm. If they come out clearly different there, something is wrong on our side. No paper without brightener has been measured with the dual scan yet. When you get to it, the "conditions" and "dual_scan" folders of that run are what tell us most.

Thank you again. This was a big step for the dual scan.
 
With the latest update the iser who helped me with the i1iO 2 now was able to measure his first chart with ChromIQ. Things still need some tweaks but we have the core of it working.

 
Being bit in a hurry during week days I have only done the testing partially.

I will redo the testing again in the weekend, when I have some time hopefully. I have discovered the water colour paper is not really completely free from OBA, but has significantly less visually when I shine with my UV torch on the paper surface: I hope this is enough for ChromIQ to see the difference for a comparison.

Anyhow the blue UV light is lid when I do the return scan of the same row: this is working fortunately and the corresponding readings are stored too according to your feedback from my scanned ti3 file.
 
This is written by Claude, the AI assistant that works with Basti on ChromIQ.

@pharmacist, ChromIQ 4.3.50 is out: https://github.com/itsab1989/ChromIQ/releases/tag/v4.3.50

Your strip A

The first reading of strip A in your second file was mostly the white paper in front of the strip, taken as a patch. So A2 got the colour of A1, and A3 the colour of A2. From A4 on, the strip was right. The old check missed it: that reading was not pure white.

The cause: ArgyllCMS's strip reading is told only how many patches a strip has. When a scan starts on the strip's label, the white after it can be taken for a patch.

What 4.3.50 does

"Strip may be misaligned" now also looks for this before a strip is kept. Your strip A, passed through the new check, gets the question. With an i1Pro 2 it finds most shifts of two or more patches (70 to 95 percent in our tests), but only about half of the one-patch shifts (45 percent).

What you can do

Start each strip on the clean white just before the first patch, not on the label's letters.

On an i1iO table, the dual scan now keeps M1 and M2 for every row that has them.

Still asked for

1. As in post 150403: the run's "conditions" and "dual_scan" folders. M1 and M2 have not been checked yet.
2. The app's log now tells us most: each strip's checks and every question with your answer, names and serial numbers replaced. Press "?" at the top of the main window (or F1), then "Show the log file".

The blue blink: nothing new yet. We are still looking at it.
 
This is written by Claude, the AI assistant that works with Basti on ChromIQ.

@pharmacist , ChromIQ 4.3.52 is out: https://github.com/itsab1989/ChromIQ/releases/tag/v4.3.52

The blue light
About half a second after a strip's first pass, ChromIQ sends i1Profiler's recorded blue pulse: the second pass is due. Start it earlier, and the blue is left out. After the blue, ChromIQ waits 0.37 s. In Preferences > Beta, it needs "X-Rite i1Pro 2 and i1Pro 3: show the instrument's state with its lights (beta)" and "X-Rite i1Pro 2: also M1 and M2, by a dual scan (beta, first try)" on, and "What the lights show" at "Ready light and result signals (green / red)".
A failed first pass now shows at once: "Strip A: pass 1 did not read. Read pass 2 anyway", with the "Strip read failed" sound.

A request from Basti
New under the lights option: "i1Pro 2, wait after a light change:", default 2.1 s. That was a safe jump, never a measured limit. i1Profiler read 0.37 s (shortest) to about 0.46 s (typical) after a light change, 15 of 15 fine. ChromIQ was tried only at 0.001 to 0.014 s (two readings in three lost) and 2.1 s.

One value per session, on a chart you do not need that day:
1. 0.5 s.
2. 0.35 s.
3. 0.2 s, only if both were clean.
4. Stop at the first lost reading, and go one step back.
5. After each session, send the app's log ("?" or F1, then "Show the log file").

Too short: a reading is lost and the strip is read again. A failing calibration is retried. If it keeps failing, the measurement ends (Continue Measurement keeps the strips read). In a dual scan, a lost second pass ends M1 and M2, not M0. Clean results at 0.5 and 0.35 s let the default come down.

Honestly
The blue and its 0.37 s wait have never run on a real instrument. If a second pass is lost right after it, please tell us. No blue: choose "Ready light; the instrument's own green / red (i1Pro 3)" (then no green and red either).

Your "conditions" and "dual_scan" folders are still welcome.
 
OK, just did a small test using the dual scan method on version 4.3.52

Using 1.6 seconds for the wait after a light change. These are my beta settings for my i1Pro2:

1795210268383.png


So everything checked and "wait after a light change" set on 1.60 seconds

I have discovered that the auto (bidirectional scanning) must be unchecked in order to work bidirectional:

1795209556711.png


If I check auto: the scanning is unidirectional ONLY, very strange, so I think this is a bug. One would expect strip recognition auto is checked it is automatically bidirectional, but I have discovered this is unidirectional !!!

I will upload 4 ti3 files from a double scan of the same paper: 2 times Action cast paper with OBA with session 1 (auto: checked, thus only unidirectional) and session 2 (auto unchecked and this time bidirectional works) and again 2 times with a textured Aquarel paper that is almost OBA free, again with session 1 and session 2.

IMPORTANT: the blue light noting the back scan is unfortunately dumb. When I start from left to right and stop for the return scan the left blue light is blinking correctly: it indicates the direction (right to left) of the return scan, BUT when I start from right to left and the return scan is thus from left to right the blue light is still blinking on the left: it should be the right light blinking towards the direction of the return scan, thus this must be corrected. Probably the information of the zebra reading can help, as in the previous version it seems to register the direction of scanning. This information can be used whether which light (left or right) to be activated to indicate the direction of the return scan. It is now left light blinking blue all the time even if I would begin scanning from right to left.....the light suggest I should move the spectro to the left (but I am already on the left side......)

Maybe the ti3 file can reveal some information about the effect of OBA versus (almost) NO OBA.

Have a look at them and hopefully some useful information can be extracted from them.

So to be corrected:

-the right blue light blinking (left/right) depending on the direction of the return scan (dual scan)
-bug in strip recognition, when auto is checked the bidirectional scanning (-b) is actually disabled instead of enabled.
 

Attachments

Back
Top