Repository navigation
For everyone updating from 4.3.44: a new {patchsize} placeholder that prints the size of the patches on your chart, a clear explanation when your instrument does not accept the spectral filter you chose, and, on Windows, a reminder to switch off the printer driver's colour management before the print dialog opens. Charts that do not use {patchsize} are made exactly as before, and your measurements and profiles do not change. And with the beta option “X-Rite i1iO support” on, ChromIQ can now drive an X-Rite i1iO 2 table with an i1Pro 2 by itself, without i1Profiler: a first version that has so far run only against a simulated table, so please read its honest limits below. With that option off, which is the default, nothing about the table changes.
New
- {patchsize}: the size of the chart's patches, printed on the chart. Type {patchsize} in the Sheet text or in the clip border's text (it is in both Insert ▾ menus), or in the run's Chart Notes, and the chart shows the patch size in millimetres with one decimal each and no spaces, for example “7.0x7.4”: first the width across the strip, then the length along the strip, in the same order as the two “Patch size (mm)” fields. It is the size the chart was laid out with: the two numbers you typed, or the size ChromIQ worked out for you when the fields are on “auto”. So 7.0 x 7.4 typed prints “7.0x7.4” at any resolution, and the Preview line under the Sheet text shows the same number the chart will print for the sizes you typed, for hexagons too. Where ChromIQ works the size out only when the chart is made (the fields on “auto”, or “Prioritise chart area” chosen), the Preview line shows the example “7.0x7.4”, the way it shows example values for the other placeholders. On paper every patch is made of whole pixels, so a single patch can be a fraction of a pixel wider or narrower than this size, and the “Patch size” row under “Chart layout information”, which measures the first patch as drawn, can show a slightly different number. A hexagonal patch is measured from tip to tip. On a chart laid out by ArgyllCMS printtarg, {patchsize} in the Chart Notes is printtarg's own patch size. Where ChromIQ cannot know the size, {patchsize} prints nothing: on an FD-9 chart, and on a printtarg chart that is not RGB, has hexagonal patches or has only one strip on each of its pages. Thanks to jctay on the printerknowledge forum for asking for this.
- Windows: a reminder to switch off the printer driver's colour management. When a chart goes through the Windows print dialog, a window now opens first and says where the switch is: for Canon, Epson (by model) and HP printers in the words of the makers' own manuals, and what to look for on other makes. It also says what happens if the switch stays on: the driver changes the colours of every patch, a profile built from the chart is wrong, and a verification chart checks the driver's corrections instead of your profile. “Open the print dialog” goes on, “Cancel” prints nothing, and “Don't show this again” stops the reminder. When “Use default Windows printer dialog” is ticked in Preferences, it also tells you that a PostScript printer can get the chart directly, with no driver setting in the way. macOS and Linux are unchanged. Thanks to a tester on dpreview, whose chart lost about 30 % of its colour range because the driver's colour management was on.
Changed
- The Windows help on the Print Chart tab names the same menus as the new window. Canon: on the “Main” tab set “Color/Intensity” to “Manual”, press “Set...”, and on the “Matching” tab set “Color Correction” to “None”. Epson, depending on the model: on the SureColor P700 and P900, “Mode” on the “Main” tab set to “Off (No Color Adjustment)”; on the SureColor T series, “Advanced Settings” on the “Printer Settings” tab, then “Color Mode” set to “Off (No Color Management)”. HP: the “Color” tab, “Application-Managed Colors”. The older help named menus such as “Color Options” and “Epson Color Controls”, which are not where these drivers switch their colour management off.
Fixed
- A spectral filter your instrument does not accept is now explained. With “Spectral filter type (-F)” switched on in the Measure tab and set to a choice the connected instrument refuses, the measurement stopped at once and the tab went back to “Start Measurement” without a word. In ArgyllCMS 3.5.0 the i1Pro 2 (also sold as ES-2000) and the ColorMunki accept no filter choice at all, and the i1Pro 3 accepts the polarising filter only when a polariser is fitted. Now a window says what happened, which instruments this concerns and what to do: switch the option off (it is in Manual mode) and start the measurement again, and the instrument measures in its normal mode, which on an i1Pro 2 is M0. Nothing has been measured or changed when it opens. Thanks to a tester on dpreview for the report.
- CR30: a project's own patch-by-patch setting is kept when you switch to it from a CR30 chart. A CR30 chart is always read patch by patch, so ChromIQ holds “Patch-by-patch mode (-p)” for it and gives the box back when you leave it. When you switched from a CR30 chart to another project, ChromIQ could give back the value from before the CR30 chart instead of the one that project keeps, and the project's next save then stored that value in it. Now the project's own value is the one you see and the one that is saved.
New (only with the beta option “X-Rite i1iO support (beta)” on)
- ChromIQ drives the X-Rite i1iO 2 table itself. With an i1Pro 2 clicked into the table's arm and a chart made for “i1iO 2 + i1Pro 2” in Create Chart, START MEASUREMENT in the Measure tab now moves the arm and reads the chart for you, in Guided and in Manual, without i1Profiler. Until now START only explained how to measure the chart in i1Profiler. That way still works: IMPORT in the Measure tab brings back a measurement made in i1Profiler 3.8.6 or older, as before. The drive is part of the existing beta option, so there is no new switch, and Preferences › Beta explains it in the option's (i). A chart made for another i1iO table keeps the i1Profiler steps.
- The first time, ChromIQ explains everything before it moves anything. On each computer, before the first drive, a window says what ChromIQ will do, that this is unofficial (X-Rite neither made nor approved it), what has and has not been tried on a real table, and how to stop the arm. You tick “I have read this.” and press “I understand, drive my table”; “Not now” sends nothing. ChromIQ remembers your answer and asks again only if that text changes.
- How a table measurement goes. ChromIQ first asks you to get ready: i1Profiler closed, the arm at its resting place over the small white tile, nothing on the bed but your sheet, and the arm's height set for your paper. You confirm two things before ChromIQ talks to the table at all. A table that has just been switched on can be started by ChromIQ, the way i1Profiler does, or you leave that to i1Profiler. The i1Pro 2 is calibrated on the table's white tile and stays in the arm, as i1Profiler does it; if you prefer its own white tile, choose that in Preferences › Beta or on the first page of a table measurement. ChromIQ makes the white only with the arm at its resting place over the tile, where every recorded calibration was made (if the arm stands a little off, it brings it home first, after asking you to take your hands away), and after a white on the instrument's own tile it reads the table's tile once to check that the white is right: if it is not, nothing is read with it and you calibrate again. You lay the page with mark 1 at the top left, the table lets go of the arm, and you push the arm gently by hand until the cross hairs of the sight sit on each of the three marks, pressing Aimed for each one. Instead of Aimed you can press the button on the i1Pro 2 itself, once, so your hand can stay on the arm; the button never starts a move. Before the arm moves after any question, ChromIQ asks you to take your hands away and waits until you confirm it, on a page of its own or with your answer to that question: the page you lay on the table, for example, is confirmed with “The page is laid, and my hands are away from the table”, and the arm moves only after that. The arm then goes to where ChromIQ works out the third mark is and asks whether the instrument's round opening sits on it; if not, nothing is read and the arm only goes home. Then the chart is read row by row, each row from the end with marks 1 and 2, as i1Profiler reads patch by patch, and a chart of several pages page by page, with the marks aimed again on each page.
- Patch by patch by default, rows as strips as a first try. “Patch-by-patch mode (-p)” decides how the table reads your chart. Ticked, which is the default for a table chart, the arm stops on every patch and the i1Pro 2 takes one reading there: the careful way, and the one we recommend. Not ticked, the arm drives along each row while the instrument reads all the time, the way i1Profiler reads a row, and ChromIQ finds each patch in those readings by where the arm was at the time: much faster, and a first try. ChromIQ never guesses a value: a row that cannot be cut cleanly into its patches is not kept, and you choose to read it again as a strip, read it patch by patch, skip it, or end the step. A row too long for one strip move is read patch by patch by itself. If strips work for you, keep that choice for every table chart: Save as Defaults on the Measure tab with a table chart loaded, Preferences › Beta ("Table charts start with “Patch-by-patch mode (-p)” ticked"), or the offer ChromIQ makes once after a measurement in which every row was read cleanly as a strip (its “Not now” stands where Close usually stands, so a quick click never changes your default). That is the table's own setting: charts for your other instruments keep theirs, and a project that keeps its own setting opens with its own.
- Stop, Report a problem, and every ending. Stop and Report a problem are on screen the whole time the table is in use. Stop halts before the next move, and nothing moves until you choose what happens next. Report a problem offers “Send nothing more”, or “Something looks or sounds wrong”, after which nothing moves except bringing the arm home, which ChromIQ asks about first; either way you can add a note in your own words. Whenever a move of the table may still be waiting, or a movement was not reported as finished, “Switch the table off now” at its power switch is the first thing ChromIQ shows, also when you press Report a problem at that moment, and no later window hides it; Stop and the line about the power switch stay on screen. ChromIQ says the arm is at its resting place only when the table has reported it there; otherwise it says where the table last reported it, and that i1Profiler brings it home when ChromIQ cannot. An answer after which the arm moves at once (Go, “The page is laid, and my hands are away from the table” and the others that say “my hands are away”) can be pressed only once its window has been on screen for a moment (0.6 seconds); until then it shows as not yet ready, in its own size, so the second click of a double click meant for the window before can never move the arm. The instrument's button waits the same moment before it counts as Aimed. When you end a measurement early, the arm stays where it is while you choose: Save and stop writes what you have read so far into the run, Discard and stop writes nothing, and Keep measuring goes on. Patches still missing can be read later: tick “Refine / resume existing measurement (-r)”, press START MEASUREMENT, and the table reads only those. A finished measurement ends in the usual completion window, exactly as when you measure by hand. During your first measurement ChromIQ also asks after each step whether the table and the arm did what you expected; at the end you can switch that question off, and on again in Preferences › Beta.
- The first time in a panel, afterwards like your other instruments. During your first table measurement, while ChromIQ asks after each step, the table's questions stand in a panel on the left of the Measure tab, with its own Stop. Once you have switched that question off (at the end of a measurement, or in Preferences › Beta), the Measure tab looks as it does when you measure by hand: its options greyed, the live-preview options still yours to change, the log telling you what the table does (where the arm is, which row and patch it reads, the white reference, each question and your answer), and the tab's own Stop, red while a table measurement is open, which stops the table before its next move and then asks whether to carry on, end the measurement or bring the arm home. Above it stays the line “To stop the arm at once, switch the table off at its power switch.”, and beside it Report a problem. Whenever the table needs an answer, a small window opens beside the chart, in the style of the measurement windows of your other instruments, and nothing moves while it is open; each one also offers End measurement. Unlike those windows, no button here is pressed by Enter, Return or the space bar: an answer that may let the arm move is always a click. Each window after whose answer the arm moves at once says itself how to stop the arm at its power switch, because it covers that line of the tab. You can move the window, and ChromIQ opens it there again next time, always fully on the screen it opens on. When ChromIQ is not the app in front, a window that opens makes ChromIQ's Dock icon bounce (on Windows its taskbar button flashes); it never takes the keyboard from the app you are typing in.
- The table's own white values, used by default, as i1Profiler does. The table keeps values for its white tile in its memory, and i1Profiler uses them when it calibrates on that tile. Table measurements in ChromIQ now do the same by default: on recorded readings of one real table, this made ChromIQ's code agree with i1Profiler's values to about 0.1 ΔE00 on average (about 0.65 ΔE00 with the instrument's own white reference). So a table measurement can differ slightly from a measurement you make by hand with the same instrument. To measure on the table with the instrument's own white reference, as by hand, switch off "Use the table's stored white tile values (as i1Profiler does)" in Preferences › Beta, under the table's other settings. ChromIQ reads the table's tile once after each calibration (the arm does not move). If at the first calibration the table's values cannot be read or do not look like those of a white tile, ChromIQ says so on screen and measures with the instrument's own reference. A measurement keeps the white reference it started with to the end, so that all its readings go into one file and it can always be saved: if a later calibration (after an hour, or when the i1Pro 2 asks for a new white) cannot use the table's values, ChromIQ does not use that calibration, reads nothing with it, and offers to calibrate again or to save what was read and end. The first page of a table measurement names the reference it uses, the session's diagnostics file records it, and a measurement file made with the table's values says so in its header (CHROMIQ_TABLE_WHITE). Readings made with and without the table's values never go into one file: a refinement, a resume, or the completion of earlier table readings that were made the other way is refused before anything is sent to the table, and the message says what you can do: switch the option in Preferences › Beta to the way those readings were made, or measure the chart again.
- Every run type. Profile runs, refinement runs (the table reads only the patches the refinement asks for), calibration runs and verification runs are all measured by the table and saved where a measurement by hand would be saved, under the same names. Readings from an earlier table measurement are only ever completed into a measurement of the same chart, and of the same verification.
- A diagnostics file of every table measurement. It records what was sent to the table, what came back, the times and the readings, and the versions of your system and of ChromIQ, but no serial numbers, no names and no folder paths. Whether it worked or not, please send it to us on GitHub: it is how this gets better for every table owner.
- What the app now carries for this. To talk to the table over USB, ChromIQ now includes pyusb 1.2.1 (BSD licence) and libusb 1.0.30 (GNU Lesser General Public License 2.1 or later), loaded as a separate, unmodified library; the details are in THIRD-PARTY-NOTICES.md. On Windows the table is reached through the libusb-win32 driver ChromIQ already uses for measuring instruments. This beta does not offer to install that driver for the table yet, because while the table has it, i1Profiler cannot use the table; a table without it gets a message that says so, and nothing is sent to it. On a Windows for ARM computer the drive works only where ChromIQ can load the USB library it needs; where it cannot, a message says so, and nothing is sent to the table. Measuring in i1Profiler and IMPORT work everywhere.
Honest limits
- The driver menu names come from the makers' manuals, not from every driver. They were checked against Canon's IJ printer driver manuals, Epson's user's guides for the SureColor P700/P900 and the SureColor T series, and HP's support pages. Other models can name them a little differently, and a driver in another language shows them translated. The two new windows are shown in this version as proposed texts and may still be reworded.
- Charts that do not use {patchsize} are unchanged, and this was checked. Thirteen built-in presets of different kinds (i1Pro, i1Pro 3, ColorMunki, CR30 with hexagons, Scanner, Red River, one to six pages) were loaded and generated in the real app with 4.3.44 and with this version, once as they are and once with the layout stamp on and Chart Notes full of placeholders, and every file written was compared byte for byte (dates and the version number pinned): no difference.
Honest limits of the i1iO table drive
- What has run on a real table, and what has not. On one real i1iO 2 with an i1Pro 2, on a Mac, with ChromIQ's separate tester program, these have run: the movements (the table's own homing, drives out over the empty table and back, and the mode in which the arm is pushed by hand), the start-up of a table that had just been switched on (once), the white calibration on the instrument's own tile and on the table's tile, and one reading of the table's tile. Reading rows, patch by patch or as strips, has not yet run on a real table with ChromIQ.
- ChromIQ's own code gets i1Profiler's values from i1Profiler's readings. The table's owner recorded i1Profiler reading two rows of 24 patches on his table, once as strips and once patch by patch, and sent the files i1Profiler saved. From the instrument's raw readings in those recordings, ChromIQ's own code worked out the 48 patch colours about 0.1 ΔE00 away from i1Profiler's values on average, when it uses the white values stored in the table, as i1Profiler does (about 0.65 ΔE00 with the instrument's own white reference). This is a computation on recorded readings, not a measurement made by ChromIQ on the table.
- One wrong number was found and corrected. Those runs showed that ChromIQ expected the arm in the wrong place after one short move at the start of the aiming. That would have stopped every measurement in the app right there, before any aiming. It is corrected in this version, with the place the real table reported twice. Three smaller things were corrected from the same recordings: one more answer of the table before a strip row is accepted, the speed i1Profiler scanned with is now one of the recorded speeds, and a position reading a hair outside the tolerance is read once more before ChromIQ stops.
- The drive inside the app has so far run only against a simulated table. Every screen, every movement, every ending and every run type was tried that way, on screen, with a simulated table and a simulated instrument that now behave like the real table did. Not one patch has yet been read by the app on a real table. The moves ChromIQ works out for your sheet (aiming, the rows, feeling its way towards the front of the table) are worked out the way i1Profiler's are, but they have not run on a real table yet, and so are reading rows as strips and using the instrument's button as Aimed (i1Profiler uses the button the same way). That is why ChromIQ asks you to look whether the opening sits on mark 3 before it reads anything.
- Windows and Linux are completely untested. It may not work there. If it does not, ChromIQ stops with a message that says what it found, and you can still measure in i1Profiler and use IMPORT. On Linux the table needs a small rule file before ChromIQ may open it; the message says so.
- Only recorded commands are sent. ChromIQ sends the table only commands taken from USB recordings of i1Profiler, never anything that writes into the memory of the table or of the instrument. Where the arm goes on your sheet is worked out by ChromIQ, at speeds that were recorded, inside the part of the table ChromIQ allows.
- A chart without aiming crosses is aimed at its corner patches. When the crosses are switched off in Create Chart, you aim the sight's cross hairs at the centre of three corner patches instead; the panel names each one as it is printed on your sheet (for example "patch A1, the one at the top left") and the preview rings it. A patch has no fine centre as a cross has, so aiming by eye is a little less exact there: the arm's move to the third point, and your look whether the opening sits on its centre before anything is read, is what catches an aim that was a little off.
- How to stop the arm: switch the table off at its power switch. That is always allowed, and ChromIQ will never ask you not to. Leave it off for ten seconds before you switch it on again. Unplugging the USB cable is not the same: it does not switch the table off. If ChromIQ ever ends while it drives the table (a crash, a forced quit, a power cut), switch the table off and on again before you open i1Profiler; ChromIQ's next START asks about that first.
- Thank you, crismi2. Everything in the table drive is built on the USB recordings of i1Profiler that crismi2 made on his own table, and on the tester sessions run there. Without that patience none of this would exist.
Installation (Linux, beta): Download the tarball for your architecture (x86_64 for most desktops/laptops, aarch64 for ARM systems like Raspberry Pi 4/5). Extract with tar xzf ChromIQ-Linux-*.tar.gz, then run ./ChromIQ/ChromIQ. Requires ArgyllCMS — install via your package manager (sudo apt install argyll) or from argyllcms.com/downloadlinux.html.
☕ ChromIQ is free and always will be — if it saves you time or ink, a coffee is a kind way to say thanks. Completely optional, and the app stays fully featured either way.
Source of libusb (LGPL): ChromIQ now includes libusb 1.0.30, unmodified, under the GNU Lesser General Public License 2.1 or later, loaded as a separate library. Its source, libusb-1.0.30.tar.bz2, exactly as published by the libusb project, is attached to this release.