Some suggestions of improvements that would be great to have:
1) Update the data tables when new data gets read. I.e for a gray scale run, fill in the data columns for each reading done instead of after all has been done. Same in color data tables. I guess this would be an easy one if the table update code is a function.Just call that function repeatedly after each data read...
2) Possibility to start a gray scale run on a freely chosen point. E.g start at IRE 60 for ironing out RGB gain issues. This one is probably harder since you need to create new GUI controls for it.
3) Having a HLS column approach a'la ChromaPure to dial in CMS issues instead of the bulls eye would be great. For now I use continous reading of a selected color column and track the yellow dot in the gamut diagram. That works, but the HLS column approach is really neat. If one could select between the bulls eye and a HLS column thingie in the same place where the bulls eye is via a drop down select, that would be really great.
4) Saturation sweeps would be better off done in ONE run instead of each primary and secondary color separately. It gets kind of tedious to use this as it is handled now. You may keep the separate runs as an option though.
5) The 0% saturation reading is IMHO unnecessary. Must be the same as pure gray, or? The MCD disk does not have them. I suggest you drop them (maybe as an option in the preferences for backward compatibility)
6) The new dE selections in the preferences are not that intuitive and since they also go with the other selection of how to interpret Y and gamma etc this becomes to big a hurdle for the novice. Further, it is my understanding that dE2000 is "better" for grayscale and dE74 is better for color. However I understand this is no easy subject (see this thread
). If the help system was updated and linked maybe this could be ok, but I still think we need a more intuitive GUI there. I suggest making the dE selection go in two separate sections. One for grayscale errors and one for color errors. In both of these sections you can set optional setting appropriate for these situations (meaning simplifying them). And we need to provide a good default setting for the novice. You don't really need to understand all the theory behind different dE formulas in order to use HCFR for a calibration - as long as there are good default settings.
The two different color and grayscale dE settings would then be applied where they belong automatically, when doing gray scale runs, the grascale dE setting is used and likewise for color.
What do you think? HCFR would really need a better workflow-oriented design to really become user friendly, but the things mentioned here would bring a lot of improvement without to much work I think.