YAAW - Yet Another Argyll Wrapper

[rjanowsky]

I just startet a complete new test run with the latest YAAW. I printed a 210 patches target. At the moment it's drying, but tomorrow I will try the measuring again. My instrument is an old i1Pro spectro with the original strip measuring ruler. Normally I'm quite sure in using this devices. Misreadings appear with this combination not so often. After measuring the test target, I will report back.

Ronald
--

 

[rjanowsky]

Test with 210 patches target:

Reading strip A gave message C was read, strip B gave E, strip C gave C, strip D gave D

That's really strange, because with ChromIQ reading the .TI2 file was fine. A .TI3 was generated and also an ICC profil. Lastly I copied the .TI3 file (from ChromIQ) to YAAW and Step 4 could be done successfully. See attached the whole working directory in the zip-file.

 

[itsab1989]

I just read the last few posts really quick. Congratulations to your new release! I really feel what you are saying. You think you are done and everything is tested. But once you release it you find a bug. And another one. And one more. And a UI element does not align correctly. And you want to put all of this aside for a while but you can’t because once you have noticed it you feel the urge to fix it.

Those reading errors are really chartread warnings. When I tried to to create my first profile on plain paper those drove me crazy because I had to manually confirm each strip I had read. Later I realized a few things:
1. on higher quality paper you get much fewer of those errors
2. it helps to disable bi-directional readings in some cases. Although not comfortable for i1Pro devices it takes away one possible cause for errors. And although you are not told this very upfront Argyll disables bi-directional for non-randomized charts by deafult which might cause confusion sometimes.
3. when you create profiles for lower quality or matte papers it helps to disable the warnings (there is a chartread argument for this). I found the warnings to be very stressful and break the measuring flow. So they made things worse instead of better. So I disabled them by default in ChromIQ to avoid this confusion. However you could make an argument that it is more transparent for the user to leave them turned on.

 

[riclin]

Test with 210 patches target:

Reading strip A gave message C was read, strip B gave E, strip C gave C, strip D gave D

That's really strange, because with ChromIQ reading the .TI2 file was fine. A .TI3 was generated and also an ICC profil. Lastly I copied the .TI3 file (from ChromIQ) to YAAW and Step 4 could be done successfully. See attached the whole working directory in the zip-file.

I should have noticed that you are using an i1Pro and not a Colormunki - sorry about that. As mentioned in my recent covering post, YAAW has been extensively tested with the CM - but until now, only a CM. You are breaking new ground

The issue here can only be the arguments being passed to the various Argyll tools by YAAW, with the defaults being tailored to the CM. This does not mean that YAAW won't work for you - merely that you may need to adjust the settings on the Config screen to suit your device. You mention that you've had some success with ChromIQ so I suggest that you look at the Argyll arguments being used there and enter them into the YAAW fields - in particular look at the printtarg settings since that's where the reader type is defined. If additional settings are needed beyond the selections of the YAAW printtarg section, they can be entered into the "additional args" fields and once saved (either automatically or explicitly) will be available for future runs. FWIW - the profile that you included in your last post may have been created successfully but is not good - colprof reports:

8< 8< 8< SNIP >8 >8 >8
[2026-07-08 19:36:31] Done gamut boundary table
[2026-07-08 19:36:31] Profile check complete, peak err = 91.932468, avg err = 25.218252, RMS = 29.184143
[2026-07-08 19:36:31] === STDERR ===
[2026-07-08 19:36:31] INFO: colprof: Warning -
[2026-07-08 19:36:31] INFO: !!!!!!! Additive space has ink limit of 290% - this will be ignored !!!!!!!
[2026-07-08 19:36:31]
[2026-07-08 19:36:31] Validating profile with profcheck...
[2026-07-08 19:36:31] Running: profcheck -k 'Epson SC-P600 Test_Ilford Test_OEM-Argyll_210.ti3' 'Epson SC-P600 Test_Ilford Test_OEM-Argyll_210.icc'
[2026-07-08 19:36:31] Profile check complete, errors(CIEDE2000): max. = 44.520837, avg. = 13.167687, RMS = 14.881306
[2026-07-08 19:36:31]
[2026-07-08 19:36:31] === PROFILE CREATED SUCCESSFULLY ===
8< 8< 8< SNIP >8 >8 >8

So although colprof managed to create an ICC profile, those errors look very high - from memory, maximum error should be below 15-20 - not 44+ as reported by profcheck.

I'm sorry that I can't help you more regarding the settings for the i1Pro but I don't have one to test with. However it is an x-rite device so I wouldn't expect it to be radically different from the ColorMunki. Perhaps itsab1983 can pipe in with the settings that he suggests for the i1Pro? Alternatively, the man pages are there for reading and inwardly digesting - I'll look a little further myself later in the day (we're in very different timezones ).

Keep me posted Wim? - I'm sure that this is an easy fix.

r/

 

[rjanowsky]

The issue here can only be the arguments being passed to the various Argyll tools by YAAW, with the defaults being tailored to the CM. This does not mean that YAAW won't work for you - merely that you may need to adjust the settings on the Config screen to suit your device. You mention that you've had some success with ChromIQ so I suggest that you look at the Argyll arguments being used there and enter them into the YAAW fields - in particular look at the printtarg settings since that's where the reader type is defined. If additional settings are needed beyond the selections of the YAAW printtarg section, they can be entered into the "additional args" fields and once saved (either automatically or explicitly) will be available for future runs. FWIW - the profile that you included in your last post may have been created successfully but is not good - colprof reports:

I will have a closer look at the parameters passed to the Argyll tools. It should be not so complicated to spot the false values. Generally the process is working, only chartread is misbehaving.

So although colprof managed to create an ICC profile, those errors look very high - from memory, maximum error should be below 15-20 - not 44+ as reported by profcheck.

The profile's quality is at the moment not so important to me. I did a quick measurement - roughly one hour after printing the target. First the chartread problem, then the next one.

 

[riclin]

I will have a closer look at the parameters passed to the Argyll tools. It should be not so complicated to spot the false values. Generally the process is working, only chartread is misbehaving.


The profile's quality is at the moment not so important to me. I did a quick measurement - roughly one hour after printing the target. First the chartread problem, then the next one.

I have uploaded an update to YAAW which attends to several observations:

3.39.18
- Added wider, more readable YAAW confirmation/warning dialogs.
- Added instrument-aware filename/profile naming:
<printer>_<paper>_<ink>-Argyll_<instrument>_<patchcount>
- Added editable Paper Size field with A3R/A2R rotated aliases.
- Added A3R mapping to 420x297 and A2R mapping to 594x420.
- Added/updated instrument-specific patch-layout tables for CM, i1, and 3p.
- Various cosmetic tweaks
- ColorMunki layouts are author-tested; i1/i1Pro3+ layouts are printtarg-generated and require physical-device confirmation.

https://drive.google.com/file/d/1k2oJgBuj0aOct16YWLAM1S4uzWayebGB/view?usp=sharing

The i1 settings should come a lot closer to delivering you successful results Ron. The i1 defaults deliver what visually look to be useful targets, but without the physical hardware, I'm unable to confirm that. Select the i1 instrument at the printarg "Instrument:" dialogue and then click the dropdown button at the RH edge of the "Patches" box - this will expose 4 patchcount/paper options that I hope will work with the i1Pro.

Please let me know how you go.

r/

 

[riclin]

I just read the last few posts really quick. Congratulations to your new release! I really feel what you are saying. You think you are done and everything is tested. But once you release it you find a bug. And another one. And one more. And a UI element does not align correctly. And you want to put all of this aside for a while but you can’t because once you have noticed it you feel the urge to fix it.

Those reading errors are really chartread warnings. When I tried to to create my first profile on plain paper those drove me crazy because I had to manually confirm each strip I had read. Later I realized a few things:
1. on higher quality paper you get much fewer of those errors
2. it helps to disable bi-directional readings in some cases. Although not comfortable for i1Pro devices it takes away one possible cause for errors. And although you are not told this very upfront Argyll disables bi-directional for non-randomized charts by deafult which might cause confusion sometimes.
3. when you create profiles for lower quality or matte papers it helps to disable the warnings (there is a chartread argument for this). I found the warnings to be very stressful and break the measuring flow. So they made things worse instead of better. So I disabled them by default in ChromIQ to avoid this confusion. However you could make an argument that it is more transparent for the user to leave them turned on.

Yep - agree with your thoughts and observations. Although I'm reluctant to use the chartread -S switch - if a profile is going bad then I think I'd rather know about rather than being lulled into a false sense of security. YMMV.

Thanks for your comments. ChromIQ is looking good!

r/

 

[rjanowsky]

Got it working/reading:

Not working: chartread -v -T 1 -l -H 'Epson SC-P600 Test_Ilford Test_OEM-Argyll_210'

Working: chartread -v -T 0.5 -S -c 1 -b 'Epson SC-P600 Test_Ilford Test_OEM-Argyll_210'

I think -S is not necessary, but I "borrowed" it from ChromIQ call to chartread.

3.39.18
- Added wider, more readable YAAW confirmation/warning dialogs.
- Added instrument-aware filename/profile naming:
<printer>_<paper>_<ink>-Argyll_<instrument>_<patchcount>
- Added editable Paper Size field with A3R/A2R rotated aliases.
- Added A3R mapping to 420x297 and A2R mapping to 594x420.
- Added/updated instrument-specific patch-layout tables for CM, i1, and 3p.
- Various cosmetic tweaks
- ColorMunki layouts are author-tested; i1/i1Pro3+ layouts are printtarg-generated and require physical-device confirmation.

Will download and try.

 

[riclin]

Got it working/reading:

Not working: chartread -v -T 1 -l -H 'Epson SC-P600 Test_Ilford Test_OEM-Argyll_210'

Working: chartread -v -T 0.5 -S -c 1 -b 'Epson SC-P600 Test_Ilford Test_OEM-Argyll_210'

I think -S is not necessary, but I "borrowed" it from ChromIQ call to chartread.


Will download and try.

-H - high res mode - chartread should use it if available for instrument else ignore it - switchable on the Config page - turn it off there
-c - useful if you need to explicitly select the device - but that wasn't an issue for you was it? Harmless.
-S - suppress warnings meaning there's reduced diagnostics. Not a fan.
-b - bidirectional strip reading - I wouldn't use bidirectional reading yet until you know that everything's working
-T - the working chartread is actually less tolerant than my default - if anything 0.5 should increase misreads
-l - harmless

The big difference I see there is the -H switch if the instrument doesn't support it. Try using the default settings but turn the High Resolution Spectrum setting off on the config page. The current version here (not posted yet) now only sets the -H option on for the CM and leaves it off by default for other instruments.