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

[crenedecotret]

Very good effort!
Just for information: my weekly token limit on my two Claude accounts is completely used up at the moment. So I am currently not able to make anymore changes. The limits will reset later this day in the night. So don’t expect changes before tomorrow. Sorry for that. But at least I squeezed everything out of this for the money I am paying

I also want to add something to the way users can save their own presets in create chart. I want to give the option to add a ti1 file as part of the user presets. This would then be saved together with the preset in the preset folder and for such a preset ChromIQ would behave the same way as it does for our built in ones.

Are you using the text UI version of Claude? I dont know if this might help or not but I moved over to OpenCode and some open source models (KIMI, QWEN, Deepseek). I had already tested KIMI a lot side by side with Claude when I was still using Windsurf

 

[crenedecotret]

Maybe a possibility to convert cgat and i1profiler pxf files into argyllcms ti1 too ? This way I can convert the Tc918 target into argyllcms more effectively.

I can help with that since I already had code to convert ti1 files to pxf in my old patch generator. You can use the attached python script (rename to *.py)

usage is simple
python3 pxf_to_ti1.py input.pxf [output.ti1]
python3 ti1_to_pxf.py input.ti1 [output.pxf]

Edit: I think this one had already been figured out by our friend istab but I was 3 pages behind on this thread

 

[pharmacist]

OK I just used the i1Profiler built-in T9.txt cgat file as a base and modified it a bit to have 924 patches and the space bars are now much more logical than my previous TC924.ti1 file that seems to be fawlty:

second page:

I will let it dry and scan this target this evening and report back.

 

[itsab1989]

I played around and added a ti2 editor to the new tools icon. Don't know if this is useful but I thought it might be for someone maybe.

https://github.com/itsab1989/ChromIQ/releases/tag/v3.8.0-beta.18

 

[pharmacist]

In that case export to pxwf workflow file would be nice too

 

[itsab1989]

In that case export to pxwf workflow file would be nice too

What even is such a file and what it is for?

 

[pharmacist]

A pxwf workflow file is similar to a ArgyllCMS ti2 file: it defines the patch size/layout/paper size/with or without space bars/defining the spectro etc.

 

[itsab1989]

@pharmacist
From Claude:

==============================================================================
FOR PHARMACIST — .pxwf reference files we need
==============================================================================

Hi! To add .pxwf (i1Profiler workflow) export to the ChromIQ TI2 editor,
I need a few real workflow files from your i1Profiler installation as
reference. The format isn't publicly documented, so I'll look at
it from your samples — exactly the way the existing .pxf export was built.

------------------------------------------------------------------------------
WHAT I NEED
------------------------------------------------------------------------------

3 – 5 .pxwf files that together cover the configurations you use day-to-day.
Each one should be saved while i1Profiler is set up for a REAL job (don't
strip anything out — keep instrument, paper, layout, all of it). Variety
matters more than count; ideal coverage:

1. Your most-used scanner workflow — whatever you reach for first
(i1iSis / i1iSis 2 / i1iSis XL). RGB target, A4 portrait.

2. The same as #1, but landscape paper or a different paper size you
commonly print.

3. A -h (double-density) or otherwise unusual layout — anything where
you've changed the patch scale, spacer scale, or margins from
defaults.

4. CMYK target (if you do CMYK profiling) — same i1iSis, but CMYK
patch set.

5. Spot-mode workflow (i1Pro / ColorMunki, manual strip reading) if
you ever use one — the schema may differ vs. the scanner cases.

Skip duplicates — if #1 and #2 are basically identical, send #2 only.

------------------------------------------------------------------------------
HOW TO EXPORT EACH ONE IN i1Profiler
------------------------------------------------------------------------------

1. Open i1Profiler.
2. Set up the workflow exactly as you'd run it (instrument, paper,
patches, spacers, scale, margins — the whole thing).
3. File → Save Workflow As… (or Workflow → Export… depending on
i1Profiler version).
4. Save with a descriptive name like
pharmacist-i1isis-a4-rgb.pxwf
so I know what each one represents.
5. Repeat for each row above.

If i1Profiler doesn't offer a Save-Workflow command in your version, the
workflows are also stored on disk:

macOS: ~/Library/Application Support/X-Rite/i1Profiler/Workflows/
Windows: CProgramData\X-Rite\i1Profiler\Workflows\

Copy the .pxwf files from there.

------------------------------------------------------------------------------
WHAT TO SEND BACK
------------------------------------------------------------------------------

Zip the .pxwf files together with a short note saying which config each
one corresponds to. Example:

pharmacist-i1isis-a4-rgb.pxwf — daily driver, i1iSis 2, A4 portrait,
RGB OFPS 1617 patches
pharmacist-i1isis-a3-cmyk.pxwf — CMYK profile target, A3, 2033 patches

Send to Bastian. Once I see the XML structure across 3 – 5 real configs,
the export feature is straightforward (the patch-set side is already
done in workflow/i1profiler_export.py).

------------------------------------------------------------------------------
ONE QUESTION FOR YOU
------------------------------------------------------------------------------

Would you want the editor's Save As to offer the workflow file alongside
the existing TI2 output in the TI2 layout editor

Save As → i1Profiler workflow (.pxwf)

Or would you prefer a separate

Tools → TI2 → i1Profiler workflow

entry that takes a saved TI2 + page TIFFs and bundles them into a .pxwf
after the fact?

Either is straightforward — I'd recommend the first (Save-As path)
because the editor already has the layout context in memory. Of course
it would be possible to add both.

 

[pharmacist]

OK, I will try to make some pwxf file using the most used spectro's in i1Profiler: i1Pro1/2/3 and also making difference between modern (no space bars) and legacy (with space bars) between them so Claude can have a look at based on a ti1-derived pxf-file so Claude can make the connection between ArgyllCMS ti1/2ti2 file configuration and linking it with the i1Profiler pxf/pxwf file layout. For the i1IO/iSis layout I will do later, not sure this will be popular (as these devices are very expensive and actually niche).

 

[itsab1989]

Just don’t modify those files in any way. It needs them the way the come out. It can produce ti2 and ti1 itself and needs to figure out what is required to do the complete conversion.