YAAW - Yet Another Argyll Wrapper

[riclin]

Well, I think both sides have valid arguments. For me it's merely out of interest how far my printed target is away from the expected values. Using an i1pro with the standard ruler/jig doesn't give much room for user created mis-measurement, but that might be completely different with other devices. Way off values might indicate reading errors, but also - perhaps - problems with the printer (i. e. nozzles not firing). Ultimately it's a personal preference, how one would like to interpret the values. As you already stated: No big effort to run a shell script afterwards and also append the data to the existent log file.

Don't forget also that by default, YAAW does not suppress chartread unexpected delta-E warnings so unusual readings will be exposed there - although admittedly this information does not appear in the logfile since chartread runs in its own terminal window.

 

[riclin]

Don't forget also that by default, YAAW does not suppress chartread unexpected delta-E warnings so unusual readings will be exposed there - although admittedly this information does not appear in the logfile since chartread runs in its own terminal window.

Further to the above:

I remain of the view that highlighting ΔE values could be misleading, but appreciate that YAAW's failure to log misreads and similar warnings was a limitation. I have placed a new version onto github which whilst not doing as Ron requested (sorry Ron) responds instead a little differently. The "Read Target" (chartread) phase no longer launches an external terminal, but instead runs in an embedded psuedo-terminal window with a virtual terminal only being used as fallback the pseodo-terminal cannot be activated. This now simplifies the chartread messages being captured by YAAW and filtered in real time for warnings or errors, which are then also recorded in the logfile along with the patch strip where any error or warning occured for subsequent attention. A "View Log" button has been added to the bottom of the Execution screen which toggles between a recorded logfile and the current live display - this allows the same main window to be used for both current real-time information and also the persistent logfile.

The quality of the profile can be reasonably assessed with the profcheck results - generally, average and max errors of less than about 1.5 & 2.5-3.0 respectively indicate reasonably sound results.

yaaw-3.40.11 resides at:

https://github.com/riclin-au/YAAW-Yet-Another-ArgyllCMS-Wrapper-Workflow

r/

 

[rjanowsky]

I remain of the view that highlighting ΔE values could be misleading, but appreciate that YAAW's failure to log misreads and similar warnings was a limitation. I have placed a new version onto github which whilst not doing as Ron requested (sorry Ron) responds instead a little differently. The "Read Target" (chartread) phase no longer launches an external terminal, but instead runs in an embedded psuedo-terminal window with a virtual terminal only being used as fallback the pseodo-terminal cannot be activated. This now simplifies the chartread messages being captured by YAAW and filtered in real time for warnings or errors, which are then also recorded in the logfile along with the patch strip where any error or warning occured for subsequent attention. A "View Log" button has been added to the bottom of the Execution screen which toggles between a recorded logfile and the current live display - this allows the same main window to be used for both current real-time information and also the persistent logfile.

Good improvement! Without an external terminal window the look and feel is cleaner. Getting chartread output onto screen and in the log is really helpful. The "View Log" button is also valuable. No more reason to open a shell to get the log file. And if I really wanted to get the worst patches, a shell script is the way to go.

The quality of the profile can be reasonably assessed with the profcheck results - generally, average and max errors of less than about 1.5 & 2.5-3.0 respectively indicate reasonably sound results.

Yes, for sure that info is most often all you need to evaluate the quality.

 

[riclin]

YAAW 3.40.13 uploaded to github:

3.40.12: Added chartread -r resume and -p patch-by-patch controls; introduced a restrained portable visual refresh with a lighter neutral background, clearer hint text, stronger section headings, slightly airier spacing, accented workflow buttons, and improved monospaced execution displays.

3.40.13: Removed redundant help-row hint text and right-aligned the targen, printtarg, chartread, and colprof Help buttons.

https://github.com/riclin-au/YAAW-Yet-Another-ArgyllCMS-Wrapper-Workflow

 

[riclin]

Well, I think both sides have valid arguments. For me it's merely out of interest how far my printed target is away from the expected values. Using an i1pro with the standard ruler/jig doesn't give much room for user created mis-measurement, but that might be completely different with other devices. Way off values might indicate reading errors, but also - perhaps - problems with the printer (i. e. nozzles not firing). Ultimately it's a personal preference, how one would like to interpret the values. As you already stated: No big effort to run a shell script afterwards and also append the data to the existent log file.

OK - so I have been converted - I noticed a post here by Graeme Gill that was endorsing your suggestion (or v.v.) so who am I to argue otherwise? The most recent version of YAAW (v3.40.14) now records the ten highest profcheck delta-E values in the persistent logfile, but for clarity, they are not displayed in the main status window. I think that's a reasonable solution which balances both of Graeme's points on this topic (profcheck html page vs his post here a week or so ago). Let me know if you think otherwise.

YAAW is at that git place.

r/

 

[rjanowsky]

Something does no longer work for me. Loaded a config and wanted to execute Step 3: Only one new window opens, but nothing happens - see screenshot. Pressing Enter to Start Calibration does not change anything. Can't close the window.

 

[rjanowsky]

Same problem with 3.40.13. Last working is 3.40.11.

 

[riclin]

Same problem with 3.40.13. Last working is 3.40.11.

Interesting - must be a subtle macOS issue I suspect since it's doing the business OK on my linux boxen. Watch this space .....

EDIT: v3.40.12 and later appear to expose a macOS Aqua/Tk focus or key-event problem. I think the issue is now sorted but need to run it up on a Mac with a spectro attached first to confirm. I will update github and advise here once tested.

r/

 

[riclin]

I ran up a VM to test YAAW under macOS - the reported glitch now appears to be sorted. V3.40.20 is now available for download which also includes the ability to view a X3DOM gamut cloud as indirectly suggested (via another thread) by Graeme Gill - his suggested ΔE test generated the html so I figured it was better to use it than throw it away. It does mean passing the html to the system browser, but that's not so costly I think - all computers will have one. However the X3DOM display was not specifically tested under macOS due to unavailable WebGL acceleration in the virtual machine. Please post your experiences.

Find it at github - V3.40.20.